Marcin Copik
Marcin Copik
- [ ] Make the heartbeat frequency fully configurable by the user. - [ ] Activate heartbeat on the first user registration. - [ ] Deactivate heartbeat on the last...
We need to implement the ZooKeeper watch semantics. - [ ] Create watches on data. - [ ] Create empty, fake nodes for `create` watches. - [ ] Writer checking...
Old report of the bug: "System hangs if we have an event in async, we don't query the future, but later submit other options". Looks like a problem in ordering...
Currently, we just replicate the `zxid` counter from ZooKeeper. - [x] Implement the extended counter with independent values for multiple writers. - [ ] Implement the epoch counters. - [x]...
ZooKeeper supported conditional updates on the node version. Instead, we want to implement a generic solution where a user submits a pickled lambda function to be invoked on the node...
In the final version, we want to support data stored in multiple cloud regions. - [ ] Per-region S3 data store. - [ ] Per-region heartbeats. - [ ] Per-region...
Currently, we do not support the creation of ephemeral and sequential nodes. The `writer` function needs an extension of `create` option.
Currently, we expose a very low-level interface for allocating memory - as shown in this documentation: ```cpp rdmalib::Buffer in(opts.input_size, rdmalib::functions::Submission::DATA_HEADER_SIZE), out(opts.input_size); in.register_memory(executor._state.pd(), IBV_ACCESS_LOCAL_WRITE); out.register_memory(executor._state.pd(), IBV_ACCESS_LOCAL_WRITE | IBV_ACCESS_REMOTE_WRITE); ``` While `rdmalib::Buffer`...
The current implementation of resource manager doesn't satisfy all of the requirements. - [x] Correctly distribute executor data to clients. - [x] Preload executor data from file for simplified testing....
We should add [readerwriterqueue](https://github.com/cameron314/readerwriterqueue) as a proper dependency in the CMake build. Furthermore, we want to fetch and build `Pistache` to avoid the trouble of forcing users to install it...