Duo Zhang created HBASE-19410:
-
Summary: Move zookeeper related UTs to hbase-zookeeper and mark
them as ZKTests
Key: HBASE-19410
URL: https://issues.apache.org/jira/browse/HBASE-19410
Project: HBase
Haibo Chen created HBASE-19409:
--
Summary: HBase client brings down YARN node manager when it tries
to register JvmMetrics in the hadoop metrics system
Key: HBASE-19409
URL:
Chia-Ping Tsai created HBASE-19408:
--
Summary: Remove WALActionsListener.Base
Key: HBASE-19408
URL: https://issues.apache.org/jira/browse/HBASE-19408
Project: HBase
Issue Type: Task
[
https://issues.apache.org/jira/browse/HBASE-18943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Drob resolved HBASE-18943.
---
Resolution: Duplicate
Fix Version/s: (was: 2.0.0-beta-1)
[~tedyu] - didn't realize that
stack created HBASE-19407:
-
Summary: [branch-2] Remove backup/restore
Key: HBASE-19407
URL: https://issues.apache.org/jira/browse/HBASE-19407
Project: HBase
Issue Type: Task
Reporter:
On Fri, Dec 1, 2017 at 11:32 AM, Stack wrote:
> ...
> Thanks all who participated trying to land this feature,
>
Just in case I give the wrong impression, the feature is in master branch
still under development there. Come hbase-2.1.0 (or later), if demonstrable
progress on
I think it's important to have some _external_ method to verify
correctness. There is a lot of space between the system thinks it is
correct and the user is confident that it is correct.
We don't intentionally set out to lose data, and yet it still happens
sometimes in HBase. It's good that we
Thanks, Mike
#1 is done
#4 is done, but not committed yet
#3 is questionable to say the least. All B tools provide guarantee of
operation correctness if operation succeeds. Otherwise, what is the point
of separate Fault-tolerance work? FT includes correctness guarantee as
well, we track all
churro morales created HBASE-19405:
--
Summary: Fix RowTooBigException to use that in hbase-client and
ensure that it extends DoNotRetryIOException
Key: HBASE-19405
URL:
The list is what Josh proposed in the original email to the list.
What is the JIRA for #3?
On Fri, Dec 1, 2017 at 12:20 PM, Vladimir Rodionov
wrote:
> Where did you get this from, Stack?
>
> I am doing scale testing now and this is last task on *my* list for beta-1.
>
>
Chia-Ping Tsai created HBASE-19404:
--
Summary: Fix DisabledWALProvider or just remove it
Key: HBASE-19404
URL: https://issues.apache.org/jira/browse/HBASE-19404
Project: HBase
Issue Type:
No problem, please commit it.
On Thu, Nov 30, 2017 at 6:19 PM, Guanghao Zhang wrote:
> Andrew, HBASE-18626 is a document fix for the incompatible change about the
> replication TableCFs' config. Can we include it for 1.4? Thanks.
>
> 2017-12-01 9:19 GMT+08:00 Stack
Balazs Meszaros created HBASE-19403:
---
Summary: Add missing security hooks for AdminService RPCs
Key: HBASE-19403
URL: https://issues.apache.org/jira/browse/HBASE-19403
Project: HBase
Issue
Balazs Meszaros created HBASE-19402:
---
Summary: Add missing security hooks for RegionServerStatusService
RPCs
Key: HBASE-19402
URL: https://issues.apache.org/jira/browse/HBASE-19402
Project: HBase
Balazs Meszaros created HBASE-19401:
---
Summary: Add missing security hooks for ClientService RPCs
Key: HBASE-19401
URL: https://issues.apache.org/jira/browse/HBASE-19401
Project: HBase
Yuqi Gu created HBASE-19398:
---
Summary: Unit Tests failed in hbase-3.0.0 on Arm64 and x86
Key: HBASE-19398
URL: https://issues.apache.org/jira/browse/HBASE-19398
Project: HBase
Issue Type: Bug
Unsubscribe
At 2017-09-11 22:58:00, "Guangxu Cheng (JIRA)" wrote:
>Guangxu Cheng created HBASE-18789:
>-
>
> Summary: Displays the reporting interval of each RS on the Master
> page
> Key: HBASE-18789
>
17 matches
Mail list logo