Matt Jaffee 48af3adc21 add degraded cluster state and handle node failure ... cluster is in degraded state when some number of nodes greater than 0 but less than replicaN have failed. This is sort of a hybrid of "STARTING" and "NORMAL" states because we can still respond to queries as in the NORMAL state, but we need to be alert to re-add nodes to the cluster if they come back online which required some changes to the cluster logic. In order to make debugging easier, the test.MustRunCluster functionality now names the nodes in the cluster explicitly as "node0", "node1", etc. "node0" is the coordinator. A number of TODOs are left in the test for scenarios that need to be checked.		2018-08-06 11:57:24 -05:00
..
cluster.go	remove the last usages of test.NewExecutor and cleanup unused in test package	2018-07-01 07:31:31 -05:00
field.go	Fix linter issues: unparam	2018-07-17 12:05:07 -05:00
handler.go	remove the last usages of test.NewExecutor and cleanup unused in test package	2018-07-01 07:31:31 -05:00
holder.go	Fix linter issues: gosimple	2018-07-20 09:06:43 -05:00
index.go	update parser to handle row keys on SetRowAttrs()	2018-07-27 10:50:04 -05:00
logger.go	Unexport test.BufferLogger	2018-07-05 23:11:56 -05:00
pilosa.go	add degraded cluster state and handle node failure	2018-08-06 11:57:24 -05:00
pilosa_test.go	Fix linter issues: ineffassign	2018-07-18 14:02:56 -05:00