Open-source graph database, built for real-time streaming data, compatible with Neo4j.
cyphergraphgraph-algorithmsgraph-analysisgraph-databasekafkakafka-streamsnosqlopencypherstream-processingstreaming-data
5d5dfbb6f7
Summary: During it's leadership, one peer can receive RPC messages from other peers that his reign is over. The problem is when this happens during a transaction commit. This is handled in the following way. If we're the current leader and we want to commit a transaction, we need to make sure the Raft Log is replicated before we can tell the client that the transaction is committed. During that wait, we can only notice that the replication takes too long, and we report that with `LOG(WARNING)` messages. If we change the Raft mode during the wait, our Raft implementation will internally commit this transaction, but won't be able to acquire the Raft lock because the `db.Reset` has been called. This is why there is an manual lock acquire. If we pick up that the `db.Reset` has been called, we throw an `UnexpectedLeaderChangeException` exception to the client. Another thing with long running transactions, if someone decides to kill a `memgraph_ha` instance during the commit, the transaction will have `abort` hint set. This will cause the `src/query/operator.cpp` to throw a `HintedAbortError`. We need to catch this during the shutdown, because the `memgraph_ha` isn't dead from the user perspective, and the transaction wasn't aborted because it took too long, but we can differentiate between those two. Reviewers: mferencevic, ipaljak Reviewed By: mferencevic, ipaljak Subscribers: pullbot Differential Revision: https://phabricator.memgraph.io/D1956 |
||
|---|---|---|
| cmake | ||
| config | ||
| customers | ||
| docs | ||
| environment | ||
| experimental | ||
| libs | ||
| poc | ||
| release | ||
| src | ||
| tests | ||
| tools | ||
| .arcconfig | ||
| .arclint | ||
| .clang-format | ||
| .clang-tidy | ||
| .gdbinit | ||
| .gitignore | ||
| .ycm_extra_conf.py | ||
| apollo_archives.py | ||
| apollo_archives.yaml | ||
| apollo_build.yaml | ||
| CHANGELOG.md | ||
| CMakeLists.txt | ||
| Doxyfile | ||
| Doxylogo.png | ||
| init | ||
| README.md | ||
memgraph
Memgraph is an ACID compliant high performance transactional distributed in-memory graph database featuring runtime native query compiling, lock free data structures, multi-version concurrency control and asynchronous IO.
dependencies
Memgraph can be compiled using any modern c++ compiler. It mostly relies on the standard template library, however, some things do require external libraries.
Some code contains linux-specific libraries and the build is only supported on a 64 bit linux kernel.
- linux
- clang 3.8 (good c++11 support, especially lock free atomics)
- antlr (compiler frontend)
- cppitertools
- fmt format
- google benchmark
- google test
- glog
- gflags