aboutsummaryrefslogtreecommitdiffstats
path: root/zkfacade/src/test/java/com
Commit message (Collapse)AuthorAgeFilesLines
* Update copyrightJon Bratseth2023-10-098-8/+9
|
* Minor refactoring of CuratorCompletionWaiter, no functional changesHarald Musum2023-09-181-2/+2
|
* Specify barrier wait for all timeout in callers, simplifyHarald Musum2023-03-221-3/+5
|
* Improve exception message grammar, javadocjonmv2022-11-141-1/+1
|
* Remove uneeded test assertion which is unstablejonmv2022-11-141-1/+0
|
* Regularly write is_active metricjonmv2022-11-091-1/+1
|
* 12s session timeout for application cluster curatorjonmv2022-10-142-3/+3
|
* Update metrics as agreedjonmv2022-10-131-21/+11
|
* Kill AbstractSingletonWorker, and add sample codejonmv2022-10-121-4/+9
|
* Acquire a single lock again in VespaCuratorjonmv2022-10-121-5/+0
|
* And another one bites the dustjonmv2022-10-111-2/+1
|
* Set exception before phasingjonmv2022-10-111-1/+1
|
* Remove another metric verificationjonmv2022-10-111-1/+0
|
* use manual clock for all testsjonmv2022-10-111-2/+2
|
* Remove test metrics for which we cannot (easily) synchronisejonmv2022-10-111-4/+3
|
* Complete janitor shutdown in synchronous part of shutdownjonmv2022-10-111-2/+2
|
* Sync shutdown, invalidate doom on no singletons, fix unit testjonmv2022-10-111-9/+13
|
* Stabilize unit testjonmv2022-10-111-1/+1
|
* Add metrics to singletone manager, with placeholder namesjonmv2022-10-101-5/+100
|
* Register number of parties equal to possible concurrent arrivalsjonmv2022-10-101-0/+2
|
* No inheritance on AbstractComponentjonmv2022-10-101-7/+7
|
* Remove left-over toString, and add forgotten assertionjonmv2022-10-101-1/+2
|
* Expand ZK API, and implement in CuratorWrapperjonmv2022-10-101-0/+245
|
* Test out-of-order releaseHåkon Hallingstad2022-04-271-0/+38
|
* Make setting jute max buffer testable and add testHarald Musum2022-02-171-1/+24
|
* Replace use of Guava's UncheckedTimeoutException with our ownBjørn Christian Seime2022-01-141-1/+1
|
* Update Verizon Media copyright notices.gjoranv2021-10-076-6/+6
|
* Update 2017 copyright notices.gjoranv2021-10-071-1/+1
|
* Use Curator instead of ConfigCurator, part 4Harald Musum2021-07-091-4/+5
|
* Remove duplicate headersJon Bratseth2021-03-181-1/+1
|
* Add copyright headersJon Bratseth2021-03-181-1/+2
|
* Simplify, testing server is not usedHarald Musum2021-03-031-59/+7
|
* Use CuratorConfigMartin Polden2020-11-201-13/+17
|
* Extract ConnectionSpecMartin Polden2020-11-202-16/+74
|
* Also test cumulative deadlock countersHåkon Hallingstad2020-10-201-0/+4
|
* Replace deadlock avoidance with metricsHåkon Hallingstad2020-10-191-9/+16
|
* Deadlock detectionHåkon Hallingstad2020-10-111-5/+70
| | | | | | | | | | | | Just before Lock.acquire() is invoked, the locks within the process is queried to see if a "deadlock" will occur: The current thread waiting to acquire lock path P1, which is held by thread T1 waiting on acquiring a lock at path P2, etc, until a thread is waiting for a lock held by the current thread. Even without this PR the deadlock would resolve itself automatically because all locks are acquired with timeouts. However, this PR 1. resolves the deadlock immediately, and 2. leaves a log trace (hopefully from the exception) to allow us to refactor code to avoid such deadlocks.
* Avoid metrics on reentry of lockHåkon Hallingstad2020-10-082-32/+60
|
* Make richer latency statsHåkon Hallingstad2020-10-054-139/+144
| | | | | | | | | Makes a LatencyStats which provides some useful metrics, best explained there and in LatencyMetrics. This includes latency metrics, the "QPS" (e.g. the number of acquire() per second), and load metrics. Unfortunately I had to move from atomics to synchronized to accomplish this, but I see no other way.
* Move lock metrics to MetricsReporterHåkon Hallingstad2020-10-035-29/+196
| | | | | | | | | | | | | | | Adds two new metrics: - The load of acquiring each lock path: The average number of threads waiting to acquire the lock within the last minute (or unit of time). Aka the lock queue (depth). - The load of the lock for each lock path: The average number of threads holding the lock within the last minute (or unit of time). This is always <= 1. Aka the lock utilization. Changes the LockCounters to LockMetrics, and exporting those once every minute through MetricReporter which is designed for this.
* Add metrics to lock attemptsHåkon Hallingstad2020-10-013-4/+6
|
* Record locks taken for external deploysHåkon Hallingstad2020-09-301-11/+11
| | | | | | | | | | | | - Information about a lock attempt now includes a list of lock attempts done while holding the lock, forming a tree (forest) structure. - Records the duration and locking attempts done as part of an external deploy, forming a tree of locks with timing info. The currently active external deploys are shown in an "ongoing-recording" field of /nodes/v2/locks. - The 3 longest external deploys are kept in "recordings" in /nodes/v2/locks. - Extracts the global process-wide parts of ThreadLockStats into separate class for clarity.
* More info -> attempt renamesHåkon Hallingstad2020-09-282-11/+11
|
* LockInfo -> LockAttempt, ThreadLockInfo -> ThreadLockStats, and moreHåkon Hallingstad2020-09-282-36/+44
|
* Use deque as stackHåkon Hallingstad2020-09-281-0/+23
|
* Mock lock path from thread to per-lock (bug)Håkon Hallingstad2020-09-262-1/+59
|
* Adds method name to stack trace and adds timeout count and testHåkon Hallingstad2020-09-251-0/+113
|
* Stick to junit for simple test.Henning Baldersheim2020-08-111-6/+5
|
* Wait longer for servers to reach barrierHarald Musum2020-04-291-3/+3
| | | | | | | 1. Wait up to 2 seconds for all to reach barrier. 2. If not, wait up to 4 seconds for the server that waits for the barrier to be one of the respondents AND a majority of servers have reached barrier. 3. If not, wait for a majority of servers to have reached barrier.
* Create zookeeper client config file only when necessaryHarald Musum2020-01-091-5/+4
|