aboutsummaryrefslogtreecommitdiffstats
path: root/container-core/src/test/java/com/yahoo/container/handler/VipStatusTestCase.java
Commit message (Collapse)AuthorAgeFilesLines
* Convert container-core to junit5Bjørn Christian Seime2022-07-281-12/+10
|
* Update 2017 copyright notices.gjoranv2021-10-071-1/+1
|
* Use a name that works better for content nodesJon Bratseth2020-11-161-1/+1
|
* Add in_rotation metric to containersJon Bratseth2020-11-161-10/+52
|
* Avoid mock thread factory and simplify constructionHåkon Hallingstad2020-10-101-6/+3
|
* Take StateMonitor snapshot every 60sHåkon Hallingstad2020-10-101-3/+5
| | | | | | | | | Using Executors simplifies the code and fixes the following 2 small problems: - A tiny drift of the 1m interval: It starts the next snapshot 1m + the time before wait() return + the time until currentTimeMillis(). - May potentially (but unlikely) invoke wait() with negative (throws exception) or 0 argument (waits forever): There is no test on the returned long from currentTimeMillis().
* Add testJon Bratseth2020-07-021-57/+112
|
* Configure initially out of rotation for config serversJon Bratseth2020-03-301-22/+46
|
* Require all up when going up, but require all down to go down.Henning Baldersheim2020-02-031-25/+61
|
* Set healt status to down when we decide to go out of rotationJon Bratseth2019-02-251-7/+12
|
* When pooling ClusterMonitors and SearchClusters you will add a cluster every ↵Henning Baldersheim2018-11-151-3/+3
| | | | | | | | time there is a reconfig. As nothing will purge them, you both keep stuff alive forever and end up with more clusters that you have. Hence the magic for not removing vipstatus when there are multiple clusters kick in preventing nodes being taken OOR. Now it is using the ComponentId for identifying a cluster.
* Revert "Merge pull request #6726 from ↵Jon Bratseth2018-08-301-2/+11
| | | | | | | vespa-engine/revert-6719-bratseth/initially-down" This reverts commit 05ea4c2b9952bceaf0e009053c2f51a09d15a957, reversing changes made to 03efdabdc9f0e43fc2c362569ae455a7abc9a64b.
* Revert "Be down initially"Jon Bratseth2018-08-301-11/+2
|
* Be down initiallyJon Bratseth2018-08-291-2/+11
| | | | | | | | | | | | | | | | | | | | Before ths change containers used to come up in the initial VIP state of up ("in rotation") before having any information about downstream cløusters. This is problematic if the node determines that it should be down when learning the state of downstream clusters, especially when it is determining that it should be down due to failing to complete pings timely due to initialization load. This changes to starting in the down state. Crucially, this requires tracking the current state of clusters in a separate component such that the state survives reconfiguration and we avoid setting the state down briefly on each reconfiguration. In addition to the case where there are downstream clusters deciding the VIP state oif a container, there are two others: - There are no such clusters. In this case the VIP state will be up by default. - Some other component is explicitly deciding the VIP state. This commit makes that case clearer.
* Update copyright headersJon Bratseth2017-06-141-1/+1
|
* Revert "Update copyright headers"Jon Bratseth2017-06-141-1/+1
|
* Update copyright headersJon Bratseth2017-06-141-1/+1
|
* Revert "Copyright header"Jon Bratseth2017-06-131-1/+1
|
* Copyright headerJon Bratseth2017-06-131-1/+1
|
* PublishJon Bratseth2016-06-151-0/+42