| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|\
| |
| |
| |
| | |
vespa-engine/vekterli/install-abseil-failure-handler
Install Abseil failure signal handler in distributor/proton daemons
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This will attempt to dump a stack trace for the offending thread
to stderr, which greatly improves visibility for everyone running
Vespa on systems with core dumps disabled.
Signal handler chaining is explicitly enabled to allow sanitizer
handlers to be called as expected.
Note that we install our own signal handlers _after_ the Abseil
handlers to avoid noisy stack dumping on `SIGTERM`. It is considered
a fatal signal by the failure handler, but the config sentinel
uses it as a friendly "please shutdown now, or else" nudge in the
common case.
|
|\ \
| | |
| | |
| | |
| | | |
vespa-engine/toregge/improve-error-message-when-field-cannot-have-attribute-aspect
Improve error message when field cannot have attribute aspect.
|
| | | |
|
| | | |
|
|\ \ \
| | | |
| | | | |
Pass trace level as `uint32_t`, which is the underlying type
|
| | |/
| |/| |
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
vespa-engine/havardpe/consolidate-sorting-strategies
consolidate solutions into a single heuristic algorithm
|
|/ / /
| | |
| | |
| | | |
use error relative to minimal cost rather than error potential
|
|\ \ \
| |/ /
|/| | |
add some comparison slack to improve robustness
|
| |/ |
|
|\ \
| |/
|/|
| |
| | |
vespa-engine/vekterli/persistence-locking-feed-op-batching
Support pipelining (batching) of mutating ops to same bucket
|
| | |
|
| |
| |
| |
| |
| | |
Can't initialize members in constructor that depend on objects
that are subsequently reset by the superclass' `SetUp()` method.
|
| |
| |
| |
| |
| |
| |
| | |
Implicitly unlocking messes up higher level assumptions about
when locks are held and thus cannot be safely done. Lock will
be unlocked immediately after anyway, so this does not seem
like a useful optimization.
|
| | |
|
| |
| |
| |
| |
| | |
Downcast-safe type invariant shall be maintained by the message's
own type ID tracking. If it's not, we have bigger problems.
|
| |
| |
| |
| | |
Avoids the need for barriers to avoid stepping on the thread's toes
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Bucket operations require either exclusive (single writer) or
shared (multiple readers) access. Prior to this commit, this
means that many enqueued feed operations to the same bucket
introduce pipeline stalls due to each operation having to wait
for all prior operations to the bucket to complete entirely
(including fsync of WAL append). This is a likely scenario when
feeding a document set that was previously acquired through
visiting, as such documents will inherently be output in
bucket-order.
With this commit, a configurable number of feed operations
(put, remove and update) bound for the exact same bucket may
be sent asynchronously to the persistence provider in the
context of the _same_ write lock. This mirrors how merge
operations work for puts and removes.
Batching is fairly conservative, and will _not_ batch across
further messages when any of the following holds:
* A non-feed operation is encountered
* More than one mutating operation is encountered for the
same document ID
* No more persistence throttler tokens can be acquired
* Max batch size has been reached
Updating the bucket DB, assigning bucket info and sending
replies is deferred until _all_ batched operations complete.
Max batch size is (re-)configurable live and defaults to a
batch size of 1, which shall have the exact same semantics as
the legacy behavior.
Additionally, clock sampling for persistence threads have been
abstracted away to allow for mocking in tests (no need for sleep!).
|
|\ \
| | |
| | | |
Update dependency org.questdb:questdb to v7.4.0
|
| | | |
|
| | | |
|
|\ \ \
| | | |
| | | | |
Update aws-java-sdk monorepo to v1.12.698
|
| |/ / |
|
|\ \ \
| |/ /
|/| | |
Add onnx output caching to embedder (allow different post-processing of model outputs)
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
Current interface requires a lot of boilerplate code.
|
| | | |
|
| | |
| | |
| | |
| | | |
using Context cache
|
|\ \ \
| | | |
| | | | |
require native libraries for llama
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | | |
Update aws-java-sdk monorepo to v1.12.697
|
| | | | | |
|
|\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
vespa-engine/renovate/github.com-klauspost-compress-1.x
Update module github.com/klauspost/compress to v1.17.8
|
| |/ / / / |
|
|\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
vespa-engine/hmusum/dont-log-error-when-subscriber-closed
No need for error if failing when subscriber is closing down
|
| | | | | | |
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
Add significance config model registry
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
|\ \ \ \ \ \ \
| |_|_|/ / / /
|/| | | | | |
| | | | | | |
| | | | | | | |
vespa-engine/marius/add-significance-model-registry
Add significance model registry to linguistics
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|