vespa - An engine for low-latency computation over large data sets

	Commit message (Collapse)	Author	Age	Files	Lines
*	Remove config param noSearchBackendsImpliesOutOfService	gjoranv	2019-01-21	1	-8/+7
\|
*	Revert "Merge pull request #6726 from ↵	Jon Bratseth	2018-08-30	1	-53/+51
\| \| \| \| \| \| \|	vespa-engine/revert-6719-bratseth/initially-down" This reverts commit 05ea4c2b9952bceaf0e009053c2f51a09d15a957, reversing changes made to 03efdabdc9f0e43fc2c362569ae455a7abc9a64b.
*	Revert "Be down initially"	Jon Bratseth	2018-08-30	1	-51/+53
\|
*	Be down initially	Jon Bratseth	2018-08-29	1	-53/+51
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	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 headers	Jon Bratseth	2017-06-14	1	-1/+1
\|
*	Revert "Update copyright headers"	Jon Bratseth	2017-06-14	1	-1/+1
\|
*	Update copyright headers	Jon Bratseth	2017-06-14	1	-1/+1
\|
*	Revert "Copyright header"	Jon Bratseth	2017-06-13	1	-1/+1
\|
*	Copyright header	Jon Bratseth	2017-06-13	1	-1/+1
\|
*	Publish	Jon Bratseth	2016-06-15	1	-0/+220