oxia
oxia copied to clipboard
Oxia - Metadata store and coordination system
``` {"endExclusive":"__oxia/session/0000000000000000//","shard":"0","startInclusive":"__oxia/session/0000000000000000/"} shard=2 term=2 panic: runtime error: invalid memory address or nil pointer dereference [signal SIGSEGV: segmentation violation code=0x1 addr=0x38 pc=0x16187db] goroutine 1201 [running]: github.com/streamnative/oxia/server.(*leaderController).list.func1() /home/runner/work/oxia/oxia/server/leader_controller.go:657 +0x23b github.com/streamnative/oxia/common.DoWithLabels.func1({0x1c08700?, 0xc000a773b0?}) /home/runner/work/oxia/oxia/common/pprof.go:46...
at: https://github.com/streamnative/oxia/actions/runs/13535939433/job/37827547039?pr=627 ``` WARNING: abs already refers to: #'clojure.core/abs in namespace: clojure.core.matrix.impl.mathsops, being replaced by: #'clojure.core.matrix.impl.mathsops/abs Warning: protocol #'clojure.core.matrix.protocols/PMathsFunctions is overwriting function abs WARNING: abs already refers to: #'clojure.core/abs in...
Ref: https://github.com/streamnative/oxia/pull/622
### Motivation During the test, we found a cluster shards leader distribution like the image as follows. That is not good for distributed systems to rebalance traffic.
### Motivation Currently, we do not support shard splits for horizontal scaling. We should support it to allow for better dynamic scaling of clusters.
``` │ panic: runtime error: invalid memory address or nil pointer dereference │ │ [signal SIGSEGV: segmentation violation code=0x1 addr=0x40 pc=0x1a69d05] │ │ │ │ goroutine 134600539 [running]: │ │...
How can a consistent backup of Oxia be created for DR purposes? What is the procedure to restore from such a backup?
### Motivation In the current implementation. We don't support multi-AZ awareness. We can only create three nodes and give three replicas per shard, which will auto-distribute in the different AZs....