| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
Created by command:
/usr/bin/tito tag --use-version=7.305.19 --no-auto-changelog
|
|\
| |
| |
| |
| | |
vespa-engine/geirst/feed-bm-async-message-handling-option
Add option to turn on use_async_message_handling_on_schedule.
|
| | |
|
| | |
|
|\ \
| |/
|/| |
Add support for registry credentials in container engine
|
| | |
|
| | |
|
|\ \
| | |
| | |
| | |
| | | |
vespa-engine/arnej/duplicate-instruction-benchmark
partial duplicate of micro-bemchmark
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
* use conditional compilation to let the installed
vespa-tensor-instructions-benchmark run its
measurements only for the two most important
implementations (old prod and new prod).
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
vespa-engine/geirst/async-message-handling-on-schedule
Add support for async message handling when scheduling storage messag…
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
FileStorManager.
When turned on, the calling thread (e.g. FNET network thread when using Storage API RPC)
gets the next async message to handle (if any) as part of scheduling a storage message.
This async message is then handled by the calling thread immediately,
instead of going via a persistence thread.
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
vespa-engine/vekterli/avoid-mergehandler-spam-log-level-crash
Don't try to access container element prior to adding it when spam logging
|
| | | | | |
|
|\ \ \ \ \
| | | | | |
| | | | | | |
Drop immediate commit, as it is gone.
|
| | |_|_|/
| |/| | | |
|
|\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
vespa-engine/jonmv/account-for-first-production-zone-having-a-newer-version-than-change-when-computing-idle-test-job-runs
Fix corner case for system/staging test jobs
|
| | | | | | |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
This fixes a corner case where we compute versions to run in system and staging tests, where the first production deployment used to compute the versions has a newer platform that what we are deploying — this confused the algorithm into believing it needed both a run which was a success both on the deploying change, AND on the newer version, which is obviously impossible. When a newer version exists in the production deployment, this is now used instead of, not in addition to, the deploying change.
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
Add ticket creation functionality to HostRepairClient
|
| | |_|_|_|/
| |/| | | | |
|
|\ \ \ \ \ \
| |/ / / / /
|/| | | | |
| | | | | |
| | | | | | |
vespa-engine/lesters/revert-revert-resolve-onnx-model-types
Lesters/revert revert resolve onnx model types
|
| | | | | | |
|
|/ / / / /
| | | | |
| | | | |
| | | | | |
This reverts commit 882d574ab53e8d10a2a8765a64487c20661dc63f.
|
|\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
vespa-engine/revert-15010-lesters/resolve-onnx-model-types
Revert "Add type resolving for ONNX models"
|
|/ / / / / |
|
|\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
vespa-engine/bratseth/avoid-allocating-invalid-nodes
Bratseth/avoid allocating invalid nodes
|
| | | | | | |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
This will never happen now, but I think it's clearer to show that
explicitly in the code.
|
|\ \ \ \ \ \
| |_|/ / / /
|/| | | | |
| | | | | |
| | | | | | |
vespa-engine/bratseth/dont-autoscale-during-a-deployment
Don't autoscale if a deployment is ongoing
|
|/ / / / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This avoids trying to do another rescaling (which will fail on activate)
if a deployment is already ongoing, for example if another config server
has already decided to autoscale.
|
|\ \ \ \ \
| |/ / / /
|/| | | | |
Create maintainer tracking host repair status
|
| | | | |
| | | | |
| | | | |
| | | | | |
unnecessary JsonIgnore. Reverse String comparison
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Extended ZmsClient to add/delete policy rules
Extended controller's node repo client with patchNode function
|
|\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
vespa-engine/bratseth/continue-suggesting-on-lock-failure
Continue suggesting on lock failure
|
| | | | | | |
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
Add type resolving for ONNX models
|
| | | | | | | |
|
|\ \ \ \ \ \ \
| |_|/ / / / /
|/| | | | | |
| | | | | | |
| | | | | | | |
vespa-engine/jonmv/remove-logging-in-doc-v1-on-errors
Destroy async session during shutdown
|
| | | | | | | |
|
|\ \ \ \ \ \ \
| |_|_|_|_|/ /
|/| | | | | |
| | | | | | |
| | | | | | | |
vespa-engine/vekterli/use-content-node-btree-db-by-default
Use content node B-tree bucket database by default
|
| | | | | | | |
|
|\ \ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
Do not add applications nodes outside cluster in NodePrioritizer
|
| | | | | | | | |
|
| | |_|_|_|/ /
| |/| | | | | |
|
|\ \ \ \ \ \ \
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
vespa-engine/ogronnesby/use-node-repo-for-quota-usage
Get quota usage from node repository
|