atlasdb
atlasdb copied to clipboard
palantir
Transactional Distributed Database Layer
Would be great if I could specify in `atlas_tracing.prefs` to only trace cas requests, for example
Following up on PDS-94960, where we ended up unable to talk to Cassandra. Since the updates happen only every 2 minutes, trying to talk to a single node that is...
Currently if publish flakes with _some_ artifacts being published, it's rather annoying: 1. Releasing the same commit has been done in the past, but this seems a bit shady and...
As part of [Timelock Partitioning](https://github.com/palantir/atlasdb/milestone/16), the leader health check makes little to no sense. Even in the single-leader-for-all clients-world, it provides little to no value. I have multiple leaders? Ok,...
In PDS-93832, we observe that TimeLock is able to get into a state where nodes are able to exchange pings, but clients are unable to actually have any client requests...
See PDS-92137. The key graph is the one where successes suddenly stop, there is a small bunch of errors, and then complete silence.
Consider the schema ```java schema.addTableDefinition("table", new TableDefinition() {{ rowName(); rowComponent("row", ValueType.STRING); columns(); column("column", "c", JPersister.class); }}); ``` Produces generated code ```java public SomeType getColumn() { byte[] bytes = row.getColumns().get(PtBytes.toCachedBytes("c")); if...
Currently, the implementation of the bytes hydrator for a user-specified persister is to create a new instance of the persister on each hydration, and then decompress the values. This leads...
Internal reference: PDS-92632 Need to be careful with this one. Quoting my comment on the ticket, > 1. The mechanics of blacklisting in AtlasDB are that requests will be routed...
When a C* node is down, and a KVS operation that requires all nodes is called, we eventually throw a `RetryLimitReachedException`. We should identify when the cause for this failure...