aboutsummaryrefslogtreecommitdiffstats
path: root/clustercontroller-core
Commit message (Collapse)AuthorAgeFilesLines
* Move some of bratseths ownership to others.Geir Storli2024-02-281-1/+1
|
* Use sentinel value for missing buckets rather than throwingTor Brede Vekterli2024-01-291-1/+1
| | | | Bucket count should have been pre-verified as present by the caller.
* Explicitly report docs, tombstones and buckets in disallow-messageTor Brede Vekterli2024-01-292-26/+38
|
* Use stored entry count rather than bucket count for (dis-)allowing permanent ↵Tor Brede Vekterli2024-01-262-112/+182
| | | | | | | | | | | | | | | | | node down edge The stored entry count encompasses both visible documents and tombstones. Using this count rather than bucket count avoids any issues where a node only containing empty buckets (i.e. no actual data) is prohibited from being marked as permanently down. Entry count is cross-checked with the visible document count; if the former is zero, the latter should always be zero as well. Since entry/doc counts were only recently introduced as part of the HostInfo payload, we have to handle the case where these do not exist. If entry count is not present, the decision to allow or disallow the transition falls back to the bucket count check.
* Revert "Merge pull request #29683 from ↵jonmv2023-12-171-1/+1
| | | | | | | vespa-engine/revert-29678-jonmv/reapply-zk-3.9.1" This reverts commit c8ece8b229362c7bf725e4433ef4fec86024cd29, reversing changes made to d42b67f0fe821d122548a345f27fda7f9c9c9d10.
* Revert "Jonmv/reapply zk 3.9.1"Harald Musum2023-12-161-1/+1
|
* Revert "Merge pull request #29674 from ↵jonmv2023-12-151-1/+1
| | | | | | | vespa-engine/revert-29671-jonmv/reapply-zk-3.9.1" This reverts commit 28f8cf3e298d51ca703ceee36a992297d38637cc, reversing changes made to 3a9f89fe60e3420eed435daee435a4f8534c9512.
* Revert "Jonmv/reapply zk 3.9.1"Jon Marius Venstad2023-12-151-1/+1
|
* Revert "Merge pull request #29669 from ↵jonmv2023-12-151-1/+1
| | | | | | | vespa-engine/revert-29662-revert-29661-revert-29658-jonmv/zk-3.9.1-clients-2" This reverts commit 9c8ba2608384ee79e143babd1e5a18a62166541f, reversing changes made to 954785e4eb91286bd166c304e98042ec63b7eb84.
* Revert "Revert "Revert "Jonmv/zk 3.9.1 clients 2"""Jon Marius Venstad2023-12-151-1/+1
|
* Revert "Revert "Jonmv/zk 3.9.1 clients 2""Jon Marius Venstad2023-12-141-1/+1
|
* Revert "Jonmv/zk 3.9.1 clients 2"Harald Musum2023-12-141-1/+1
|
* Get zk-client-common through zkfacadejonmv2023-12-141-1/+1
|
* Restore original ZK embed placements, and duplicate ClientX509Util insteadjonmv2023-12-141-6/+0
|
* Depend on client and auth setup in clustercontroller-corejonmv2023-12-141-3/+3
|
* Embed ZK in zookeeper-client-commonjonmv2023-12-141-2/+8
|
* Use fake ZooKeeper database implementation for subset of CC testsTor Brede Vekterli2023-12-047-15/+184
| | | | | | The fake impl acts "as if" a single-node ZK quorum is present, so it cannot be directly used with most multi-node tests that require multiple nodes to actually participate in leader elections.
* Reduce unit test ZooKeeper WAL file preallocations by three orders of magnitudeTor Brede Vekterli2023-11-291-0/+4
| | | | | | | | | | ZK will by default preallocate 65536 * 1024 bytes for its write-ahead log file. This will happen for every test instantiation of the ZooKeeper database. Now, I like wearing out SSD flash cells as much as the next guy, but this just feels silly. Input number is always multiplied by 1024, so reduce down to 64 to get a 64k preallocation instead.
* Move Jackson util from vespajlib to container-core.Henning Baldersheim2023-11-242-2/+2
|
* jackson 2.16 changes some of its default settings so we consolidate our use ↵Henning Baldersheim2023-11-236-18/+19
| | | | | | of the ObjectMapper. Unless special options are used, use a common instance, or create via factory metod.
* Update copyrightJon Bratseth2023-10-09202-201/+203
|
* GC unused count and averageHenning Baldersheim2023-08-301-8/+0
|
* Consolidate hamcrest usage to 2.x and remove cthul-matchersBjørn Christian Seime2023-08-2910-19/+2
|
* Revert "More logging at higher level, need more info"Harald Musum2023-08-251-5/+3
|
* Add content cluster name to generated feed block messageTor Brede Vekterli2023-07-264-34/+37
| | | | | | | | | | | Messages now prefixed with content cluster name to help disambiguate which cluster is exceeding its limits in multi-cluster deployments. Example message: ``` in content cluster 'my-cool-cluster': disk on node 1 [my-node-1.example.com] is 81.0% full (the configured limit is 80.0%). See https://docs.vespa.ai/en/operations/feed-block.html ```
* Make generated automatic feed block error messages more user-friendlyTor Brede Vekterli2023-07-265-38/+60
| | | | | | | | | | | | | | | | | | Messages are generated centrally by the cluster controller and pushed to content nodes as part of a cluster state bundle; the distributors nodes merely repeat back what they have been told. This changes the cluster controller feed block error message code to be less ambiguous and to include a URL to our public documentation about feed blocks. Example of _old_ message: ``` disk on node 1 [storage.1.local] (0.510 > 0.500) ``` Same feed block with _new_ message: ``` disk on node 1 [storage.1.local] is 51.0% full (the configured limit is 50.0%). See https://docs.vespa.ai/en/operations/feed-block.html ```
* Use 'vespa.version' suffix for all global version properties.gjoranv2023-07-241-1/+1
|
* Revert "New parent pom"Arnstein Ressem2023-07-211-1/+1
|
* Merge pull request #27827 from vespa-engine/new-parent-pomgjoranv2023-07-211-1/+1
|\ | | | | New parent pom
| * Use 'vespa.version' suffix for all global version properties.gjoranv2023-07-191-1/+1
| |
* | More logging at higher level, need more infoHarald Musum2023-07-201-3/+5
|/
* Use cluster state to check if disttributors are UPHarald Musum2023-07-181-5/+4
|
* Check min replication seen from all distributors that are UPHarald Musum2023-07-172-29/+17
| | | | | This means we will also check distributors that are on same node as a retired storage node
* Fix minor issues after code reviewsHarald Musum2023-07-172-3/+1
|
* Avoid code duplicationHarald Musum2023-07-161-9/+7
|
* Check redundancy also for groups that are upHarald Musum2023-07-162-18/+106
| | | | | | | When we allow several groups to go down for maintenance we should check nodes in the groups that are up if they have the required redundancy. They might be up but have not yet synced all buckets after coming up. We want to wait with allowing more nodes to be taken down until that is done.
* Split out method for finding min replication per distributorHarald Musum2023-07-141-15/+20
|
* Separate code at a higher level based on groupes setup or notHarald Musum2023-07-111-71/+66
|
* More minor changesHarald Musum2023-07-091-22/+29
|
* Split out method to avoid repeating codeHarald Musum2023-07-091-69/+68
|
* Renames and minor refactorings, no funcational changesHarald Musum2023-07-095-258/+226
|
* SimplifyHarald Musum2023-07-092-35/+17
|
* SimplifyHarald Musum2023-07-055-16/+9
|
* Code cleanup, no functional changesHarald Musum2023-07-051-5/+4
|
* Minor refactoring and start of some new testHarald Musum2023-07-052-25/+46
|
* Depend on container-dev to ensure correct Import-Packagegjoranv2023-06-221-14/+1
|
* Replace metrics strings with the corresponding enum constants.gjoranv2023-06-223-4/+12
| | | | - Add 'metrics' as provided dep for clustercontroller-core
* Revert "Replace metrics strings with the corresponding enum constants."Harald Musum2023-06-223-12/+4
|
* Replace metrics strings with the corresponding enum constants.gjoranv2023-06-213-4/+12
| | | | - Add 'metrics' as provided dep for clustercontroller-core
* Move fetchStatusPageHarald Musum2023-06-193-42/+79
|