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
stack created HBASE-21450:
-
Summary: [documentation] Point spark doc at hbase-connectors spark
Key: HBASE-21450
URL: https://issues.apache.org/jira/browse/HBASE-21450
Project: HBase
Issue Type: Bug
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
stack created HBASE-21449:
-
Summary: [hbase-connectors] Test can do secure hbase-spark
Key: HBASE-21449
URL: https://issues.apache.org/jira/browse/HBASE-21449
Project: HBase
Issue Type: Bug
Hi folks!
Some time ago we talked about trying to get back on track for a more
regular cadence of minor releases rather than maintenance releases
(like how we did back pre-1.0). That never quite worked out for the
HBase 1.y line, but is still something we could make happen for HBase
2.
We're
[
https://issues.apache.org/jira/browse/HBASE-21448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack resolved HBASE-21448.
---
Resolution: Fixed
Merged. Resolving.
> [hbase-connectors] Make compile/tests pass on scala 2.10 AND 2.11
>
stack created HBASE-21448:
-
Summary: [hbase-connectors] Make compile/tests pass on scala 2.10
AND 2.11
Key: HBASE-21448
URL: https://issues.apache.org/jira/browse/HBASE-21448
Project: HBase
Issue
Nicholas Jiang created HBASE-21447:
--
Summary: HBCK2 tool have questions on holes when HBCK2 checks
region chain
Key: HBASE-21447
URL: https://issues.apache.org/jira/browse/HBASE-21447
Project:
