summaryrefslogtreecommitdiffstats
path: root/clustercontroller-core
Commit message (Collapse)AuthorAgeFilesLines
* Add non-converged nodes to task deadline exceeded messagesTor Brede Vekterli2019-11-046-26/+142
| | | | | Makes it easier for an external observer to understand what set of nodes is causing the cluster state to not converge.
* Pass working candidate state rather than published state to timer codeTor Brede Vekterli2019-10-301-2/+3
| | | | | | | Avoids triggering pointless cluster state recomputation edges because the timer code observes stale information. This can happen if publishing the candidate state is suppressed due to e.g. the minimum time between published state versions not having passed.
* Move grace period event edge from timer to event diff calculatorTor Brede Vekterli2019-10-309-25/+103
| | | | | | | | Ensures that event is only emitted when we're actually publishing a state containing the state transition. Emitting events in the timer code is fragile when it does not modify any state, risking emitting the same event an unbounded amount of times if the condition keeps holding for each timer cycle.
* Use mockito-core 3.1.0Håkon Hallingstad2019-10-1816-35/+47
|
* Revert "Reapply "upgrade to zookeeper 3.5""Harald Musum2019-09-272-24/+9
|
* Revert "Revert "Hmusum/upgrade to zookeeper 3.5""Harald Musum2019-09-242-9/+24
|
* Revert "Hmusum/upgrade to zookeeper 3.5"Harald Musum2019-09-172-24/+9
|
* Add spotbugs dep to clustercontroller-core.gjoranv2019-09-101-0/+7
| | | | + Use version property for zk in parent pom
* Don't use import wildcards.gjoranv2019-09-101-9/+17
|
* Cleanup tests, no functional changesHarald Musum2019-09-0357-457/+384
|
* Guard critical cluster state version ZK writes with an atomic CaSTor Brede Vekterli2019-07-115-68/+170
| | | | | | | | | Lets a controller discover that another controller also believes it is the leader by tracking the expected znode versions for cluster state version and bundle znodes. If a CaS failure is triggered, the controller will drop its database and election state, forcing a state refresh.
* Do not allow states to be published when they have pending ZK writesTor Brede Vekterli2019-07-052-0/+15
| | | | | | Avoids a race condition where a bundle ZK write fails but we have not yet detected that ZK connectivity has been lost. This could lead to violating the invariant that published state versions are strictly increasing.
* Don't use fake timers for master election testsTor Brede Vekterli2019-06-201-14/+14
| | | | | | | | When using fake timers there's a catch-22 edge case during transient ZooKeeper disconnects. The test will not progress and increase the fake timer value until ZK is connected, but ZK will not attempt to reconnect until the reconnection cooldown period has passed (which depends on the faked timer).
* Increase ZK client session timeout from 10s to 30sTor Brede Vekterli2019-06-191-1/+1
| | | | | | | | Have a suspicion that 10s ends up being too short when ZK's write-ahead log flushing is taking a long time due to a heavily loaded CI container. Should still be short enough for a network hiccup to hopefully trigger a reconnect before the test itself times out.
* Reduce ZK session timeout for master election unit testsTor Brede Vekterli2019-06-171-4/+4
| | | | | | | | | Setup methods would previously override explicit timeouts set by the tests with a default of 2 minutes. It's suspected that this long timeout combined with spurious ZK client failures is a source of test failures. Reduce to 10 seconds for now. Let's see how well it fares on a heavily loaded CI container.
* Keep the spec final.Henning Baldersheim2019-05-281-1/+1
| | | | | | Create the address when needed in the async connect thread. Implement hash/equal/compareTo for Spec to avoid toString. Use Spec as key and avoid creating it every time.
* Remove usage of deprecated Method constructorBjørn Christian Seime2019-05-232-21/+21
|
* mockito-all => mockito-coreHenning Baldersheim2019-04-291-1/+1
|
* Change interface from Mirror.Entry[] to List<Mirror.Entry> as you already ↵Henning Baldersheim2019-04-221-4/+9
| | | | | | have a list. Avoid having to do an array copy that is not necessary.
* Address code review feedback for cluster controller changesTor Brede Vekterli2019-03-263-36/+42
|
* Work around some Java generics snags in test mocksTor Brede Vekterli2019-03-221-0/+7
|
* Activation reply processing must inspect actual version returnedTor Brede Vekterli2019-03-2113-35/+113
| | | | | | | | Version mismatches in backend do not return explicit RPC errors, so actual vs. desired versions must be checked in order to avoid potentially spurious activation of other versions. Also do some minor code cleanup.
* Add activated state version to node status page rowTor Brede Vekterli2019-03-204-10/+18
| | | | | Only displayed if not equal to published state version and if two-phase transitions are enabled.
* Break rendering MegaFunction(tm) into separate functionsTor Brede Vekterli2019-03-201-112/+142
|
* Explicitly enable two-phase transitions in tests, disable in default optionsTor Brede Vekterli2019-03-2016-70/+80
| | | | Mirrors the default values in the actual underlying config definitions.
* Add explicit tests of `SystemStateBroadcaster` behaviorTor Brede Vekterli2019-03-202-14/+177
|
* Bring default state of ClusterStateBundle deferred activation flag in line ↵Tor Brede Vekterli2019-03-204-25/+21
| | | | | | | with C++ impl I.e. disabled by default. Also reduce log level for logging used during development.
* Print deferred activation flag in `ClusterStateBundle.toString`Tor Brede Vekterli2019-03-152-4/+36
|
* Bind deferred activation decision to concrete bundle instance, not global configTor Brede Vekterli2019-03-155-9/+38
| | | | Ensure that deferred activation flags are propagated during building and cloning.
* Support configurable two-phase state transitions in cluster controllerTor Brede Vekterli2019-03-1416-108/+382
|
* Initial groundwork for cluster state version activation RPCTor Brede Vekterli2019-03-1410-62/+206
|
* Include deferred activation flag with cluster state bundlesTor Brede Vekterli2019-03-147-18/+114
| | | | | | | Bundles including this flag from the cluster controller indicate to receiver nodes that an explicit activation RPC will follow. When it is not present, nodes must activate the cluster state at their own leisure as they have done historically.
* Reduce log spamHåkon Hallingstad2019-01-221-3/+4
|
* 6-SNAPSHOT -> 7-SNAPSHOTArnstein Ressem2019-01-211-2/+2
|
* Remove experimental enable-multiple-bucket-spaces flag.Geir Storli2018-11-233-14/+3
| | | | The feature has been default on since late May 2018.
* Revert "Revert "Revert "Revert "Enforce CC timeouts in Orchestrator 4""""Håkon Hallingstad2018-11-015-21/+64
|
* Revert "Revert "Revert "Enforce CC timeouts in Orchestrator 4"""Håkon Hallingstad2018-11-015-64/+21
|
* Revert "Revert "Enforce CC timeouts in Orchestrator [4]""Håkon Hallingstad2018-11-015-21/+64
|
* Revert "Enforce CC timeouts in Orchestrator [4]"Harald Musum2018-10-315-64/+21
|
* Revert "Revert "Revert "Revert "Enforce CC timeouts in Orchestrator 2""""Håkon Hallingstad2018-10-305-21/+64
|
* Revert "Revert "Revert "Enforce CC timeouts in Orchestrator 2"""Håkon Hallingstad2018-10-305-64/+21
|
* Revert "Revert "Enforce CC timeouts in Orchestrator 2""Håkon Hallingstad2018-10-295-21/+64
|
* Revert "Enforce CC timeouts in Orchestrator 2"Håkon Hallingstad2018-10-295-64/+21
|
* Fixes after review roundHåkon Hallingstad2018-10-261-1/+1
|
* set-node-state probing in CCHåkon Hallingstad2018-10-245-21/+64
|
* Minor fixesJon Bratseth2018-10-142-38/+39
|
* Add copyright headerJon Bratseth2018-10-012-0/+2
|
* set-node-state timeout in CCHåkon Hallingstad2018-06-226-5/+45
|
* Warn on timeoutHåkon Hallingstad2018-06-151-1/+1
|
* Do not wait for version ack for failed set-node-stateHåkon Hallingstad2018-06-135-6/+82
|