sbhat7's comments

sbhat7 | 7 years ago | on: Rebuilding My Personal Infrastructure With Alpine Linux and Docker

Deployment of a new version would depend upon your setup. Assuming a setup similar to the author, you can have a new Docker images with the new version of your code and run it in parallel. All you have to do after that is point the traffic from the old version to the new version (By just running `docker compose`).

If you have a more complex setup, e.g. if by using Kubernetes, you can do things like run both the version at the same time, person A/B testing or have canary deployments to ensure the new version works .

Time for deployment would be most likely in seconds unless the setup is complex/convoluted.

Schema modifications are another beast. For small use cases, you could run a specialized one time container that performs the modifications, but once you need high availability, you'd have to consider a more complex approach. See https://queue.acm.org/detail.cfm?id=3300018

sbhat7 | 11 years ago | on: Raft: Understandable Distributed Consensus

To add a new node to the network, it

* needs to have the same data as the other nodes

* needs a round of Raft to notify its presence to other nodes

So you can only add new nodes (automatically) when you have a 'live' system.

majority = ceil((2n + 1)/2) : so by getting the number of available nodes in the partition, nodes can figure out if they are in the majority or minority cluster.

See section 6 in the paper for details of its implementation.

sbhat7 | 11 years ago | on: Raft: Understandable Distributed Consensus

From 9.1 section in the paper,

> Each student watched one video, took the corresponding quiz, watched the second video, and took the second quiz. About half of the participants did the Paxos portion first and the other half did the Raft portion first in order to account for both individual differences in performance and experience gained from the first portion of the study. We compared participants’ scores on each quiz to deter- mine whether participants showed a better understanding of Raft.

sbhat7 | 11 years ago | on: Raft: Understandable Distributed Consensus

> To give an example, say I have n machines in datacenter A, and n*.99 in datacenter B. datacenter A gets destroyed, permanently. Does datacenter B now reject all (EDIT: where reject = not commit) requests until a human comes along to tell it that datacenter A isn't coming back?

Of CAP, you are now choosing CP with Raft. So yes, the system is unavailable until an external agent fixes it. In other words, the system needs to have a majority of nodes online to be "available".

sbhat7 | 14 years ago | on: Hacker News Fires Steve Yegge

My friend used to work for a large multi-national. In his company, each of the departments were like companies in itself. The formalities for quitting the job and changing departments were the same. So most of the time the only way to get off a bad project was to quit the company.

sbhat7 | 15 years ago | on: How Digg is Built

Nice article. It'd be great to have some numbers that indicate the size/scale of the system and its components.
page 1