| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|\
| |
| | |
Add metric for Hubspot exceptions
|
| | |
|
|/ |
|
|
|
|
| |
Was only used by `DirConfig`.
|
|
|
|
|
| |
Test has not served much of a purpose other than burning CPU cycles
and seemingly greatly confusing Valgrind's thread scheduler.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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!).
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Extends metric producer classes with the requested exposition format.
As a consequence, the State API server has been changed to allow
emitting other content types than just `application/json`.
Add custom Prometheus rendering for Slobrok, as it does its own
domain-specific metric tracking. However, since it has non-destructive
sampling properties, we can actually use proper `counter` types.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Maps all internal metrics to one or more labelled time series.
Due to poor compatibility between the data model (and sampling
strategy) of the legacy metrics framework and that of Prometheus,
all time series are emitted as `untyped` metrics.
This is a stop-gap solution on the way to "properly" supporting
Prometheus exposition, and the output of this renderer should
therefore only be used for internal purposes.
|
| |
|
|
|
| |
Co-authored-by: Ola Aunrønning <olaa@yahooinc.com>
|
| |
|
| |
|
| |
|
| |
|
|\
| |
| | |
Expose expire metrics
|
| | |
|
| | |
|
| | |
|
|/ |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
node down edge
The stored entry count encompasses both visible documents and
tombstones. Using this count rather than bucket count avoids any
issues where a node only containing empty buckets (i.e. no actual
data) is prohibited from being marked as permanently down.
Entry count is cross-checked with the visible document count;
if the former is zero, the latter should always be zero as well.
Since entry/doc counts were only recently introduced as part of
the HostInfo payload, we have to handle the case where these do
not exist. If entry count is not present, the decision to allow
or disallow the transition falls back to the bucket count check.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|\
| |
| | |
Let distributor metric decide cluster stability
|
| | |
|
| | |
|
|/ |
|
| |
|
| |
|
|\
| |
| |
| |
| | |
vespa-engine/vekterli/expose-remove-by-gid-metrics
Expose `remove_by_gid` persistence-level metrics
|
| | |
|
| | |
|
|/ |
|
| |
|
|
|
|
|
| |
Having visibility of this number will make it easier to choose
sensible defaults based on observations of existing systems.
|
|\
| |
| |
| |
| | |
vespa-engine/yngveaasheim/add-description-to-metric-set-reference-doc
Add a short description to metric set reference documentation
|
| | |
|
|/ |
|
| |
|
| |
|