summaryrefslogtreecommitdiffstats
path: root/flags
Commit message (Collapse)AuthorAgeFilesLines
* Revert "Revert "Change default value for start-and-stop-vespa-with-yinst to ↵Harald Musum2019-11-181-1/+1
| | | | false""
* Revert "Change default value for start-and-stop-vespa-with-yinst to false"Harald Musum2019-11-181-1/+1
|
* Change default value for start-and-stop-vespa-with-yinst to falseHarald Musum2019-11-181-1/+1
|
* Merge pull request #11300 from ↵Andreas Eriksen2019-11-151-13/+0
|\ | | | | | | | | vespa-engine/andreer/remove-direct-routing-feature-flags remove direct routing feature flags
| * remove direct routing feature flagsandreer2019-11-141-13/+0
| |
* | Change default major.minor version for ZooKeeper servers to 3.5Harald Musum2019-11-151-1/+1
| |
* | Merge pull request #11284 from ↵Håkon Hallingstad2019-11-141-0/+6
|\ \ | | | | | | | | | | | | vespa-engine/hakonhall/allow-overriding-noderepositorymaintenance-durations-with-flag Add flag to control reboot interval
| * | Read reboot-interval-in-days dynamicallyHåkon Hallingstad2019-11-131-2/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | But also: Changes the distribution of the scheduling past 1x reboot interval: hosts will be scheduled for reboot evenly distributed in the whole 1x-2x range, and is by this guaranteed to be scheduled at latest at 2x. The expected time before a reboot was scheduled was 1.33 reboot intervals, while there was no guarantee of an upper time. The new algorithm has an expected time before reboot of 1.5 reboot intervals, bound to 2x. The old would have a higher probability of reboot passing the 1x boundary, while a lower probability than the new as one nears 2x. So I think the new algorithm also have the nice property of avoiding thundering herd, perhaps even more so than the old: For instance when most hosts are rebooted at the same time in a zone, they would tend to be rescheduled for reboot closer to each other with the old than with the new. And, enabling the new algoritm should also not lead to too many hosts suddenly having to reboot, or at least that's what I hope. I can sanity-check this before merge - I guess it would be dominated by the number of hosts in west/east that are beyond 2x.
| * | Make flag only for NodeRebooter, and remove fetching from environmentHåkon Hallingstad2019-11-133-81/+3
| | |
| * | Allow overriding NodeRepositoryMaintenance durations with flagHåkon Hallingstad2019-11-133-0/+83
| | |
* | | Change feature flag for tls for ZooKeeper quorum communication to be a stringHarald Musum2019-11-141-3/+3
| |/ |/|
* | Add feature flag for using TLS for zk quorum communicationHarald Musum2019-11-131-0/+6
|/
* Add feature flag for deciding if vespa should be started and stopped with yinstHarald Musum2019-11-051-0/+6
|
* Add application id and hostname as dimensions for ↵Harald Musum2019-10-291-1/+1
| | | | ZOOKEEPER_SERVER_MAJOR_MINOR_VERSION
* Merge pull request #11138 from vespa-engine/mpolden/remove-flagMartin Polden2019-10-291-6/+0
|\ | | | | Remove use-internal-zts flag
| * Remove use-internal-zts flagMartin Polden2019-10-281-6/+0
| |
* | Merge pull request #11140 from ↵Håkon Hallingstad2019-10-281-1/+1
|\ \ | | | | | | | | | | | | vespa-engine/hmusum/use-node-type-as-flag-dimension Use node type as flag dimension
| * | Use node type as flag dimensionHarald Musum2019-10-281-1/+1
| |/
* | Merge pull request #11139 from vespa-engine/mpolden/remove-endpoints-flagBjørn Christian Seime2019-10-281-6/+0
|\ \ | | | | | | Remove multiple-global-endpoints flag
| * | Remove multiple-global-endpoints flagMartin Polden2019-10-281-6/+0
| |/
* / Remove 'configserver-rpc-authorizer' feature flagBjørn Christian Seime2019-10-281-5/+0
|/
* Use major.minor as flag value and rename flagHarald Musum2019-10-251-3/+3
|
* Add feature flag for zookeeper versionHarald Musum2019-10-251-0/+6
|
* Use withX instead of setXHåkon Hallingstad2019-10-232-9/+9
|
* Make fluent-style paramsHåkon Hallingstad2019-10-232-16/+24
|
* Revert "Revert "Support flag conditions based on Vespa release ""Håkon Hallingstad2019-10-2314-54/+339
|
* Revert "Support flag conditions based on Vespa release "Harald Musum2019-10-2314-339/+54
|
* Merge pull request #11037 from ↵Håkon Hallingstad2019-10-2314-54/+339
|\ | | | | | | | | vespa-engine/hakonhall/support-flag-conditions-based-on-vespa-release Support flag conditions based on Vespa release
| * Document HOSTNAME and make factoriesHåkon Hallingstad2019-10-228-25/+37
| |
| * Update flags/src/main/java/com/yahoo/vespa/flags/json/Condition.java Håkon Hallingstad2019-10-221-1/+1
| | | | | | | | | | Use equalsIgnoreCase Co-Authored-By: Valerij Fredriksen <freva@users.noreply.github.com>
| * Support flag conditions based on Vespa releaseHåkon Hallingstad2019-10-2214-50/+323
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Supports a "relational" condition with a new dimension "vespa-version", that can be satisfied with e.g. "predicate": ">= 7.120.5" as long as the condition is evaluated in a JVM that has a Vtag at least high as 7.120.5. The typical use-case for this condition would be: The developer has used the flag to test and verify the feature is ready to roll out globally. The developer can now roll the feature with the next release, and ORCHESTRATED, halting if anything goes wrong like any normal rollout. This also allows one-shot tests of a feature flag in integration tests: Just enable it for an upcoming version with predicate "== 7.x.y".
* | Use mockito-core 3.1.0Håkon Hallingstad2019-10-182-3/+3
|/
* Move FlagRepository to flagsValerij Fredriksen2019-10-111-0/+13
|
* Remove unused feature flagsBjørn Christian Seime2019-10-101-12/+0
|
* Update flag definition of include-sis-in-truststoreHåkon Hallingstad2019-10-071-3/+8
|
* Add 'nginx-upstream-keepalive-multiplier' feature flagBjørn Christian Seime2019-10-021-0/+6
|
* Remove 'dynamic-upstream-connection-cache' flagBjørn Christian Seime2019-10-021-5/+0
|
* Merge pull request #10803 from ↵Håkon Hallingstad2019-09-301-0/+6
|\ | | | | | | | | vespa-engine/hakonhall/make-filesnapshot-for-repeated-reads Make FileSnapshot for repeated reads
| * Define flag to include SIS certificate in host-admin truststoreHåkon Hallingstad2019-09-271-0/+6
| |
* | flag for using internal ztsMorten Tokle2019-09-241-0/+6
| |
* | Merge pull request #10769 from vespa-engine/hmusum/remove-feature-flagHarald Musum2019-09-231-5/+0
|\ \ | | | | | | Remove feature flag USE_DEDICATED_NODE_FOR_LOGSERVER
| * | Remove feature flag USE_DEDICATED_NODE_FOR_LOGSERVERHarald Musum2019-09-231-5/+0
| | | | | | | | | | | | | | | Make useDedicatedNodeForLogserver be a default implmentation that returns true. This is just to remove the feature flag, more work needed to update tests etc.
* | | Add application id as filter dimensionBjørn Christian Seime2019-09-231-1/+2
| | |
* | | Add feature flag to control port for load balancer health checksBjørn Christian Seime2019-09-231-0/+5
|/ /
* / Add feature flag for controlling upstream connection cacheBjørn Christian Seime2019-09-231-0/+5
|/
* Merge pull request #10758 from vespa-engine/balder/remove-fdispatch-flagHenning Baldersheim2019-09-231-12/+0
|\ | | | | Fdispatch is now gone - no mor eneed for this flag.
| * Clean up the dispatch protobuf flag too.Henning Baldersheim2019-09-221-6/+0
| |
| * Fdispatch is now gone - no mor eneed for this flag.Henning Baldersheim2019-09-211-6/+0
| |
* | Remove 'use-https-load-balancer-upstream' feature flagBjørn Christian Seime2019-09-201-6/+0
|/
* Remove default-resources feature flagValerij Fredriksen2019-09-191-8/+0
|