summaryrefslogtreecommitdiffstats
path: root/clustercontroller-core
Commit message (Collapse)AuthorAgeFilesLines
* Merge pull request #16494 from ↵Håkon Hallingstad2021-02-123-14/+55
|\ | | | | | | | | vespa-engine/hakonhall/also-deny-maintenance-when-another-node-is-in-maintenance Also deny maintenance when another node is in maintenance
| * Add testHåkon Hallingstad2021-02-122-11/+49
| |
| * Also deny maintenance when another node is in maintenanceHåkon Hallingstad2021-02-122-4/+7
| | | | | | | | | | | | | | The cluster controller today already denies setting a node X safely to maintenance M, if there is another node Y in another group that has wanted state M. Which means that if Y is in M but wanted state is not M, X is allowed to be set in M. This is an edge case which is rare.
* | enableSmallBuffers -> useSmallBuffersHenning Baldersheim2021-02-122-2/+2
| |
* | Use small buffers where size matters more than speed.Henning Baldersheim2021-02-122-2/+3
| |
* | Support configurable feed block hysteresis on the cluster controllerTor Brede Vekterli2021-02-108-11/+171
|/ | | | | | | | | | | | | | | | | | | 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.
* Cleanup: Remove unnecessary and unused methods, simplifyHarald Musum2021-02-088-68/+45
|
* Minor cleanup, no functional changesHarald Musum2021-02-089-62/+44
|
* Add extra row under content node if it's blocking feedTor Brede Vekterli2021-02-082-0/+37
| | | | List all resource exhaustions for node, including enum store etc.
* Merge pull request #16424 from ↵Geir Storli2021-02-087-30/+226
|\ | | | | | | | | vespa-engine/geirst/resource-usage-metrics-in-cluster-controller Add and expose resource usage metrics from the cluster controller.
| * Nodes above limit should only count each node once.Geir Storli2021-02-082-2/+16
| |
| * Add and expose resource usage metrics from the cluster controller.Geir Storli2021-02-057-30/+212
| |
* | Show feed block options on cluster controller status pageTor Brede Vekterli2021-02-051-0/+7
|/
* Add resource usage per node to cluster controller status pageTor Brede Vekterli2021-02-043-1/+56
| | | | | Also adds top-level cluster feed block status. Does not yet make enum store/multivalue limit feed blocks visible per node.
* Emit node-level events when resource exhaustion set changesTor Brede Vekterli2021-02-039-44/+138
|
* Recompute cluster state if set of resource exhaustions changesTor Brede Vekterli2021-02-026-18/+127
| | | | | Ensures that feed block description pushed to nodes is updated as further resource exhaustions are recorded (or disappear).
* Add hostname to resource exhaustion descriptionTor Brede Vekterli2021-01-295-19/+58
| | | | Hostname is inferred from the node's RPC address
* Support optional resource usage name fieldTor Brede Vekterli2021-01-296-24/+84
| | | | | If present, will be reported alongside the resource type in the feed block description string.
* add maybePublishOldMetrics hookArne Juul2021-01-281-0/+16
|
* Add cluster feed block support to cluster controllerTor Brede Vekterli2021-01-2715-4/+583
| | | | | | | | | | | | | | | 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.
* Dummy change to trigger systemtestHåkon Hallingstad2021-01-211-1/+0
|
* Allows setting a node safely to maintenance in these two new circumstances:Håkon Hallingstad2021-01-218-56/+302
| | | | | | | | | | | | | 1. The node has state MAINTENANCE with (user) wanted state UP. 2. There are other nodes in the same hierarchical group that are set in MAINTENANCE with the same description. Also made the following change. 3. Deny a request for safe MAINTENANCE or DOWN, if the wanted state is already set but with a different description. If the descriptions are the same, it is assumed to be the same operator (e.g. Orchestrator) having changed its mind.
* Support group maintenance [run-systemtest]Håkon Hallingstad2021-01-196-25/+216
|
* Add feed block propagation to ClusterStateBundle in JavaTor Brede Vekterli2021-01-154-19/+173
| | | | | | Fully forwards and backwards compatible. Currently only supports indicating feed blocked status for the entire cluster, with one associated descriptive message intended to be used by distributors.
* Change isMaster to updateMasterStateOla Aunrønning2021-01-042-2/+2
|
* Always set 'is-master' metric. Remove 'master-change'Ola Aunrønning2021-01-042-10/+3
|
* Track explicitly when we are initializing configJon Bratseth2020-12-161-1/+3
|
* Remove code in StatusPageServer, keep some inner classes temporarilyHarald Musum2020-11-194-655/+14
|
* SimplifyHarald Musum2020-11-193-13/+16
|
* Rename methodHarald Musum2020-11-181-18/+9
|
* Remove unused methodHarald Musum2020-11-181-11/+3
|
* Add back @Ignore and add timeout for testsHarald Musum2020-10-021-0/+5
|
* CleanupHarald Musum2020-10-023-44/+33
|
* Name the transport threads to understand how things are interconnected.Henning Baldersheim2020-08-043-3/+3
|
* use fixed port for rebinding testArne Juul2020-07-061-1/+1
|
* Downgrade log level when node watch races with internal state resetsTor Brede Vekterli2020-05-051-1/+4
| | | | | | | This appears to happen if pending data node watches are triggered with failures after the cluster controller has already reset the internal voting state due to connectivity issues. Internal state is rebuilt automatically, so no need to scream errors into the logs for this.
* Add dependency to vespalog (directly used by these modules)gjoranv2020-04-261-1/+7
|
* Use correct log Level class where search & replace has failed.gjoranv2020-04-251-1/+1
|
* Replace remaining LogLevel.<level> with corresponding Levelgjoranv2020-04-255-16/+16
|
* Map remaining DEBUG/SPAM/ERROR/FATAL -> Level.FINE/FINEST/SEVEREgjoranv2020-04-255-9/+9
|
* LogLevel -> Level for isLoggable()gjoranv2020-04-253-9/+9
|
* LogLevel.ERROR -> Level.SEVEREgjoranv2020-04-253-8/+8
|
* LogLevel.WARNING -> Level.WARNINGgjoranv2020-04-2510-32/+32
|
* LogLevel.INFO -> Level.INFOgjoranv2020-04-2513-80/+80
|
* LogLevel.SPAM -> Level.FINESTgjoranv2020-04-259-14/+14
|
* LogLevel.DEBUG -> Level.FINEgjoranv2020-04-2517-146/+146
|
* Import java.util.logging.Level instead of com.yahoo.log.LogLevelgjoranv2020-04-2524-24/+24
|
* Merge branch 'master' into hakonhall/remove-use-bucket-space-metric-feature-flagHåkon Hallingstad2020-04-201-2/+3
|\
| * Increase ZooKeeper test server tick timeTor Brede Vekterli2020-03-271-2/+3
| | | | | | | | | | | | | | | | | | | | Tests running under heavy concurrent CI build load appear to struggle maintaining ZK sessions, causing flakiness. This is an attempt to mitigate that by bumping the ZK server's tick interval (and therefore session timeout) by 20x. According to local testing, this does not increase testing time in the common case.
* | Remove stray parameter docHåkon Hallingstad2020-01-271-4/+2
| |