| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|\
| |
| |
| |
| | |
vespa-engine/vekterli/invalidate-min-replica-stats-on-recovery-mode-entry
Invalidate bucket DB replica statistics upon recovery mode entry [run-systemtest]
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
bundles
If an application uses deferred cluster state activations, do not report
back a given cluster state version as being in use by the node until the
state version has been explicitly activated by the cluster controller.
This change is due to the fact that the replication invalidation happens
upon recovery mode entry, and for deferred state bundles this takes place
when a cluster state is _activated_, not when the distributor is otherwise
done gathering bucket info (for a non-deferred bundle the activation happens
implicitly at this point). If the state manager reports that the new cluster
state is in effect even though it has not been activated, the cluster
controller could still end up using stale replication stats, as the invalidation
logic has not yet run at this point in time.
The cluster controller will ignore any host info responses for older
versions, so any stale replication statistics should not be taken into
account with this change.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The replica stats track the minimum replication factor for any bucket
for a given content node the distributor maintains buckets for. These
statistics may be asynchronously queried by the cluster controller
through the host info reporting API.
If we do not invalidate the statistics upon a cluster state change, there
is a very small window of time where the distributor may potentially
report back _stale_ statistics that were valid for the _prior_ cluster
state version but not for the new one. This can happen if the cluster
controller fetches host info from the node in between start of the recovery
period and the completion of the recovery mode DB scan. Receiving stale
replication statistics may cause the cluster controller to erroneously
believe that replication due to node retirements etc has completed earlier
than it really has, possibly impacting orchestration decisions in a sub-
optimal manner.
|
|\ \
| | |
| | | |
Avoid deprecated APIs
|
| |/ |
|
|\ \
| | |
| | |
| | |
| | | |
vespa-engine/geirst/use-unset-entry-ref-that-matches-invalid-entry-ref
Use zero as unset entry ref as that matches an invalid entry ref.
|
| | |
| | |
| | |
| | | |
The previous value was within the range of valid entry refs and we could (very rarely) consider a set entry ref to not being set.
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
vespa-engine/toregge/avoid-illegal-char-sequence-in-debug-log
Avoid illegal character sequence in debug log.
|
| | | | |
|
|\ \ \ \
| |_|_|/
|/| | | |
Arnej/feature flag for user agents
|
| |\ \ \
| |/ / /
|/| | |
| | | |
| | | |
| | | | |
Conflicts:
config-model-api/src/main/java/com/yahoo/config/model/api/ModelContext.java
configserver/src/main/java/com/yahoo/vespa/config/server/deploy/ModelContextImpl.java
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
vespa-engine/revert-20609-mortent/developer-role-manual-deploy
Revert "Allow developers to deploy application in manual zones"
|
|/ / / / |
|
|\ \ \ \
| | | | |
| | | | | |
Deprecate the 'service' element in services.xml
|
| | | | | |
|
|\ \ \ \ \
| |_|_|/ /
|/| | | | |
Simplify MockConnection
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
No need to use thread, start() isn't called anyway.
Collapse methods into one to simplify
|
|\ \ \ \ \
| |_|_|_|/
|/| | | |
| | | | |
| | | | | |
vespa-engine/hmusum/deprecated-get-and-set-config-md5
Deprecate getConfigMd5() and setConfigMd5() [run-systemtest]
|
| |/ / /
| | | |
| | | |
| | | |
| | | | |
We don't use md5 checksum for config anymore, methods will be removed
in Vespa 8.
|
|\ \ \ \
| | | | |
| | | | | |
Allow developers to deploy application in manual zones
|
| | | | | |
|
|\ \ \ \ \
| | | | | |
| | | | | | |
Add feature flag for OCSP Stapling on application container clusters
|
| | | | | | |
|
| | | | | | |
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
vespa-engine/mortent/routing-enable-reuseport-default
Enable reuseport by default
|
| | |_|/ / /
| |/| | | | |
|
|\ \ \ \ \ \
| |/ / / / /
|/| | | | | |
Add helper method for synchronous use of feed client
|
| | | | | | |
|
| | | | | | |
|
| |_|_|_|/
|/| | | | |
|
|\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
vespa-engine/revert-20622-hmusum/add-logging-when-file-not-found
Revert "Add some logging to debug issue sometimes seen when running system tests"
|
|/ / / / /
| | | | |
| | | | |
| | | | | |
tests"
|
|\ \ \ \ \
| | | | | |
| | | | | | |
decouple tests by giving them separate destination session names
|
|/ / / / / |
|
|\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
vespa-engine/hmusum/add-logging-when-file-not-found
Add some logging to debug issue sometimes seen when running system tests
|
|/ / / / / |
|
|\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
vespa-engine/hmusum/dots-should-be-allowed-in-jvm-options
Allow dots in JVM options
|
|/ / / / / |
|
|\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
vespa-engine/vekterli/swallow-internal-replies-at-top-storage-link
Let CommunicationManager swallow any errant internal reply messages [run-systemtest]
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
It's possible for internal commands to have replies auto-generated
if they're being evicted/aborted from persistence queue structures.
Most of these replies are intercepted by higher-level links in the
storage chain, but commands such as `RunTaskCommand` are actually
initiated by the persistence _provider_ and not a higher level component,
and are therefore not caught explicitly anywhere.
Let CommunicationManager signal that internal replies are handled,
even if the handling of these is just to ignore them entirely. This
prevents the replies from being spuriously warning-logged as "unhandled
message on top of call chain".
|
| | | | | | |
|
|\ \ \ \ \ \
| |/ / / / /
|/| | | | | |
Jonmv/fix metric for doc v1
|
| | | | | | |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
vespa-engine/revert-20616-jonmv/filter-when-create-true"
This reverts commit 2fd7739b9fa7ce3283d1485dae3726c8e8ec882b, reversing
changes made to 7ef261d471f4a11651811957b2f24bb7e0bcf4d5.
|
|\ \ \ \ \ \
| |/ / / / /
|/| | | | | |
optimize tensor create by making the index up front...
|
| | | | | | |
|
| | |_|_|/
| |/| | | |
|
|\ \ \ \ \
| | | | | |
| | | | | | |
sparse 112 dot product
|
| | | | | | |
|