aboutsummaryrefslogtreecommitdiffstats
path: root/clustercontroller-apps
Commit message (Collapse)AuthorAgeFilesLines
* Add config for max number of content groups allowed to be downHarald Musum2023-03-281-0/+1
|
* Require capabilities for built-in request handlersBjørn Christian Seime2023-02-142-4/+14
|
* No need to wait until connected in cluster controllerHarald Musum2023-02-071-19/+1
| | | | | VespaZooKeeperSever now guarantees that server is working by writing a node, so no need to do an extra check in cluster controller
* StatusPageServerInterface has just one implementation, simplifyHarald Musum2022-12-281-3/+2
|
* Replace jettison with jacksonjonmv2022-10-211-5/+0
|
* Return X-Vespa-Ignored-Fields if fields were ignoredJon Bratseth2022-10-061-0/+1
|
* Remove unused config fieldHarald Musum2022-09-061-1/+0
|
* Make FleetControllerOptions immutable and support builder patternHarald Musum2022-08-313-63/+56
|
* Remove useless test that requires hacks in other placesHarald Musum2022-08-221-70/+0
| | | | | Want to require zooKeeperServerAddress and slobrokConnectionSpecs being non-null
* Revert "Cluster controller unit test cleanup, part 4 [run-systemtest]"Harald Musum2022-08-221-0/+70
|
* Remove useless test that requires hacks in other placesHarald Musum2022-08-171-70/+0
| | | | | Want to require zooKeeperServerAddress and slobrokConnectionSpecs being non-null
* Convert clustercontroller-apps to junit5Bjørn Christian Seime2022-07-297-51/+60
|
* Set project version to 8-SNAPSHOTgjoranv2022-06-081-2/+2
|
* install_jar CMake functionHåkon Hallingstad2022-05-201-1/+1
|
* Use '@Inject' from 'annotations' in multiple bundlesBjørn Christian Seime2022-05-064-4/+4
|
* Shut down ClusterController from last configurer, thus before ZKJon Marius Venstad2022-03-114-20/+52
|
* Revert "Ensure ClusterController shuts down before ZK cluster is uses"Arnstein Ressem2022-03-111-7/+1
|
* Ensure ClusterController shuts down before ZK cluster is usesJon Marius Venstad2022-03-111-1/+7
|
* Extend ThreadedHttpReqHndlr instead of deprecated LoggingReqHndlrgjoranv2022-01-173-5/+5
|
* Remove config generation -1/0 from CC at :19050/status/<clustername>/configHåkon Hallingstad2021-10-201-1/+1
|
* Update Verizon Media copyright notices.gjoranv2021-10-073-3/+3
|
* Update 2017 copyright notices.gjoranv2021-10-0712-12/+12
|
* Revert "Avoid safe mutations in master moratorium and increase first cluster ↵Håkon Hallingstad2021-03-241-14/+3
| | | | state broadcast deadline [run-systemtest]"
* Increase the minimum time before first cluster state broadcast [run-systemtest]Håkon Hallingstad2021-03-191-3/+14
|
* High graph constructino timeoutJon Marius Venstad2021-02-201-1/+1
|
* Die after 1 minute if no ZK-connection when constructing CCJon Marius Venstad2021-02-191-1/+3
|
* Merge pull request #16527 from ↵Jon Marius Venstad2021-02-163-11/+19
|\ | | | | | | | | vespa-engine/jonmv/create-only-one-cluster-controller Avoid recreation of ClusterController when config changes
| * Avoid recreation of ClusterController when config changesJon Marius Venstad2021-02-163-11/+19
| |
* | Also shut down Curator instances created during clustercontroller component ↵Jon Marius Venstad2021-02-141-2/+3
|/ | | | setup
* Support configurable feed block hysteresis on the cluster controllerTor Brede Vekterli2021-02-102-1/+4
| | | | | | | | | | | | | | | | | | | Adds an absolute number delta that is subtracted from the feed block limit when a node has a resource already in feed blocked state. This means that there's a lower watermark threshold that must be crossed before feeding can be unblocked. Avoids flip-flopping between block states. Default is currently 0.0, i.e. effectively disabled. To be modified later for system tests and trial roll-outs. A couple of caveats with the current implementation: * The cluster state is not recomputed automatically when just the hysteresis threshold is crossed, so the description will be out of date on the content nodes. However, if any other feed block event happens (or the hysteresis threshold is crossed), the state will be recomputed as expected. This does not affect correctness, since the feed is still to be blocked. * A node event remove/add pair is emitted for feed block status when the hysteresis threshold is crossed and there's a cluster state recomputation.
* Fix importHarald Musum2021-02-091-1/+1
|
* Cleanup: Remove unnecessary and unused methods, simplifyHarald Musum2021-02-082-17/+24
|
* Add cluster feed block support to cluster controllerTor Brede Vekterli2021-01-272-1/+10
| | | | | | | | | | | | | | | Will push out a new cluster state bundle indicating cluster feed blocked if one or more nodes in the cluster has one or more resources exhausted. Similarly, a new state will be pushed out once no nodes have resources exhausted any more. The feed block description currently contains up to 3 separate exhausted resources, possibly across multiple nodes. A cluster-level event is emitted for both the block and unblock edges. No hysteresis is present yet, so if a node is oscillating around a block-limit, so will the cluster state.
* Add back javadocHarald Musum2020-12-161-0/+4
|
* Inject VespaZooKeeperServer in constructorHarald Musum2020-12-161-1/+7
|
* Revert "Revert " Stop depending on ZooKeeperProvider, take 2""Harald Musum2020-12-164-48/+2
|
* Revert " Stop depending on ZooKeeperProvider, take 2"Harald Musum2020-12-164-2/+48
|
* Constructor needs to be publicHarald Musum2020-12-151-1/+1
|
* Revert "Revert "Stop depending on ZooKeeperProvider""Harald Musum2020-12-154-47/+1
|
* Revert "Stop depending on ZooKeeperProvider"Harald Musum2020-12-154-1/+47
|
* Stop depending on ZooKeeperProviderHarald Musum2020-12-154-47/+1
| | | | | | | | VespaZooKeeperServer is enough, ZooKeeperProvider is just an unnecessary extra layer. In addition neither provides any guarantee that the the server has started and is working. ClusterController has code that verifies that connecting to zookeeper works, that should be sufficient.
* Merge branch 'master' into ↵Harald Musum2020-12-141-12/+13
|\ | | | | | | hmusum/disallow-clustercontroller-with-no-zookeeper-cluster
| * Use CuratorFramework.blockUntilConnected() to verify connectionHarald Musum2020-12-141-6/+2
| |
| * Refactor code and document code to verify that ZooKeeper is workingHarald Musum2020-12-141-12/+17
| |
* | Remove unnecessary argumentHarald Musum2020-12-143-18/+18
| |
* | Disallow creating a cluster controller having no zookeeper clusterHarald Musum2020-12-142-28/+8
|/
* Revert "Remove code that nobody understands the need for"Arnstein Ressem2020-12-091-2/+11
|
* Remove code that nobody undrstands the need forHarald Musum2020-12-081-11/+2
| | | | | | Cannot find any usage of nodes created. This might be some initialization code to check if operations work, but I cannot see the need for it. If this breaks something we can at least document why this is needed.
* Move code in clustercontroller-apputils into clustercontroller-appsHarald Musum2020-12-016-6/+278
| | | | | Code in clustercontroller-apputils is now only used from clustercontroller-apps, so those two modules can be merged
* Rename methodHarald Musum2020-11-181-1/+1
|