Should be handled in RPC queues first, before mutation op reaches
RingBuffer, I think.
But to answer your question: the only guarantee HBase provide (promises) is
strictly consistent writes and atomicity for
a single row mutation. No, won't break anything. Permutations of mutations
in an execution
We have different priority in RPC level, we can even separate write
requests and read requests to different handlers. But, yes, the WAL uses
FIFO queue, and even more, we use a single thread to consume the append and
sync requests. The reason is that we need to keep the sequenceID of WAL
entry to i
Hi,
I'am trying to add priority to schedule different types of requests in
HBase. But the Write-ahead logging use RingBuffer which
is essentially a FIFO queue makes it hard. In this case, let's say if the
low priority request already queued in the RingBuffer, the high priority
request can not be e
