[jira] [Created] (HBASE-18734) Possible memory leak when running mini cluster

2017-09-01 Thread Samarth Jain (JIRA)
Samarth Jain created HBASE-18734: Summary: Possible memory leak when running mini cluster Key: HBASE-18734 URL: https://issues.apache.org/jira/browse/HBASE-18734 Project: HBase Issue Type: Bu

[jira] [Created] (HBASE-18735) Provide a fast mechanism for shutting down mini cluster

2017-09-01 Thread Samarth Jain (JIRA)
Samarth Jain created HBASE-18735: Summary: Provide a fast mechanism for shutting down mini cluster Key: HBASE-18735 URL: https://issues.apache.org/jira/browse/HBASE-18735 Project: HBase Issue

[jira] [Resolved] (HBASE-18729) [compat 1-2] The input type of Result#createCompleteResult is changed

2017-09-01 Thread Chia-Ping Tsai (JIRA)
[ https://issues.apache.org/jira/browse/HBASE-18729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai resolved HBASE-18729. Resolution: Not A Problem > [compat 1-2] The input type of Result#createCompleteResult is c

HBase Backup Mode

2017-09-01 Thread Lars George
Hi, I stumbled across this: hbase-server/src/main/java/org/apache/hadoop/hbase/backup/example/HFileArchiveManager.java I am wondering what the state of this is. Also, why is this in an _example_ package, if it is usable code. Should be in `util` or so instead? If it isn't really used at all or ju

[jira] [Created] (HBASE-18736) Cleanup the HTD/HCD for Admin

2017-09-01 Thread Chia-Ping Tsai (JIRA)
Chia-Ping Tsai created HBASE-18736: -- Summary: Cleanup the HTD/HCD for Admin Key: HBASE-18736 URL: https://issues.apache.org/jira/browse/HBASE-18736 Project: HBase Issue Type: Sub-task

[jira] [Created] (HBASE-18737) Display configured max size of memstore and cache on RS UI

2017-09-01 Thread Biju Nair (JIRA)
Biju Nair created HBASE-18737: - Summary: Display configured max size of memstore and cache on RS UI Key: HBASE-18737 URL: https://issues.apache.org/jira/browse/HBASE-18737 Project: HBase Issue Ty

[jira] [Created] (HBASE-18738) Ride over HDFS 'safe mode' post-launch

2017-09-01 Thread stack (JIRA)
stack created HBASE-18738: - Summary: Ride over HDFS 'safe mode' post-launch Key: HBASE-18738 URL: https://issues.apache.org/jira/browse/HBASE-18738 Project: HBase Issue Type: Bug Reporter

Re: [DISCUSS] hbase-2.0.0 compatibility expectations

2017-09-01 Thread stack
On Thu, Aug 24, 2017 at 9:13 AM, stack wrote: > On Thu, Aug 3, 2017 at 11:05 PM, stack wrote: > >> Thanks Zach for clarification. Let me work up a list and then come back >> to this thread. Jira needs an edit pass to. >> >> > JIRA editing reflecting incompatibles has been coming along. It is st

[jira] [Resolved] (HBASE-18507) [C++] Support for MultiPuts in AsyncBatchRpcRetryingCaller class

2017-09-01 Thread Enis Soztutar (JIRA)
[ https://issues.apache.org/jira/browse/HBASE-18507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Enis Soztutar resolved HBASE-18507. --- Resolution: Fixed Fix Version/s: HBASE-14850 Thanks Sudeep. I have committed the code

[jira] [Created] (HBASE-18739) Make all TimeRange Constructors InterfaceAudience Private.

2017-09-01 Thread stack (JIRA)
stack created HBASE-18739: - Summary: Make all TimeRange Constructors InterfaceAudience Private. Key: HBASE-18739 URL: https://issues.apache.org/jira/browse/HBASE-18739 Project: HBase Issue Type: Sub-

[jira] [Created] (HBASE-18740) Upgrade Zookeeper version in branch 1.4 and branch-1

2017-09-01 Thread Jerry He (JIRA)
Jerry He created HBASE-18740: Summary: Upgrade Zookeeper version in branch 1.4 and branch-1 Key: HBASE-18740 URL: https://issues.apache.org/jira/browse/HBASE-18740 Project: HBase Issue Type: Impr

Re: [DISCUSS] hbase-2.0.0 compatibility expectations

2017-09-01 Thread Stack
What versions should you be able to upgrade from? 1.0.0? 0.98.x? 1.2? I'm thinking 0.98 unless it means more work. Thanks, St.Ack On Wed, Aug 2, 2017 at 4:38 PM, Stack wrote: > What are our expectations regards compatibility between hbase1 and hbase2? > > Lets have a chat about it. Here are some

Re: [DISCUSS] hbase-2.0.0 compatibility expectations

2017-09-01 Thread Stack
On Fri, Sep 1, 2017 at 2:23 PM, Stack wrote: > What versions should you be able to upgrade from? 1.0.0? 0.98.x? 1.2? I'm > thinking 0.98 unless it means more work. > Scratch that. Minimum is 1.0.0 I think given that is what I'm doing all compat compares against and given we did API cleanup befor

Re: [DISCUSS] hbase-2.0.0 compatibility expectations

2017-09-01 Thread Sean Busbey
Giving rolling-upgradable ability within branch-1, I'm inclined to push for our current stable release line,1.2. On Fri, Sep 1, 2017 at 2:24 PM, Stack wrote: > On Fri, Sep 1, 2017 at 2:23 PM, Stack wrote: > >> What versions should you be able to upgrade from? 1.0.0? 0.98.x? 1.2? I'm >> thinking

[jira] [Created] (HBASE-18741) Remove cancel command from backup code

2017-09-01 Thread Ted Yu (JIRA)
Ted Yu created HBASE-18741: -- Summary: Remove cancel command from backup code Key: HBASE-18741 URL: https://issues.apache.org/jira/browse/HBASE-18741 Project: HBase Issue Type: Bug Report

Re: [DISCUSS] hbase-2.0.0 compatibility expectations

2017-09-01 Thread Chia-Ping Tsai
The most of issues use hadoop flag, so the filter looks like this. project = HBASE AND fixVersion in (2.0.0, 2.0.0-alpha-1, 2.0.0-alpha-2, 2.0.0-alpha-3, 3.0) AND (labels in (incompatibleChange, incompatible, incompatibility) OR "Hadoop Flags" in ("Incompatible change")) On 2017-08-04 05:46, Ted

[jira] [Created] (HBASE-18742) Make cache configuration like global switch

2017-09-01 Thread Chia-Ping Tsai (JIRA)
Chia-Ping Tsai created HBASE-18742: -- Summary: Make cache configuration like global switch Key: HBASE-18742 URL: https://issues.apache.org/jira/browse/HBASE-18742 Project: HBase Issue Type: N