| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
|
|
|
|
| |
- Remove parameters not used.
- Make template parameter runtime parameter.
|
| |
|
|
|
|
|
| |
in preparation for using RankingAssetsBuilder when handling config
in streaming search.
|
|
|
|
| |
This reverts commit 003f019d7579e49f4ec7609ef8eac26ada6ae753.
|
| |
|
| |
|
|\
| |
| |
| |
| | |
vespa-engine/balder/final-consolidation-of-storage-framework-time-for-now
- Disconnect clock and MicroSecTime.
|
| |
| |
| |
| |
| | |
- GC unused functionality from clock/time.h
- Unify on vespalib::steady_time/system_time/duration.
|
|/ |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Enable cross-thread stack tracing as part of signal handler init
code in both storage and proton daemons.
Make deadlock detector parameters live configurable. Remove existing
`restart` config definition annotations to reflect this.
Remove dumping of bucket DB locks which hasn't really worked for a
long time now.
|
| |
|
|
|
|
| |
storage storgae_storageserver and storage_distributor.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
fixup (per application):
- maybe ignore SIGPIPE
- wire argc/argv
untangle Vespa Test Framework
strip down deprecated TestApp
|
|
|
|
| |
signal handler
|
|
|
|
| |
proton.
|
| |
|
| |
|
|
|
|
|
|
|
| |
* For C++ code this introduces a "document::config" namespace, which will
sometimes conflict with the global "config" namespace.
* Move all forward-declarations of the types DocumenttypesConfig and
DocumenttypesConfigBuilder to a common header file.
|
| |
|
| |
|
|
|
|
| |
If the number of stripes is not configured, we tune it based on the sampled number of CPU cores.
|
| |
|
|
|
|
|
|
|
| |
* a signal handler is not a thread
* if the main thread holds the lock when the signal handler is invoked
in the same thread, it will deadlock
* holding the lock is not necessary for notify_one()
|
|
|
|
|
|
| |
asserts.
This ensures the number of stripes is a power of 2 and within MaxStripes boundary.
|
|
|
|
|
|
|
| |
BucketDBUpdater if needed.
At the same time remove the manageActiveBucketCopies flag,
which has been true since the Storage provider was removed years ago.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Remove call to requestShutdown which could try to use components
that weren't properly set up yet. Only used for _maybe_ being able
to scream an error to the cluster controller, but this has very
limited usefulness in practice.
Since exceptions are categorized and logged with backtrace at the
root application main level, remove redundant logging. Also enforce
component shutdown for network setup exceptions (not sure why this
wasn't there to start with).
|
|
|
|
|
| |
- Avoid needing the definition of Error everywhere.
- use std::make_xxx and other c++11 constructs.
|
|
|
|
|
| |
Default is zero bits, which causes the standard, non-striped
implementation to be used.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
using a true repo.
|
| |
|
|\
| |
| |
| |
| | |
vespa-engine/vekterli/remove-legacy-distributor-bucket-database-implementation
Remove legacy distributor bucket DB implementation and config wiring
|
| | |
|
|/ |
|
|\
| |
| |
| |
| | |
vespa-engine/vekterli/btree-bucket-db-support-on-content-node
Create generic B-tree bucket DB and content node DB implementation
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This is the first stage of removing the legacy DB implementation.
Support for B-tree specific functionality such as lock-free snapshot
reads will be added soon. This commit is just for feature parity.
Abstract away actual database implementation to allow it to
be chosen dynamically at startup. This abstraction does incur
some overhead via call indirections and type erasures of callbacks,
so it's likely it will be removed once the transition to the
new B-tree DB has been completed.
Since the algorithms used for bucket key operations is so similar
between the content node and distributor, a generic B-tree backed
bucket database has been created. The distributor DB will be rewritten
around this code very soon.
Due to the strong coupling between bucket locking and actual DB
implementation details, the new bucket DB has a fairly significant
code overlap with the legacy implementation. This is to avoid
spending time abstracting away and factoring out code for a
legacy implementation that is to be removed entirely anyway.
Remove existing LockableMap functionality not used or that's
only used by tests.
|