[jira] [Created] (HBASE-21376) Add some verbose log to MasterProcedureScheduler

2018-10-23 Thread Allan Yang (JIRA)
Allan Yang created HBASE-21376: -- Summary: Add some verbose log to MasterProcedureScheduler Key: HBASE-21376 URL: https://issues.apache.org/jira/browse/HBASE-21376 Project: HBase Issue Type:

[jira] [Created] (HBASE-21375) Forward port "HBASE-21364 Procedure holds the lock should put to front of the queue after restart"

2018-10-23 Thread Duo Zhang (JIRA)
Duo Zhang created HBASE-21375: - Summary: Forward port "HBASE-21364 Procedure holds the lock should put to front of the queue after restart" Key: HBASE-21375 URL: https://issues.apache.org/jira/browse/HBASE-21375

Re: HBase developer meetup

2018-10-23 Thread la...@apache.org
This is still on. I'm trying to get us a spot in the Salesforce tower top floor. As you can imagine it's a coveted spot.If I can't get a time slot there in the next week I'll book a "usual" conference room. Stay tuned. Thanks. -- Lars On Friday, October 5, 2018, 1:00:42 PM PDT,

[jira] [Resolved] (HBASE-21353) TestHBCKCommandLineParsing#testCommandWithOptions hangs on call to HBCK2#checkHBCKSupport

2018-10-23 Thread stack (JIRA)
[ https://issues.apache.org/jira/browse/HBASE-21353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack resolved HBASE-21353. --- Resolution: Fixed Assignee: stack Fix Version/s: hbck2-1.0.0 Pushed fix over on

[jira] [Created] (HBASE-21374) Backport HBASE-21342 to branch-1

2018-10-23 Thread Mike Drob (JIRA)
Mike Drob created HBASE-21374: - Summary: Backport HBASE-21342 to branch-1 Key: HBASE-21374 URL: https://issues.apache.org/jira/browse/HBASE-21374 Project: HBase Issue Type: Task

[jira] [Created] (HBASE-21373) Backport to branch-1, "HBASE-21338 [balancer] If balancer is an ill-fit for cluster size, it gives little indication"

2018-10-23 Thread stack (JIRA)
stack created HBASE-21373: - Summary: Backport to branch-1, "HBASE-21338 [balancer] If balancer is an ill-fit for cluster size, it gives little indication" Key: HBASE-21373 URL:

Re: [DISCUSS] Changing hadoop check versions in our hbase-personality?

2018-10-23 Thread Stack
On Tue, Oct 23, 2018 at 9:44 AM Sean Busbey wrote: > I can get behind more aggressively updating our dependencies to avoid > CVEs. I don't think we should do this in maintenance releases though. > Maintenance releases are meant to be extremely low risk for downstream > users. Despite our efforts

[jira] [Created] (HBASE-21372) Set hbase.assignment.maximum.attempts to Long.MAX

2018-10-23 Thread stack (JIRA)
stack created HBASE-21372: - Summary: Set hbase.assignment.maximum.attempts to Long.MAX Key: HBASE-21372 URL: https://issues.apache.org/jira/browse/HBASE-21372 Project: HBase Issue Type: Sub-task

Re: [DISCUSS] 2.1.1 Release Plans?

2018-10-23 Thread Stack
Heads-up. I'm going to cut an RC0 this evening unless objection. HBASE-21073 landed this morning as did some other sweet fixes over night. Mildly related, I put up first cut at hbck2 doc over at https://github.com/apache/hbase-operator-tools/tree/master/hbase-hbck2. There is way more to do --

[jira] [Created] (HBASE-21371) Hbase unable to compile against Hadoop trunk (3.3.0-SNAPSHOT) due to license error

2018-10-23 Thread Wei-Chiu Chuang (JIRA)
Wei-Chiu Chuang created HBASE-21371: --- Summary: Hbase unable to compile against Hadoop trunk (3.3.0-SNAPSHOT) due to license error Key: HBASE-21371 URL: https://issues.apache.org/jira/browse/HBASE-21371

[jira] [Resolved] (HBASE-21192) Add HOW-TO repair damaged AMv2.

2018-10-23 Thread stack (JIRA)
[ https://issues.apache.org/jira/browse/HBASE-21192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack resolved HBASE-21192. --- Resolution: Fixed Fix Version/s: 2.0.3 2.1.1 2.2.0

[jira] [Created] (HBASE-21370) Revamp or remove OfflineMetaRepair

2018-10-23 Thread stack (JIRA)
stack created HBASE-21370: - Summary: Revamp or remove OfflineMetaRepair Key: HBASE-21370 URL: https://issues.apache.org/jira/browse/HBASE-21370 Project: HBase Issue Type: Task Components:

Re: [DISCUSS] Changing hadoop check versions in our hbase-personality?

2018-10-23 Thread Zach York
Thanks for the context Duo! Yes I agree, if we know about a CVE for a dependency it is our duty to either upgrade the dependency or disclose the vulnerability (ReleaseNotes?) so that users can make the necessary decision. However, this obviously does not apply for any CVE that hasn't been brought

[jira] [Created] (HBASE-21369) [hbase-operator-tools] Create a tool that will write the versions file

2018-10-23 Thread stack (JIRA)
stack created HBASE-21369: - Summary: [hbase-operator-tools] Create a tool that will write the versions file Key: HBASE-21369 URL: https://issues.apache.org/jira/browse/HBASE-21369 Project: HBase

Re: [DISCUSS] Changing hadoop check versions in our hbase-personality?

2018-10-23 Thread Sean Busbey
I can get behind more aggressively updating our dependencies to avoid CVEs. I don't think we should do this in maintenance releases though. Maintenance releases are meant to be extremely low risk for downstream users. Despite our efforts to date upgrading a dependency is still disruptive,

[jira] [Resolved] (HBASE-21332) HBase scan with PageFilter cannot get all rows, non-edge region skiped

2018-10-23 Thread Zheng Hu (JIRA)
[ https://issues.apache.org/jira/browse/HBASE-21332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zheng Hu resolved HBASE-21332. -- Resolution: Not A Problem Assignee: Zheng Hu > HBase scan with PageFilter cannot get all rows,

[jira] [Created] (HBASE-21368) The write latency is affected because hbase:meta move frequently at a point in time

2018-10-23 Thread Zheng Hu (JIRA)
Zheng Hu created HBASE-21368: Summary: The write latency is affected because hbase:meta move frequently at a point in time Key: HBASE-21368 URL: https://issues.apache.org/jira/browse/HBASE-21368

[jira] [Created] (HBASE-21367) Add table/region/row's statistics output for WALPrettyPrinter

2018-10-23 Thread Guanghao Zhang (JIRA)
Guanghao Zhang created HBASE-21367: -- Summary: Add table/region/row's statistics output for WALPrettyPrinter Key: HBASE-21367 URL: https://issues.apache.org/jira/browse/HBASE-21367 Project: HBase

[jira] [Created] (HBASE-21366) Optionally ignore edits for deleted columns when replication

2018-10-23 Thread Guanghao Zhang (JIRA)
Guanghao Zhang created HBASE-21366: -- Summary: Optionally ignore edits for deleted columns when replication Key: HBASE-21366 URL: https://issues.apache.org/jira/browse/HBASE-21366 Project: HBase

[jira] [Created] (HBASE-21365) Throw exception when user put data with skip wal to a table which may be replicated

2018-10-23 Thread Guanghao Zhang (JIRA)
Guanghao Zhang created HBASE-21365: -- Summary: Throw exception when user put data with skip wal to a table which may be replicated Key: HBASE-21365 URL: https://issues.apache.org/jira/browse/HBASE-21365

[jira] [Created] (HBASE-21364) Procedure holds the lock should put to front of the queue after restart

2018-10-23 Thread Allan Yang (JIRA)
Allan Yang created HBASE-21364: -- Summary: Procedure holds the lock should put to front of the queue after restart Key: HBASE-21364 URL: https://issues.apache.org/jira/browse/HBASE-21364 Project: HBase

[jira] [Created] (HBASE-21363) Do not unset the partial flag for local tracker in ProcedureWALFormatReader

2018-10-23 Thread Duo Zhang (JIRA)
Duo Zhang created HBASE-21363: - Summary: Do not unset the partial flag for local tracker in ProcedureWALFormatReader Key: HBASE-21363 URL: https://issues.apache.org/jira/browse/HBASE-21363 Project: HBase

[jira] [Resolved] (HBASE-21354) Procedure may be deleted improperly during master restarts resulting in 'Corrupt'

2018-10-23 Thread Duo Zhang (JIRA)
[ https://issues.apache.org/jira/browse/HBASE-21354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang resolved HBASE-21354. --- Resolution: Fixed Hadoop Flags: Reviewed > Procedure may be deleted improperly during master