Added Merkel Trees for better replication state tracking. #1
Reference in New Issue
Block a user
No description provided.
Delete Branch "MrKalzu/kalzu-value-store:master"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Code compiles, but have not been tested at all. I haven even look at the code.
==================================================
KVS Integration Test Suite (Merkle Tree)
[INFO] Setting up test environment...
[INFO] Cleaning up test environment...
[INFO] Test 1: Binary build verification
[PASS] Binary builds successfully
[INFO] Test 2: Basic functionality test
[PASS] Basic CRUD operations work
[INFO] Test 3: 2-node cluster formation and Merkle Tree replication
[PASS] 2-node cluster formed successfully (N1 members: 1, N2 members: 1)
[INFO] Putting data on Node 1, waiting for Merkle sync...
[PASS] Data replication works correctly (Node 2 has data from Node 1)
[PASS] Replicated data retains original UUID and Timestamp
[INFO] Test 4: Conflict resolution test (Merkle Tree based)
[INFO] Initial conflict state: Node1='from node1', Node2='from node2'
[PASS] Conflict resolution converged to: 'from node2'
[PASS] Resolved data retains consistent UUID and Timestamp across nodes
[PASS] Conflict resolution messages found in logs
==================================================
Total Tests: 4
Passed: 8
Failed: 0
🎉 All tests passed! KVS with Merkle Tree sync is working correctly.
[INFO] Cleaning up test environment...