[jira] [Assigned] (HBASE-12568) Adopt Semantic Versioning and document it in the book

2014-12-09 Thread Enis Soztutar (JIRA)

 [ 
https://issues.apache.org/jira/browse/HBASE-12568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Enis Soztutar reassigned HBASE-12568:
-

Assignee: Enis Soztutar

 Adopt Semantic Versioning and document it in the book
 -

 Key: HBASE-12568
 URL: https://issues.apache.org/jira/browse/HBASE-12568
 Project: HBase
  Issue Type: Sub-task
Reporter: Enis Soztutar
Assignee: Enis Soztutar
 Fix For: 1.0.0


 See 
 http://search-hadoop.com/m/DHED4LFNzP/semantic+versioningsubj=Re+HBase+Semantic+Versioning
 We should put that in the book.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-12564) consolidate the getTableDescriptors() semantic

2014-12-09 Thread Matteo Bertozzi (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-12564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14239109#comment-14239109
 ] 

Matteo Bertozzi commented on HBASE-12564:
-

{quote}We need the String and Pattern permutations? (Especially when Pattern 
gets turned into a String down in pb util for shipping to master){quote}
yeah, the String version calls Pattern.compile() to validate the regex. so it 
will be nice to keep it

 consolidate the getTableDescriptors() semantic
 --

 Key: HBASE-12564
 URL: https://issues.apache.org/jira/browse/HBASE-12564
 Project: HBase
  Issue Type: Bug
  Components: Client, master
Affects Versions: 2.0.0
Reporter: Matteo Bertozzi
Assignee: Matteo Bertozzi
Priority: Minor
 Fix For: 2.0.0

 Attachments: HBASE-12564-v0.patch, HBASE-12564-v1.patch, 
 HBASE-12564-v2.patch


 Master getTableDescriptors() which is called by Admin.listTables() has a 
 couple of different behaviors depending on how it is called. 
 after HBASE-12073 with the AccessController enabled, we now get a global 
 admin required if listTables() is called without a regex otherwise we return 
 only the table that the user can see (we show only the tables that the user 
 have access to, which means or the user is a global admin or it has a 
 table-level create/admin). We probably should have the second behavior even 
 without regex, since I should able to see my own tables. 
 getTableDescriptors() is returning only non system tables. Tools like 
 user_permission that are doing for each listTable(): userPerm(table) are 
 losing the system tables, so stuff like user_permission 'hbase:acls' will not 
 result any result.  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-11979) Compaction progress reporting is wrong

2014-12-09 Thread Hadoop QA (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-11979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14239124#comment-14239124
 ] 

Hadoop QA commented on HBASE-11979:
---

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12685945/HBASE-11979.v0.patch
  against master branch at commit b4371252fe71db938b37b7bc6391d0fb87466b36.
  ATTACHMENT ID: 12685945

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:red}-1 tests included{color}.  The patch doesn't appear to include 
any new or modified tests.
Please justify why no new tests are needed for this 
patch.
Also please list what manual steps were performed to 
verify this patch.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 javadoc{color}.  The javadoc tool did not generate any 
warning messages.

{color:green}+1 checkstyle{color}.  The applied patch does not increase the 
total number of checkstyle errors

{color:green}+1 findbugs{color}.  The patch does not introduce any new 
Findbugs (version 2.0.3) warnings.

{color:red}-1 release audit{color}.  The applied patch generated 1 release 
audit warnings (more than the master's current 0 warnings).

{color:green}+1 lineLengths{color}.  The patch does not introduce lines 
longer than 100

  {color:green}+1 site{color}.  The mvn site goal succeeds with this patch.

{color:green}+1 core tests{color}.  The patch passed unit tests in .

Test results: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12010//testReport/
Release audit warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12010//artifact/patchprocess/patchReleaseAuditWarnings.txt
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12010//artifact/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12010//artifact/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12010//artifact/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12010//artifact/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12010//artifact/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12010//artifact/patchprocess/newPatchFindbugsWarningshbase-rest.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12010//artifact/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12010//artifact/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12010//artifact/patchprocess/newPatchFindbugsWarningshbase-thrift.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12010//artifact/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12010//artifact/patchprocess/newPatchFindbugsWarningshbase-annotations.html
Checkstyle Errors: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12010//artifact/patchprocess/checkstyle-aggregate.html

  Console output: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12010//console

This message is automatically generated.

 Compaction progress reporting is wrong
 --

 Key: HBASE-11979
 URL: https://issues.apache.org/jira/browse/HBASE-11979
 Project: HBase
  Issue Type: Bug
Reporter: Andrew Purtell
Assignee: Esteban Gutierrez
Priority: Minor
 Fix For: 1.0.0, 2.0.0, 0.98.9

 Attachments: HBASE-11979.v0.patch


 This is a long standing problem and previously could be observed in 
 regionserver metrics, but, we recently added logging for long running 
 compactions, and this has exposed the issue in a new way, e.g.
 {noformat}
 2014-09-15 14:20:59,450 DEBUG 
 [regionserver8120-largeCompactions-1410813534627]
 compactions.Compactor: Compaction progress: 22683625/6808179 (333.18%), 
 rate=162.08 kB/sec
 {noformat}
 The 'rate' reported in such logging is consistent and what we were really 
 after, but the progress indication is clearly broken and should be fixed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-12653) Move TestRegionServerOnlineConfigChange TestConfigurationManager to Junit4 tests

2014-12-09 Thread Ashish Singhi (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-12653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14239130#comment-14239130
 ] 

Ashish Singhi commented on HBASE-12653:
---

-1's not related to patch.

 Move TestRegionServerOnlineConfigChange  TestConfigurationManager to Junit4 
 tests
 --

 Key: HBASE-12653
 URL: https://issues.apache.org/jira/browse/HBASE-12653
 Project: HBase
  Issue Type: Improvement
  Components: test
Affects Versions: 2.0.0, 0.99.2
Reporter: Ashish Singhi
Assignee: Ashish Singhi
Priority: Minor
 Fix For: 1.0.0, 2.0.0

 Attachments: HBASE-12653.patch






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (HBASE-11677) Make Logger instance modifiers consistent

2014-12-09 Thread Usha Kuchibhotla (JIRA)

 [ 
https://issues.apache.org/jira/browse/HBASE-11677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Usha Kuchibhotla updated HBASE-11677:
-
Attachment: HBASE-11677.2.patch

 Make Logger instance modifiers consistent
 -

 Key: HBASE-11677
 URL: https://issues.apache.org/jira/browse/HBASE-11677
 Project: HBase
  Issue Type: Task
Reporter: Sean Busbey
Priority: Minor
  Labels: beginner, sonar
 Attachments: HBASE-11677.2.patch, HBASE-11677.patch


 We have some instances of Logger that are missing one of being private, 
 static, and final.
 ex from HealthChecker.java, missing final
 {code}
 private static Log LOG = LogFactory.getLog(HealthChecker.class);
 {code}
 * Clean up where possible by making {{private static final}}
 * If we can't, add a non-javadoc note about why
 One way to look for problematic instances is to grep for initial assignment 
 for the commonly used LOG member, e.g.
 * missing final: {{grep -r LOG = * | grep -v final}}
 * missing static: {{grep -r LOG = * | grep -v static}}
 * missing private: {{grep -r LOG = * | grep -v private}}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-11677) Make Logger instance modifiers consistent

2014-12-09 Thread Hadoop QA (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-11677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14239146#comment-14239146
 ] 

Hadoop QA commented on HBASE-11677:
---

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12685971/HBASE-11677.2.patch
  against master branch at commit b4371252fe71db938b37b7bc6391d0fb87466b36.
  ATTACHMENT ID: 12685971

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:green}+1 tests included{color}.  The patch appears to include 511 
new or modified tests.

{color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12013//console

This message is automatically generated.

 Make Logger instance modifiers consistent
 -

 Key: HBASE-11677
 URL: https://issues.apache.org/jira/browse/HBASE-11677
 Project: HBase
  Issue Type: Task
Reporter: Sean Busbey
Priority: Minor
  Labels: beginner, sonar
 Attachments: HBASE-11677.2.patch, HBASE-11677.patch


 We have some instances of Logger that are missing one of being private, 
 static, and final.
 ex from HealthChecker.java, missing final
 {code}
 private static Log LOG = LogFactory.getLog(HealthChecker.class);
 {code}
 * Clean up where possible by making {{private static final}}
 * If we can't, add a non-javadoc note about why
 One way to look for problematic instances is to grep for initial assignment 
 for the commonly used LOG member, e.g.
 * missing final: {{grep -r LOG = * | grep -v final}}
 * missing static: {{grep -r LOG = * | grep -v static}}
 * missing private: {{grep -r LOG = * | grep -v private}}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-12655) WALPerformanceEvaluation miscalculates append/sync statistics for multiple regions

2014-12-09 Thread Hadoop QA (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-12655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14239157#comment-14239157
 ] 

Hadoop QA commented on HBASE-12655:
---

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  
http://issues.apache.org/jira/secure/attachment/12685952/HBASE-12655.1.patch.txt
  against master branch at commit b4371252fe71db938b37b7bc6391d0fb87466b36.
  ATTACHMENT ID: 12685952

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:green}+1 tests included{color}.  The patch appears to include 7 new 
or modified tests.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 javadoc{color}.  The javadoc tool did not generate any 
warning messages.

{color:green}+1 checkstyle{color}.  The applied patch does not increase the 
total number of checkstyle errors

{color:green}+1 findbugs{color}.  The patch does not introduce any new 
Findbugs (version 2.0.3) warnings.

{color:red}-1 release audit{color}.  The applied patch generated 1 release 
audit warnings (more than the master's current 0 warnings).

{color:green}+1 lineLengths{color}.  The patch does not introduce lines 
longer than 100

  {color:green}+1 site{color}.  The mvn site goal succeeds with this patch.

{color:green}+1 core tests{color}.  The patch passed unit tests in .

Test results: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12011//testReport/
Release audit warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12011//artifact/patchprocess/patchReleaseAuditWarnings.txt
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12011//artifact/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12011//artifact/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12011//artifact/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12011//artifact/patchprocess/newPatchFindbugsWarningshbase-annotations.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12011//artifact/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12011//artifact/patchprocess/newPatchFindbugsWarningshbase-rest.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12011//artifact/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12011//artifact/patchprocess/newPatchFindbugsWarningshbase-thrift.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12011//artifact/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12011//artifact/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12011//artifact/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html
Checkstyle Errors: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12011//artifact/patchprocess/checkstyle-aggregate.html

  Console output: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12011//console

This message is automatically generated.

 WALPerformanceEvaluation miscalculates append/sync statistics for multiple 
 regions
 --

 Key: HBASE-12655
 URL: https://issues.apache.org/jira/browse/HBASE-12655
 Project: HBase
  Issue Type: Bug
  Components: wal
Affects Versions: 0.99.2
Reporter: Sean Busbey
Assignee: Sean Busbey
Priority: Minor
 Fix For: 1.0.0, 2.0.0

 Attachments: HBASE-12655.1.patch.txt


 Right now the WALPerformaceEvaluation tool sets up each new region by asking 
 for a WAL and then adding a listener. The listener updates running stats on 
 appends / syncs using a shared object in the evaluation tool.
 For WALProviders that reuse WALs (such as the default one always using a 
 single WAL), this results in adding a listener to WALs that already have 
 them. Each of those listeners is then updated on each append/sync.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-12661) rat check fails for MetricsReplicationSinkSource

2014-12-09 Thread Hadoop QA (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-12661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14239164#comment-14239164
 ] 

Hadoop QA commented on HBASE-12661:
---

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  
http://issues.apache.org/jira/secure/attachment/12685951/HBASE-12661.1.patch.txt
  against master branch at commit b4371252fe71db938b37b7bc6391d0fb87466b36.
  ATTACHMENT ID: 12685951

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:red}-1 tests included{color}.  The patch doesn't appear to include 
any new or modified tests.
Please justify why no new tests are needed for this 
patch.
Also please list what manual steps were performed to 
verify this patch.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 javadoc{color}.  The javadoc tool did not generate any 
warning messages.

{color:green}+1 checkstyle{color}.  The applied patch does not increase the 
total number of checkstyle errors

{color:green}+1 findbugs{color}.  The patch does not introduce any new 
Findbugs (version 2.0.3) warnings.

{color:red}-1 release audit{color}.  The applied patch generated 3 release 
audit warnings (more than the master's current 0 warnings).

{color:green}+1 lineLengths{color}.  The patch does not introduce lines 
longer than 100

  {color:green}+1 site{color}.  The mvn site goal succeeds with this patch.

{color:green}+1 core tests{color}.  The patch passed unit tests in .

 {color:red}-1 core zombie tests{color}.  There are 1 zombie test(s): 

Test results: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12012//testReport/
Release audit warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12012//artifact/patchprocess/patchReleaseAuditWarnings.txt
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12012//artifact/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12012//artifact/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12012//artifact/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12012//artifact/patchprocess/newPatchFindbugsWarningshbase-rest.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12012//artifact/patchprocess/newPatchFindbugsWarningshbase-thrift.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12012//artifact/patchprocess/newPatchFindbugsWarningshbase-annotations.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12012//artifact/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12012//artifact/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12012//artifact/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12012//artifact/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12012//artifact/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Checkstyle Errors: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12012//artifact/patchprocess/checkstyle-aggregate.html

  Console output: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12012//console

This message is automatically generated.

 rat check fails for MetricsReplicationSinkSource
 

 Key: HBASE-12661
 URL: https://issues.apache.org/jira/browse/HBASE-12661
 Project: HBase
  Issue Type: Bug
Affects Versions: 1.0.0, 2.0.0
Reporter: Sean Busbey
Assignee: Sean Busbey
Priority: Blocker
 Fix For: 1.0.0, 2.0.0

 Attachments: HBASE-12661.1.patch.txt


 newly added MetricsReplicationSinkSource is missing a license header.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (HBASE-11677) Make Logger instance modifiers consistent

2014-12-09 Thread Usha Kuchibhotla (JIRA)

 [ 
https://issues.apache.org/jira/browse/HBASE-11677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Usha Kuchibhotla updated HBASE-11677:
-
Attachment: HBASE-11677-v1.patch

 Make Logger instance modifiers consistent
 -

 Key: HBASE-11677
 URL: https://issues.apache.org/jira/browse/HBASE-11677
 Project: HBase
  Issue Type: Task
Reporter: Sean Busbey
Priority: Minor
  Labels: beginner, sonar
 Attachments: HBASE-11677-v1.patch, HBASE-11677.patch


 We have some instances of Logger that are missing one of being private, 
 static, and final.
 ex from HealthChecker.java, missing final
 {code}
 private static Log LOG = LogFactory.getLog(HealthChecker.class);
 {code}
 * Clean up where possible by making {{private static final}}
 * If we can't, add a non-javadoc note about why
 One way to look for problematic instances is to grep for initial assignment 
 for the commonly used LOG member, e.g.
 * missing final: {{grep -r LOG = * | grep -v final}}
 * missing static: {{grep -r LOG = * | grep -v static}}
 * missing private: {{grep -r LOG = * | grep -v private}}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (HBASE-11677) Make Logger instance modifiers consistent

2014-12-09 Thread Usha Kuchibhotla (JIRA)

 [ 
https://issues.apache.org/jira/browse/HBASE-11677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Usha Kuchibhotla updated HBASE-11677:
-
Attachment: (was: HBASE-11677.2.patch)

 Make Logger instance modifiers consistent
 -

 Key: HBASE-11677
 URL: https://issues.apache.org/jira/browse/HBASE-11677
 Project: HBase
  Issue Type: Task
Reporter: Sean Busbey
Priority: Minor
  Labels: beginner, sonar
 Attachments: HBASE-11677-v1.patch, HBASE-11677.patch


 We have some instances of Logger that are missing one of being private, 
 static, and final.
 ex from HealthChecker.java, missing final
 {code}
 private static Log LOG = LogFactory.getLog(HealthChecker.class);
 {code}
 * Clean up where possible by making {{private static final}}
 * If we can't, add a non-javadoc note about why
 One way to look for problematic instances is to grep for initial assignment 
 for the commonly used LOG member, e.g.
 * missing final: {{grep -r LOG = * | grep -v final}}
 * missing static: {{grep -r LOG = * | grep -v static}}
 * missing private: {{grep -r LOG = * | grep -v private}}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-11677) Make Logger instance modifiers consistent

2014-12-09 Thread Hadoop QA (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-11677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14239170#comment-14239170
 ] 

Hadoop QA commented on HBASE-11677:
---

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12685975/HBASE-11677-v1.patch
  against master branch at commit b4371252fe71db938b37b7bc6391d0fb87466b36.
  ATTACHMENT ID: 12685975

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:green}+1 tests included{color}.  The patch appears to include 511 
new or modified tests.

{color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12014//console

This message is automatically generated.

 Make Logger instance modifiers consistent
 -

 Key: HBASE-11677
 URL: https://issues.apache.org/jira/browse/HBASE-11677
 Project: HBase
  Issue Type: Task
Reporter: Sean Busbey
Priority: Minor
  Labels: beginner, sonar
 Attachments: HBASE-11677-v1.patch, HBASE-11677.patch


 We have some instances of Logger that are missing one of being private, 
 static, and final.
 ex from HealthChecker.java, missing final
 {code}
 private static Log LOG = LogFactory.getLog(HealthChecker.class);
 {code}
 * Clean up where possible by making {{private static final}}
 * If we can't, add a non-javadoc note about why
 One way to look for problematic instances is to grep for initial assignment 
 for the commonly used LOG member, e.g.
 * missing final: {{grep -r LOG = * | grep -v final}}
 * missing static: {{grep -r LOG = * | grep -v static}}
 * missing private: {{grep -r LOG = * | grep -v private}}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-12597) Add RpcClient interface and enable changing of RpcClient implementation

2014-12-09 Thread Jurriaan Mous (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-12597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14239230#comment-14239230
 ] 

Jurriaan Mous commented on HBASE-12597:
---

Thanks for the commit! :)
Would it be possible to do a new SNAPSHOT release so I could more easily use it 
in the async client?

 Add RpcClient interface and enable changing of RpcClient implementation
 ---

 Key: HBASE-12597
 URL: https://issues.apache.org/jira/browse/HBASE-12597
 Project: HBase
  Issue Type: Improvement
  Components: Client
Reporter: Jurriaan Mous
Assignee: Jurriaan Mous
 Fix For: 1.0.0, 2.0.0

 Attachments: HBASE-12597-v1.patch, HBASE-12597-v2.patch, 
 HBASE-12597-v3.patch, HBASE-12597-v4.patch, HBASE-12597-v4.patch, 
 HBASE-12597-v5.patch, HBASE-12597-v6.patch, HBASE-12597-v7.patch, 
 HBASE-12597-v8-branch-1.patch, HBASE-12597-v8.patch, HBASE-12597.patch


 Currently HConnectionImplementation works with the included RpcClient which 
 is a direct implementation and not defined by an interface.
 It would be great to be able to swap out the default RpcClient with another 
 implementation which can also be controlled by the default 
 HConnectionImplementation. 
 Suggested changes:
 - Create a RpcClient interface which defines all the ways 
 HConnectionImplementation interacts with an RPC client. Like getting a 
 blocking protobuf service interface or closing the client.
 - Define which RpcClient implementation to construct by setting a 
 configuration variable which defaults to the current RpcClient.
 - Possibly create an abstract RpcClient class to only load all the basic Rpc 
 layer configurations to be used in an implementation.
 Why? It enables experimentation with RpcClients which could enable new 
 features or could be more performant than the included client. 
 I created a new RpcClient implementation based on Netty which can also be 
 called asynchronously. It would be great to also be able to use this 
 RpcClient in all the default ways and tests to see if there are any issues 
 with it. 
 https://github.com/jurmous/async-hbase-client/
 https://github.com/jurmous/async-hbase-client/blob/master/src/main/java/org/apache/hadoop/hbase/ipc/AsyncRpcClient.java



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (HBASE-12564) consolidate the getTableDescriptors() semantic

2014-12-09 Thread Matteo Bertozzi (JIRA)

 [ 
https://issues.apache.org/jira/browse/HBASE-12564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Matteo Bertozzi updated HBASE-12564:

   Resolution: Fixed
Fix Version/s: 1.0.0
   Status: Resolved  (was: Patch Available)

 consolidate the getTableDescriptors() semantic
 --

 Key: HBASE-12564
 URL: https://issues.apache.org/jira/browse/HBASE-12564
 Project: HBase
  Issue Type: Bug
  Components: Client, master
Affects Versions: 2.0.0
Reporter: Matteo Bertozzi
Assignee: Matteo Bertozzi
Priority: Minor
 Fix For: 1.0.0, 2.0.0

 Attachments: HBASE-12564-v0.patch, HBASE-12564-v1.patch, 
 HBASE-12564-v2.patch


 Master getTableDescriptors() which is called by Admin.listTables() has a 
 couple of different behaviors depending on how it is called. 
 after HBASE-12073 with the AccessController enabled, we now get a global 
 admin required if listTables() is called without a regex otherwise we return 
 only the table that the user can see (we show only the tables that the user 
 have access to, which means or the user is a global admin or it has a 
 table-level create/admin). We probably should have the second behavior even 
 without regex, since I should able to see my own tables. 
 getTableDescriptors() is returning only non system tables. Tools like 
 user_permission that are doing for each listTable(): userPerm(table) are 
 losing the system tables, so stuff like user_permission 'hbase:acls' will not 
 result any result.  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (HBASE-12583) Allow creating reference files even the split row not lies in the storefile range if required

2014-12-09 Thread rajeshbabu (JIRA)

 [ 
https://issues.apache.org/jira/browse/HBASE-12583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

rajeshbabu updated HBASE-12583:
---
Attachment: HBASE-12583_98_v2.patch
HBASE-12583_branch1_v2.patch

 Allow creating reference files even the split row not lies in the storefile 
 range if required
 -

 Key: HBASE-12583
 URL: https://issues.apache.org/jira/browse/HBASE-12583
 Project: HBase
  Issue Type: Improvement
Reporter: rajeshbabu
Assignee: rajeshbabu
  Labels: Phoenix
 Fix For: 1.0.0, 2.0.0, 0.98.9

 Attachments: HBASE-12583.patch, HBASE-12583_98.patch, 
 HBASE-12583_98_v2.patch, HBASE-12583_branch1.patch, 
 HBASE-12583_branch1_v2.patch, HBASE-12583_v2.patch


 Currently in HRegionFileSystem#splitStoreFile we are not creating reference 
 files if the split row not lies in the storefile range that means one of the 
 child region doesn't have any data.
 {code}
// Check whether the split row lies in the range of the store file
 // If it is outside the range, return directly.
 if (top) {
   //check if larger than last key.
   KeyValue splitKey = KeyValueUtil.createFirstOnRow(splitRow);
   byte[] lastKey = f.createReader().getLastKey();
   // If lastKey is null means storefile is empty.
   if (lastKey == null) return null;
   if (f.getReader().getComparator().compareFlatKey(splitKey.getBuffer(),
   splitKey.getKeyOffset(), splitKey.getKeyLength(), lastKey, 0, 
 lastKey.length)  0) {
 return null;
   }
 } else {
   //check if smaller than first key
   KeyValue splitKey = KeyValueUtil.createLastOnRow(splitRow);
   byte[] firstKey = f.createReader().getFirstKey();
   // If firstKey is null means storefile is empty.
   if (firstKey == null) return null;
   if (f.getReader().getComparator().compareFlatKey(splitKey.getBuffer(),
   splitKey.getKeyOffset(), splitKey.getKeyLength(), firstKey, 0, 
 firstKey.length)  0) {
 return null;
   }
 }
 {code}
 In some cases when split row should be compared with part of rowkey(in 
 composite rowkey) mainly for secondary index tables we need to create 
 reference files even when split row not lies in the storefile range so that 
 they can be rewritten to it's child regions by some custom half store file 
 reader which compare the part of row key with split row.
 The check of comparing split row with storefile range and returning directly 
 can be avoided by having special boolean attribute in table descriptor when 
 it set to true. Or else we can have coprocessor hooks so that in the hooks we 
 can create the references and bypass.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (HBASE-12583) Allow creating reference files even the split row not lies in the storefile range if required

2014-12-09 Thread rajeshbabu (JIRA)

 [ 
https://issues.apache.org/jira/browse/HBASE-12583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

rajeshbabu updated HBASE-12583:
---
Attachment: HBASE-12583_v3.patch

Here are the patches addressing Stack's comment. Passing split policy instead 
of boolean for HRegionFileSystem#splitStoreFile.


 Allow creating reference files even the split row not lies in the storefile 
 range if required
 -

 Key: HBASE-12583
 URL: https://issues.apache.org/jira/browse/HBASE-12583
 Project: HBase
  Issue Type: Improvement
Reporter: rajeshbabu
Assignee: rajeshbabu
  Labels: Phoenix
 Fix For: 1.0.0, 2.0.0, 0.98.9

 Attachments: HBASE-12583.patch, HBASE-12583_98.patch, 
 HBASE-12583_98_v2.patch, HBASE-12583_branch1.patch, 
 HBASE-12583_branch1_v2.patch, HBASE-12583_v2.patch, HBASE-12583_v3.patch


 Currently in HRegionFileSystem#splitStoreFile we are not creating reference 
 files if the split row not lies in the storefile range that means one of the 
 child region doesn't have any data.
 {code}
// Check whether the split row lies in the range of the store file
 // If it is outside the range, return directly.
 if (top) {
   //check if larger than last key.
   KeyValue splitKey = KeyValueUtil.createFirstOnRow(splitRow);
   byte[] lastKey = f.createReader().getLastKey();
   // If lastKey is null means storefile is empty.
   if (lastKey == null) return null;
   if (f.getReader().getComparator().compareFlatKey(splitKey.getBuffer(),
   splitKey.getKeyOffset(), splitKey.getKeyLength(), lastKey, 0, 
 lastKey.length)  0) {
 return null;
   }
 } else {
   //check if smaller than first key
   KeyValue splitKey = KeyValueUtil.createLastOnRow(splitRow);
   byte[] firstKey = f.createReader().getFirstKey();
   // If firstKey is null means storefile is empty.
   if (firstKey == null) return null;
   if (f.getReader().getComparator().compareFlatKey(splitKey.getBuffer(),
   splitKey.getKeyOffset(), splitKey.getKeyLength(), firstKey, 0, 
 firstKey.length)  0) {
 return null;
   }
 }
 {code}
 In some cases when split row should be compared with part of rowkey(in 
 composite rowkey) mainly for secondary index tables we need to create 
 reference files even when split row not lies in the storefile range so that 
 they can be rewritten to it's child regions by some custom half store file 
 reader which compare the part of row key with split row.
 The check of comparing split row with storefile range and returning directly 
 can be avoided by having special boolean attribute in table descriptor when 
 it set to true. Or else we can have coprocessor hooks so that in the hooks we 
 can create the references and bypass.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Created] (HBASE-12662) region_status.rb is failing with NoMethodError

2014-12-09 Thread Ashish Singhi (JIRA)
Ashish Singhi created HBASE-12662:
-

 Summary: region_status.rb is failing with NoMethodError
 Key: HBASE-12662
 URL: https://issues.apache.org/jira/browse/HBASE-12662
 Project: HBase
  Issue Type: Bug
  Components: shell
Affects Versions: 2.0.0
Reporter: Ashish Singhi
Assignee: Ashish Singhi


{noformat}
$/hbase-2.0.0-SNAPSHOT/bin hbase org.jruby.Main region_status.rb --table t
2014-12-09 19:33:06,839 WARN  [main] util.NativeCodeLoader: Unable to load 
native-hadoop library for your platform... using builtin-java classes where 
applicable
NoMethodError: undefined method `cache_blocks=' for 
#Java::OrgApacheHadoopHbaseClient::Scan:0x1c7abd4c
  (root) at region_status.rb:93
{noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (HBASE-12662) region_status.rb is failing with NoMethodError

2014-12-09 Thread Ashish Singhi (JIRA)

 [ 
https://issues.apache.org/jira/browse/HBASE-12662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ashish Singhi updated HBASE-12662:
--
Attachment: HBASE-12662.patch

Tested manually with the patch on trunk build, it is working fine.

 region_status.rb is failing with NoMethodError
 --

 Key: HBASE-12662
 URL: https://issues.apache.org/jira/browse/HBASE-12662
 Project: HBase
  Issue Type: Bug
  Components: shell
Affects Versions: 2.0.0
Reporter: Ashish Singhi
Assignee: Ashish Singhi
 Attachments: HBASE-12662.patch


 {noformat}
 $/hbase-2.0.0-SNAPSHOT/bin hbase org.jruby.Main region_status.rb --table t
 2014-12-09 19:33:06,839 WARN  [main] util.NativeCodeLoader: Unable to load 
 native-hadoop library for your platform... using builtin-java classes where 
 applicable
 NoMethodError: undefined method `cache_blocks=' for 
 #Java::OrgApacheHadoopHbaseClient::Scan:0x1c7abd4c
   (root) at region_status.rb:93
 {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-12564) consolidate the getTableDescriptors() semantic

2014-12-09 Thread Hudson (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-12564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14239453#comment-14239453
 ] 

Hudson commented on HBASE-12564:


FAILURE: Integrated in HBase-TRUNK #5891 (See 
[https://builds.apache.org/job/HBase-TRUNK/5891/])
HBASE-12564 consolidate the getTableDescriptors() semantic (matteo.bertozzi: 
rev 8a2c84156a2829f44307e5aff07323902580af86)
* 
hbase-server/src/main/java/org/apache/hadoop/hbase/coprocessor/MasterObserver.java
* hbase-client/src/main/java/org/apache/hadoop/hbase/client/HBaseAdmin.java
* 
hbase-server/src/main/java/org/apache/hadoop/hbase/security/access/AccessController.java
* 
hbase-client/src/main/java/org/apache/hadoop/hbase/client/ConnectionAdapter.java
* 
hbase-server/src/main/java/org/apache/hadoop/hbase/master/MasterRpcServices.java
* 
hbase-server/src/main/java/org/apache/hadoop/hbase/coprocessor/BaseMasterAndRegionObserver.java
* hbase-client/src/main/java/org/apache/hadoop/hbase/client/Admin.java
* 
hbase-client/src/main/java/org/apache/hadoop/hbase/security/access/AccessControlClient.java
* 
hbase-client/src/main/java/org/apache/hadoop/hbase/client/ConnectionManager.java
* 
hbase-protocol/src/main/java/org/apache/hadoop/hbase/protobuf/generated/MasterProtos.java
* hbase-protocol/src/main/protobuf/Master.proto
* 
hbase-server/src/test/java/org/apache/hadoop/hbase/coprocessor/TestMasterObserver.java
* hbase-shell/src/main/ruby/hbase/admin.rb
* 
hbase-server/src/main/java/org/apache/hadoop/hbase/master/MasterCoprocessorHost.java
* hbase-server/src/main/java/org/apache/hadoop/hbase/master/HMaster.java
* hbase-client/src/main/java/org/apache/hadoop/hbase/client/HConnection.java
* 
hbase-server/src/test/java/org/apache/hadoop/hbase/security/access/TestAccessController.java
* 
hbase-server/src/main/java/org/apache/hadoop/hbase/security/access/TableAuthManager.java
* 
hbase-client/src/main/java/org/apache/hadoop/hbase/protobuf/RequestConverter.java
* 
hbase-server/src/main/java/org/apache/hadoop/hbase/coprocessor/BaseMasterObserver.java


 consolidate the getTableDescriptors() semantic
 --

 Key: HBASE-12564
 URL: https://issues.apache.org/jira/browse/HBASE-12564
 Project: HBase
  Issue Type: Bug
  Components: Client, master
Affects Versions: 2.0.0
Reporter: Matteo Bertozzi
Assignee: Matteo Bertozzi
Priority: Minor
 Fix For: 1.0.0, 2.0.0

 Attachments: HBASE-12564-v0.patch, HBASE-12564-v1.patch, 
 HBASE-12564-v2.patch


 Master getTableDescriptors() which is called by Admin.listTables() has a 
 couple of different behaviors depending on how it is called. 
 after HBASE-12073 with the AccessController enabled, we now get a global 
 admin required if listTables() is called without a regex otherwise we return 
 only the table that the user can see (we show only the tables that the user 
 have access to, which means or the user is a global admin or it has a 
 table-level create/admin). We probably should have the second behavior even 
 without regex, since I should able to see my own tables. 
 getTableDescriptors() is returning only non system tables. Tools like 
 user_permission that are doing for each listTable(): userPerm(table) are 
 losing the system tables, so stuff like user_permission 'hbase:acls' will not 
 result any result.  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-12583) Allow creating reference files even the split row not lies in the storefile range if required

2014-12-09 Thread Hudson (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-12583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14239457#comment-14239457
 ] 

Hudson commented on HBASE-12583:


FAILURE: Integrated in HBase-0.98-on-Hadoop-1.1 #695 (See 
[https://builds.apache.org/job/HBase-0.98-on-Hadoop-1.1/695/])
HBASE-12583 Allow creating reference files even the split row not lies in the 
storefile range if required(Rajeshbabu) (rajeshbabu: rev 
0e3d4cd71bd1de622a00ab05bb047a97d9e15b7e)
* 
hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/RegionSplitPolicy.java
* 
hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestStoreFile.java
* 
hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/HRegionFileSystem.java
* 
hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestSplitTransactionOnCluster.java
* hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/HRegion.java
* 
hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/SplitTransaction.java


 Allow creating reference files even the split row not lies in the storefile 
 range if required
 -

 Key: HBASE-12583
 URL: https://issues.apache.org/jira/browse/HBASE-12583
 Project: HBase
  Issue Type: Improvement
Reporter: rajeshbabu
Assignee: rajeshbabu
  Labels: Phoenix
 Fix For: 1.0.0, 2.0.0, 0.98.9

 Attachments: HBASE-12583.patch, HBASE-12583_98.patch, 
 HBASE-12583_98_v2.patch, HBASE-12583_branch1.patch, 
 HBASE-12583_branch1_v2.patch, HBASE-12583_v2.patch, HBASE-12583_v3.patch


 Currently in HRegionFileSystem#splitStoreFile we are not creating reference 
 files if the split row not lies in the storefile range that means one of the 
 child region doesn't have any data.
 {code}
// Check whether the split row lies in the range of the store file
 // If it is outside the range, return directly.
 if (top) {
   //check if larger than last key.
   KeyValue splitKey = KeyValueUtil.createFirstOnRow(splitRow);
   byte[] lastKey = f.createReader().getLastKey();
   // If lastKey is null means storefile is empty.
   if (lastKey == null) return null;
   if (f.getReader().getComparator().compareFlatKey(splitKey.getBuffer(),
   splitKey.getKeyOffset(), splitKey.getKeyLength(), lastKey, 0, 
 lastKey.length)  0) {
 return null;
   }
 } else {
   //check if smaller than first key
   KeyValue splitKey = KeyValueUtil.createLastOnRow(splitRow);
   byte[] firstKey = f.createReader().getFirstKey();
   // If firstKey is null means storefile is empty.
   if (firstKey == null) return null;
   if (f.getReader().getComparator().compareFlatKey(splitKey.getBuffer(),
   splitKey.getKeyOffset(), splitKey.getKeyLength(), firstKey, 0, 
 firstKey.length)  0) {
 return null;
   }
 }
 {code}
 In some cases when split row should be compared with part of rowkey(in 
 composite rowkey) mainly for secondary index tables we need to create 
 reference files even when split row not lies in the storefile range so that 
 they can be rewritten to it's child regions by some custom half store file 
 reader which compare the part of row key with split row.
 The check of comparing split row with storefile range and returning directly 
 can be avoided by having special boolean attribute in table descriptor when 
 it set to true. Or else we can have coprocessor hooks so that in the hooks we 
 can create the references and bypass.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-12583) Allow creating reference files even the split row not lies in the storefile range if required

2014-12-09 Thread Anoop Sam John (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-12583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14239460#comment-14239460
 ] 

Anoop Sam John commented on HBASE-12583:


This is committed already?
minor comments in javadoc.
{quote}
In {@link HRegionFileSystem#splitStoreFile(org.apache.hadoop.hbase.HRegionInfo,
   * String, StoreFile, byte[], boolean)} 
{quote}
Pls correct the signature. Split policy at end. You will get javadoc warn here

But some use cases we may  - But in some use cases we may 
even the split row not lies in the range - even when
StoreRile range check  - StoreFile
or or not - or not
This method can be used to whether - This method can be used to decide, 
whether 

 Allow creating reference files even the split row not lies in the storefile 
 range if required
 -

 Key: HBASE-12583
 URL: https://issues.apache.org/jira/browse/HBASE-12583
 Project: HBase
  Issue Type: Improvement
Reporter: rajeshbabu
Assignee: rajeshbabu
  Labels: Phoenix
 Fix For: 1.0.0, 2.0.0, 0.98.9

 Attachments: HBASE-12583.patch, HBASE-12583_98.patch, 
 HBASE-12583_98_v2.patch, HBASE-12583_branch1.patch, 
 HBASE-12583_branch1_v2.patch, HBASE-12583_v2.patch, HBASE-12583_v3.patch


 Currently in HRegionFileSystem#splitStoreFile we are not creating reference 
 files if the split row not lies in the storefile range that means one of the 
 child region doesn't have any data.
 {code}
// Check whether the split row lies in the range of the store file
 // If it is outside the range, return directly.
 if (top) {
   //check if larger than last key.
   KeyValue splitKey = KeyValueUtil.createFirstOnRow(splitRow);
   byte[] lastKey = f.createReader().getLastKey();
   // If lastKey is null means storefile is empty.
   if (lastKey == null) return null;
   if (f.getReader().getComparator().compareFlatKey(splitKey.getBuffer(),
   splitKey.getKeyOffset(), splitKey.getKeyLength(), lastKey, 0, 
 lastKey.length)  0) {
 return null;
   }
 } else {
   //check if smaller than first key
   KeyValue splitKey = KeyValueUtil.createLastOnRow(splitRow);
   byte[] firstKey = f.createReader().getFirstKey();
   // If firstKey is null means storefile is empty.
   if (firstKey == null) return null;
   if (f.getReader().getComparator().compareFlatKey(splitKey.getBuffer(),
   splitKey.getKeyOffset(), splitKey.getKeyLength(), firstKey, 0, 
 firstKey.length)  0) {
 return null;
   }
 }
 {code}
 In some cases when split row should be compared with part of rowkey(in 
 composite rowkey) mainly for secondary index tables we need to create 
 reference files even when split row not lies in the storefile range so that 
 they can be rewritten to it's child regions by some custom half store file 
 reader which compare the part of row key with split row.
 The check of comparing split row with storefile range and returning directly 
 can be avoided by having special boolean attribute in table descriptor when 
 it set to true. Or else we can have coprocessor hooks so that in the hooks we 
 can create the references and bypass.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (HBASE-12661) rat check fails for several files

2014-12-09 Thread Sean Busbey (JIRA)

 [ 
https://issues.apache.org/jira/browse/HBASE-12661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sean Busbey updated HBASE-12661:

Description: 
newly added files missing a license header:

* MetricsReplicationSinkSource
* MetricsReplicationSourceFactoryImpl
* MetricsReplicationSourceSourceImpl
* TestMetricsReplicationSourceFactoryImpl

  was:newly added MetricsReplicationSinkSource is missing a license header.

Summary: rat check fails for several files  (was: rat check fails for 
MetricsReplicationSinkSource)

 rat check fails for several files
 -

 Key: HBASE-12661
 URL: https://issues.apache.org/jira/browse/HBASE-12661
 Project: HBase
  Issue Type: Bug
Affects Versions: 1.0.0, 2.0.0
Reporter: Sean Busbey
Assignee: Sean Busbey
Priority: Blocker
 Fix For: 1.0.0, 2.0.0

 Attachments: HBASE-12661.1.patch.txt


 newly added files missing a license header:
 * MetricsReplicationSinkSource
 * MetricsReplicationSourceFactoryImpl
 * MetricsReplicationSourceSourceImpl
 * TestMetricsReplicationSourceFactoryImpl



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (HBASE-12661) rat check fails for several files

2014-12-09 Thread Sean Busbey (JIRA)

 [ 
https://issues.apache.org/jira/browse/HBASE-12661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sean Busbey updated HBASE-12661:

Status: Patch Available  (was: Open)

 rat check fails for several files
 -

 Key: HBASE-12661
 URL: https://issues.apache.org/jira/browse/HBASE-12661
 Project: HBase
  Issue Type: Bug
Affects Versions: 1.0.0, 2.0.0
Reporter: Sean Busbey
Assignee: Sean Busbey
Priority: Blocker
 Fix For: 1.0.0, 2.0.0

 Attachments: HBASE-12661.1.patch.txt, HBASE-12661.2.patch.txt


 newly added files missing a license header:
 * MetricsReplicationSinkSource
 * MetricsReplicationSourceFactoryImpl
 * MetricsReplicationSourceSourceImpl
 * TestMetricsReplicationSourceFactoryImpl



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (HBASE-12661) rat check fails for several files

2014-12-09 Thread Sean Busbey (JIRA)

 [ 
https://issues.apache.org/jira/browse/HBASE-12661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sean Busbey updated HBASE-12661:

Status: Open  (was: Patch Available)

 rat check fails for several files
 -

 Key: HBASE-12661
 URL: https://issues.apache.org/jira/browse/HBASE-12661
 Project: HBase
  Issue Type: Bug
Affects Versions: 1.0.0, 2.0.0
Reporter: Sean Busbey
Assignee: Sean Busbey
Priority: Blocker
 Fix For: 1.0.0, 2.0.0

 Attachments: HBASE-12661.1.patch.txt, HBASE-12661.2.patch.txt


 newly added files missing a license header:
 * MetricsReplicationSinkSource
 * MetricsReplicationSourceFactoryImpl
 * MetricsReplicationSourceSourceImpl
 * TestMetricsReplicationSourceFactoryImpl



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (HBASE-12661) rat check fails for several files

2014-12-09 Thread Sean Busbey (JIRA)

 [ 
https://issues.apache.org/jira/browse/HBASE-12661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sean Busbey updated HBASE-12661:

Attachment: HBASE-12661.2.patch.txt

manually running apache-rat:check passes now.

 rat check fails for several files
 -

 Key: HBASE-12661
 URL: https://issues.apache.org/jira/browse/HBASE-12661
 Project: HBase
  Issue Type: Bug
Affects Versions: 1.0.0, 2.0.0
Reporter: Sean Busbey
Assignee: Sean Busbey
Priority: Blocker
 Fix For: 1.0.0, 2.0.0

 Attachments: HBASE-12661.1.patch.txt, HBASE-12661.2.patch.txt


 newly added files missing a license header:
 * MetricsReplicationSinkSource
 * MetricsReplicationSourceFactoryImpl
 * MetricsReplicationSourceSourceImpl
 * TestMetricsReplicationSourceFactoryImpl



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-12655) WALPerformanceEvaluation miscalculates append/sync statistics for multiple regions

2014-12-09 Thread Sean Busbey (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-12655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14239465#comment-14239465
 ] 

Sean Busbey commented on HBASE-12655:
-

the release audit is HBASE-12661.

 WALPerformanceEvaluation miscalculates append/sync statistics for multiple 
 regions
 --

 Key: HBASE-12655
 URL: https://issues.apache.org/jira/browse/HBASE-12655
 Project: HBase
  Issue Type: Bug
  Components: wal
Affects Versions: 0.99.2
Reporter: Sean Busbey
Assignee: Sean Busbey
Priority: Minor
 Fix For: 1.0.0, 2.0.0

 Attachments: HBASE-12655.1.patch.txt


 Right now the WALPerformaceEvaluation tool sets up each new region by asking 
 for a WAL and then adding a listener. The listener updates running stats on 
 appends / syncs using a shared object in the evaluation tool.
 For WALProviders that reuse WALs (such as the default one always using a 
 single WAL), this results in adding a listener to WALs that already have 
 them. Each of those listeners is then updated on each append/sync.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-12655) WALPerformanceEvaluation miscalculates append/sync statistics for multiple regions

2014-12-09 Thread stack (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-12655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14239499#comment-14239499
 ] 

stack commented on HBASE-12655:
---

+1

 WALPerformanceEvaluation miscalculates append/sync statistics for multiple 
 regions
 --

 Key: HBASE-12655
 URL: https://issues.apache.org/jira/browse/HBASE-12655
 Project: HBase
  Issue Type: Bug
  Components: wal
Affects Versions: 0.99.2
Reporter: Sean Busbey
Assignee: Sean Busbey
Priority: Minor
 Fix For: 1.0.0, 2.0.0

 Attachments: HBASE-12655.1.patch.txt


 Right now the WALPerformaceEvaluation tool sets up each new region by asking 
 for a WAL and then adding a listener. The listener updates running stats on 
 appends / syncs using a shared object in the evaluation tool.
 For WALProviders that reuse WALs (such as the default one always using a 
 single WAL), this results in adding a listener to WALs that already have 
 them. Each of those listeners is then updated on each append/sync.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-12661) rat check fails for several files

2014-12-09 Thread stack (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-12661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14239501#comment-14239501
 ] 

stack commented on HBASE-12661:
---

+1

 rat check fails for several files
 -

 Key: HBASE-12661
 URL: https://issues.apache.org/jira/browse/HBASE-12661
 Project: HBase
  Issue Type: Bug
Affects Versions: 1.0.0, 2.0.0
Reporter: Sean Busbey
Assignee: Sean Busbey
Priority: Blocker
 Fix For: 1.0.0, 2.0.0

 Attachments: HBASE-12661.1.patch.txt, HBASE-12661.2.patch.txt


 newly added files missing a license header:
 * MetricsReplicationSinkSource
 * MetricsReplicationSourceFactoryImpl
 * MetricsReplicationSourceSourceImpl
 * TestMetricsReplicationSourceFactoryImpl



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-12564) consolidate the getTableDescriptors() semantic

2014-12-09 Thread stack (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-12564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14239503#comment-14239503
 ] 

stack commented on HBASE-12564:
---

ok. +1 again.

 consolidate the getTableDescriptors() semantic
 --

 Key: HBASE-12564
 URL: https://issues.apache.org/jira/browse/HBASE-12564
 Project: HBase
  Issue Type: Bug
  Components: Client, master
Affects Versions: 2.0.0
Reporter: Matteo Bertozzi
Assignee: Matteo Bertozzi
Priority: Minor
 Fix For: 1.0.0, 2.0.0

 Attachments: HBASE-12564-v0.patch, HBASE-12564-v1.patch, 
 HBASE-12564-v2.patch


 Master getTableDescriptors() which is called by Admin.listTables() has a 
 couple of different behaviors depending on how it is called. 
 after HBASE-12073 with the AccessController enabled, we now get a global 
 admin required if listTables() is called without a regex otherwise we return 
 only the table that the user can see (we show only the tables that the user 
 have access to, which means or the user is a global admin or it has a 
 table-level create/admin). We probably should have the second behavior even 
 without regex, since I should able to see my own tables. 
 getTableDescriptors() is returning only non system tables. Tools like 
 user_permission that are doing for each listTable(): userPerm(table) are 
 losing the system tables, so stuff like user_permission 'hbase:acls' will not 
 result any result.  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-12583) Allow creating reference files even the split row not lies in the storefile range if required

2014-12-09 Thread Hadoop QA (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-12583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14239521#comment-14239521
 ] 

Hadoop QA commented on HBASE-12583:
---

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12686006/HBASE-12583_v3.patch
  against master branch at commit 8a2c84156a2829f44307e5aff07323902580af86.
  ATTACHMENT ID: 12686006

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:green}+1 tests included{color}.  The patch appears to include 6 new 
or modified tests.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 javadoc{color}.  The javadoc tool did not generate any 
warning messages.

{color:green}+1 checkstyle{color}.  The applied patch does not increase the 
total number of checkstyle errors

{color:green}+1 findbugs{color}.  The patch does not introduce any new 
Findbugs (version 2.0.3) warnings.

{color:red}-1 release audit{color}.  The applied patch generated 1 release 
audit warnings (more than the master's current 0 warnings).

{color:green}+1 lineLengths{color}.  The patch does not introduce lines 
longer than 100

  {color:green}+1 site{color}.  The mvn site goal succeeds with this patch.

{color:green}+1 core tests{color}.  The patch passed unit tests in .

Test results: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12015//testReport/
Release audit warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12015//artifact/patchprocess/patchReleaseAuditWarnings.txt
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12015//artifact/patchprocess/newPatchFindbugsWarningshbase-rest.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12015//artifact/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12015//artifact/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12015//artifact/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12015//artifact/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12015//artifact/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12015//artifact/patchprocess/newPatchFindbugsWarningshbase-thrift.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12015//artifact/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12015//artifact/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12015//artifact/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12015//artifact/patchprocess/newPatchFindbugsWarningshbase-annotations.html
Checkstyle Errors: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12015//artifact/patchprocess/checkstyle-aggregate.html

  Console output: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12015//console

This message is automatically generated.

 Allow creating reference files even the split row not lies in the storefile 
 range if required
 -

 Key: HBASE-12583
 URL: https://issues.apache.org/jira/browse/HBASE-12583
 Project: HBase
  Issue Type: Improvement
Reporter: rajeshbabu
Assignee: rajeshbabu
  Labels: Phoenix
 Fix For: 1.0.0, 2.0.0, 0.98.9

 Attachments: HBASE-12583.patch, HBASE-12583_98.patch, 
 HBASE-12583_98_v2.patch, HBASE-12583_branch1.patch, 
 HBASE-12583_branch1_v2.patch, HBASE-12583_v2.patch, HBASE-12583_v3.patch


 Currently in HRegionFileSystem#splitStoreFile we are not creating reference 
 files if the split row not lies in the storefile range that means one of the 
 child region doesn't have any data.
 {code}
// Check whether the split row lies in the range of the store file
 // If it is outside the range, return directly.
 if (top) {
   //check if larger than last key.
   KeyValue splitKey = KeyValueUtil.createFirstOnRow(splitRow);
   byte[] lastKey = f.createReader().getLastKey();
   // If lastKey is null means storefile is empty.
   if 

[jira] [Commented] (HBASE-12597) Add RpcClient interface and enable changing of RpcClient implementation

2014-12-09 Thread stack (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-12597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14239523#comment-14239523
 ] 

stack commented on HBASE-12597:
---

I pushed a 1.0.0-SNAPSHOT [~jurmous]  Let me know if issue.

 Add RpcClient interface and enable changing of RpcClient implementation
 ---

 Key: HBASE-12597
 URL: https://issues.apache.org/jira/browse/HBASE-12597
 Project: HBase
  Issue Type: Improvement
  Components: Client
Reporter: Jurriaan Mous
Assignee: Jurriaan Mous
 Fix For: 1.0.0, 2.0.0

 Attachments: HBASE-12597-v1.patch, HBASE-12597-v2.patch, 
 HBASE-12597-v3.patch, HBASE-12597-v4.patch, HBASE-12597-v4.patch, 
 HBASE-12597-v5.patch, HBASE-12597-v6.patch, HBASE-12597-v7.patch, 
 HBASE-12597-v8-branch-1.patch, HBASE-12597-v8.patch, HBASE-12597.patch


 Currently HConnectionImplementation works with the included RpcClient which 
 is a direct implementation and not defined by an interface.
 It would be great to be able to swap out the default RpcClient with another 
 implementation which can also be controlled by the default 
 HConnectionImplementation. 
 Suggested changes:
 - Create a RpcClient interface which defines all the ways 
 HConnectionImplementation interacts with an RPC client. Like getting a 
 blocking protobuf service interface or closing the client.
 - Define which RpcClient implementation to construct by setting a 
 configuration variable which defaults to the current RpcClient.
 - Possibly create an abstract RpcClient class to only load all the basic Rpc 
 layer configurations to be used in an implementation.
 Why? It enables experimentation with RpcClients which could enable new 
 features or could be more performant than the included client. 
 I created a new RpcClient implementation based on Netty which can also be 
 called asynchronously. It would be great to also be able to use this 
 RpcClient in all the default ways and tests to see if there are any issues 
 with it. 
 https://github.com/jurmous/async-hbase-client/
 https://github.com/jurmous/async-hbase-client/blob/master/src/main/java/org/apache/hadoop/hbase/ipc/AsyncRpcClient.java



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-12583) Allow creating reference files even the split row not lies in the storefile range if required

2014-12-09 Thread Hudson (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-12583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14239524#comment-14239524
 ] 

Hudson commented on HBASE-12583:


SUCCESS: Integrated in HBase-1.0 #556 (See 
[https://builds.apache.org/job/HBase-1.0/556/])
HBASE-12583 Allow creating reference files even the split row not lies in the 
storefile range if required(Rajeshbabu) (rajeshbabu: rev 
08a25598511998e0d7da5904c210db96b1e0ca16)
* hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/HRegion.java
* 
hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/SplitTransaction.java
* 
hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestSplitTransactionOnCluster.java
* 
hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestStoreFile.java
* 
hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/RegionSplitPolicy.java
* 
hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/HRegionFileSystem.java


 Allow creating reference files even the split row not lies in the storefile 
 range if required
 -

 Key: HBASE-12583
 URL: https://issues.apache.org/jira/browse/HBASE-12583
 Project: HBase
  Issue Type: Improvement
Reporter: rajeshbabu
Assignee: rajeshbabu
  Labels: Phoenix
 Fix For: 1.0.0, 2.0.0, 0.98.9

 Attachments: HBASE-12583.patch, HBASE-12583_98.patch, 
 HBASE-12583_98_v2.patch, HBASE-12583_branch1.patch, 
 HBASE-12583_branch1_v2.patch, HBASE-12583_v2.patch, HBASE-12583_v3.patch


 Currently in HRegionFileSystem#splitStoreFile we are not creating reference 
 files if the split row not lies in the storefile range that means one of the 
 child region doesn't have any data.
 {code}
// Check whether the split row lies in the range of the store file
 // If it is outside the range, return directly.
 if (top) {
   //check if larger than last key.
   KeyValue splitKey = KeyValueUtil.createFirstOnRow(splitRow);
   byte[] lastKey = f.createReader().getLastKey();
   // If lastKey is null means storefile is empty.
   if (lastKey == null) return null;
   if (f.getReader().getComparator().compareFlatKey(splitKey.getBuffer(),
   splitKey.getKeyOffset(), splitKey.getKeyLength(), lastKey, 0, 
 lastKey.length)  0) {
 return null;
   }
 } else {
   //check if smaller than first key
   KeyValue splitKey = KeyValueUtil.createLastOnRow(splitRow);
   byte[] firstKey = f.createReader().getFirstKey();
   // If firstKey is null means storefile is empty.
   if (firstKey == null) return null;
   if (f.getReader().getComparator().compareFlatKey(splitKey.getBuffer(),
   splitKey.getKeyOffset(), splitKey.getKeyLength(), firstKey, 0, 
 firstKey.length)  0) {
 return null;
   }
 }
 {code}
 In some cases when split row should be compared with part of rowkey(in 
 composite rowkey) mainly for secondary index tables we need to create 
 reference files even when split row not lies in the storefile range so that 
 they can be rewritten to it's child regions by some custom half store file 
 reader which compare the part of row key with split row.
 The check of comparing split row with storefile range and returning directly 
 can be avoided by having special boolean attribute in table descriptor when 
 it set to true. Or else we can have coprocessor hooks so that in the hooks we 
 can create the references and bypass.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (HBASE-12652) Allow unmanaged connections in MetaTableAccessor

2014-12-09 Thread Solomon Duskis (JIRA)

 [ 
https://issues.apache.org/jira/browse/HBASE-12652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Solomon Duskis updated HBASE-12652:
---
Attachment: HBASE-12652B.patch

Fixed the issue with TestMasterNoCluster with some additional mocking in 
HConnectionTestingUtility.

 Allow unmanaged connections in MetaTableAccessor
 

 Key: HBASE-12652
 URL: https://issues.apache.org/jira/browse/HBASE-12652
 Project: HBase
  Issue Type: Bug
Affects Versions: 1.0.0, 2.0.0
Reporter: Solomon Duskis
Assignee: Solomon Duskis
 Attachments: HBASE-12652.patch, HBASE-12652.patch, HBASE-12652B.patch


 Passing in an unmanaged connnection to MetaTableAccessor causes an exception. 
  MetaTableAccessor should be able to use both unmanaged and managed 
 connections.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (HBASE-12653) Move TestRegionServerOnlineConfigChange TestConfigurationManager to Junit4 tests

2014-12-09 Thread Ted Yu (JIRA)

 [ 
https://issues.apache.org/jira/browse/HBASE-12653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ted Yu updated HBASE-12653:
---
  Resolution: Fixed
Hadoop Flags: Reviewed
  Status: Resolved  (was: Patch Available)

Thanks for the contribution, Ashish.

 Move TestRegionServerOnlineConfigChange  TestConfigurationManager to Junit4 
 tests
 --

 Key: HBASE-12653
 URL: https://issues.apache.org/jira/browse/HBASE-12653
 Project: HBase
  Issue Type: Improvement
  Components: test
Affects Versions: 2.0.0, 0.99.2
Reporter: Ashish Singhi
Assignee: Ashish Singhi
Priority: Minor
 Fix For: 1.0.0, 2.0.0

 Attachments: HBASE-12653.patch






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-12662) region_status.rb is failing with NoMethodError

2014-12-09 Thread Ted Yu (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-12662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14239546#comment-14239546
 ] 

Ted Yu commented on HBASE-12662:


+1

 region_status.rb is failing with NoMethodError
 --

 Key: HBASE-12662
 URL: https://issues.apache.org/jira/browse/HBASE-12662
 Project: HBase
  Issue Type: Bug
  Components: shell
Affects Versions: 2.0.0
Reporter: Ashish Singhi
Assignee: Ashish Singhi
 Attachments: HBASE-12662.patch


 {noformat}
 $/hbase-2.0.0-SNAPSHOT/bin hbase org.jruby.Main region_status.rb --table t
 2014-12-09 19:33:06,839 WARN  [main] util.NativeCodeLoader: Unable to load 
 native-hadoop library for your platform... using builtin-java classes where 
 applicable
 NoMethodError: undefined method `cache_blocks=' for 
 #Java::OrgApacheHadoopHbaseClient::Scan:0x1c7abd4c
   (root) at region_status.rb:93
 {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-12583) Allow creating reference files even the split row not lies in the storefile range if required

2014-12-09 Thread Hudson (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-12583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14239560#comment-14239560
 ] 

Hudson commented on HBASE-12583:


SUCCESS: Integrated in HBase-TRUNK #5892 (See 
[https://builds.apache.org/job/HBase-TRUNK/5892/])
HBASE-12583 Allow creating reference files even the split row not lies in the 
storefile range if required(Rajeshbabu) (rajeshbabu: rev 
0354128780abc41b4a0018a3f0712330952ebd83)
* 
hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestSplitTransactionOnCluster.java
* hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/HRegion.java
* 
hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestStoreFile.java
* 
hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/RegionSplitPolicy.java
* 
hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/HRegionFileSystem.java
* 
hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/SplitTransaction.java


 Allow creating reference files even the split row not lies in the storefile 
 range if required
 -

 Key: HBASE-12583
 URL: https://issues.apache.org/jira/browse/HBASE-12583
 Project: HBase
  Issue Type: Improvement
Reporter: rajeshbabu
Assignee: rajeshbabu
  Labels: Phoenix
 Fix For: 1.0.0, 2.0.0, 0.98.9

 Attachments: HBASE-12583.patch, HBASE-12583_98.patch, 
 HBASE-12583_98_v2.patch, HBASE-12583_branch1.patch, 
 HBASE-12583_branch1_v2.patch, HBASE-12583_v2.patch, HBASE-12583_v3.patch


 Currently in HRegionFileSystem#splitStoreFile we are not creating reference 
 files if the split row not lies in the storefile range that means one of the 
 child region doesn't have any data.
 {code}
// Check whether the split row lies in the range of the store file
 // If it is outside the range, return directly.
 if (top) {
   //check if larger than last key.
   KeyValue splitKey = KeyValueUtil.createFirstOnRow(splitRow);
   byte[] lastKey = f.createReader().getLastKey();
   // If lastKey is null means storefile is empty.
   if (lastKey == null) return null;
   if (f.getReader().getComparator().compareFlatKey(splitKey.getBuffer(),
   splitKey.getKeyOffset(), splitKey.getKeyLength(), lastKey, 0, 
 lastKey.length)  0) {
 return null;
   }
 } else {
   //check if smaller than first key
   KeyValue splitKey = KeyValueUtil.createLastOnRow(splitRow);
   byte[] firstKey = f.createReader().getFirstKey();
   // If firstKey is null means storefile is empty.
   if (firstKey == null) return null;
   if (f.getReader().getComparator().compareFlatKey(splitKey.getBuffer(),
   splitKey.getKeyOffset(), splitKey.getKeyLength(), firstKey, 0, 
 firstKey.length)  0) {
 return null;
   }
 }
 {code}
 In some cases when split row should be compared with part of rowkey(in 
 composite rowkey) mainly for secondary index tables we need to create 
 reference files even when split row not lies in the storefile range so that 
 they can be rewritten to it's child regions by some custom half store file 
 reader which compare the part of row key with split row.
 The check of comparing split row with storefile range and returning directly 
 can be avoided by having special boolean attribute in table descriptor when 
 it set to true. Or else we can have coprocessor hooks so that in the hooks we 
 can create the references and bypass.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (HBASE-12655) WALPerformanceEvaluation miscalculates append/sync statistics for multiple regions

2014-12-09 Thread Sean Busbey (JIRA)

 [ 
https://issues.apache.org/jira/browse/HBASE-12655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sean Busbey updated HBASE-12655:

Resolution: Fixed
Status: Resolved  (was: Patch Available)

pushed to branch-1+.

 WALPerformanceEvaluation miscalculates append/sync statistics for multiple 
 regions
 --

 Key: HBASE-12655
 URL: https://issues.apache.org/jira/browse/HBASE-12655
 Project: HBase
  Issue Type: Bug
  Components: wal
Affects Versions: 0.99.2
Reporter: Sean Busbey
Assignee: Sean Busbey
Priority: Minor
 Fix For: 1.0.0, 2.0.0

 Attachments: HBASE-12655.1.patch.txt


 Right now the WALPerformaceEvaluation tool sets up each new region by asking 
 for a WAL and then adding a listener. The listener updates running stats on 
 appends / syncs using a shared object in the evaluation tool.
 For WALProviders that reuse WALs (such as the default one always using a 
 single WAL), this results in adding a listener to WALs that already have 
 them. Each of those listeners is then updated on each append/sync.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (HBASE-12661) rat check fails for several files

2014-12-09 Thread Sean Busbey (JIRA)

 [ 
https://issues.apache.org/jira/browse/HBASE-12661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sean Busbey updated HBASE-12661:

Resolution: Fixed
Status: Resolved  (was: Patch Available)

pushed to branch-1+.

 rat check fails for several files
 -

 Key: HBASE-12661
 URL: https://issues.apache.org/jira/browse/HBASE-12661
 Project: HBase
  Issue Type: Bug
Affects Versions: 1.0.0, 2.0.0
Reporter: Sean Busbey
Assignee: Sean Busbey
Priority: Blocker
 Fix For: 1.0.0, 2.0.0

 Attachments: HBASE-12661.1.patch.txt, HBASE-12661.2.patch.txt


 newly added files missing a license header:
 * MetricsReplicationSinkSource
 * MetricsReplicationSourceFactoryImpl
 * MetricsReplicationSourceSourceImpl
 * TestMetricsReplicationSourceFactoryImpl



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (HBASE-12630) Provide capability for dropping malfunctioning ConfigurationObserver automatically

2014-12-09 Thread Ashish Singhi (JIRA)

 [ 
https://issues.apache.org/jira/browse/HBASE-12630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ashish Singhi updated HBASE-12630:
--
Status: Open  (was: Patch Available)

 Provide capability for dropping malfunctioning ConfigurationObserver 
 automatically
 --

 Key: HBASE-12630
 URL: https://issues.apache.org/jira/browse/HBASE-12630
 Project: HBase
  Issue Type: Improvement
Reporter: Ted Yu
Assignee: Ashish Singhi
 Fix For: 1.0.0, 2.0.0

 Attachments: HBASE-12630.patch


 Chatting with Manukranth, online config update feature should handle the case 
 where certain ConfigurationObserver(s) constantly produce exception when 
 notified of config update.
 We can handle such ConfigurationObserver by sidelining it after configurable 
 number of exceptions seen from the ConfigurationObserver.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (HBASE-12630) Provide capability for dropping malfunctioning ConfigurationObserver automatically

2014-12-09 Thread Ashish Singhi (JIRA)

 [ 
https://issues.apache.org/jira/browse/HBASE-12630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ashish Singhi updated HBASE-12630:
--
Attachment: HBASE-12630-v2.patch

 Provide capability for dropping malfunctioning ConfigurationObserver 
 automatically
 --

 Key: HBASE-12630
 URL: https://issues.apache.org/jira/browse/HBASE-12630
 Project: HBase
  Issue Type: Improvement
Reporter: Ted Yu
Assignee: Ashish Singhi
 Fix For: 1.0.0, 2.0.0

 Attachments: HBASE-12630-v2.patch, HBASE-12630.patch


 Chatting with Manukranth, online config update feature should handle the case 
 where certain ConfigurationObserver(s) constantly produce exception when 
 notified of config update.
 We can handle such ConfigurationObserver by sidelining it after configurable 
 number of exceptions seen from the ConfigurationObserver.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (HBASE-12630) Provide capability for dropping malfunctioning ConfigurationObserver automatically

2014-12-09 Thread Ashish Singhi (JIRA)

 [ 
https://issues.apache.org/jira/browse/HBASE-12630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ashish Singhi updated HBASE-12630:
--
Status: Patch Available  (was: Open)

 Provide capability for dropping malfunctioning ConfigurationObserver 
 automatically
 --

 Key: HBASE-12630
 URL: https://issues.apache.org/jira/browse/HBASE-12630
 Project: HBase
  Issue Type: Improvement
Reporter: Ted Yu
Assignee: Ashish Singhi
 Fix For: 1.0.0, 2.0.0

 Attachments: HBASE-12630-v2.patch, HBASE-12630.patch


 Chatting with Manukranth, online config update feature should handle the case 
 where certain ConfigurationObserver(s) constantly produce exception when 
 notified of config update.
 We can handle such ConfigurationObserver by sidelining it after configurable 
 number of exceptions seen from the ConfigurationObserver.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (HBASE-12630) Provide capability for dropping malfunctioning ConfigurationObserver automatically

2014-12-09 Thread Ashish Singhi (JIRA)

 [ 
https://issues.apache.org/jira/browse/HBASE-12630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ashish Singhi updated HBASE-12630:
--
Status: Open  (was: Patch Available)

 Provide capability for dropping malfunctioning ConfigurationObserver 
 automatically
 --

 Key: HBASE-12630
 URL: https://issues.apache.org/jira/browse/HBASE-12630
 Project: HBase
  Issue Type: Improvement
Reporter: Ted Yu
Assignee: Ashish Singhi
 Fix For: 1.0.0, 2.0.0

 Attachments: HBASE-12630-v2.patch, HBASE-12630.patch


 Chatting with Manukranth, online config update feature should handle the case 
 where certain ConfigurationObserver(s) constantly produce exception when 
 notified of config update.
 We can handle such ConfigurationObserver by sidelining it after configurable 
 number of exceptions seen from the ConfigurationObserver.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-12583) Allow creating reference files even the split row not lies in the storefile range if required

2014-12-09 Thread Hudson (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-12583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14239583#comment-14239583
 ] 

Hudson commented on HBASE-12583:


FAILURE: Integrated in HBase-0.98 #728 (See 
[https://builds.apache.org/job/HBase-0.98/728/])
HBASE-12583 Allow creating reference files even the split row not lies in the 
storefile range if required(Rajeshbabu) (rajeshbabu: rev 
0e3d4cd71bd1de622a00ab05bb047a97d9e15b7e)
* hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/HRegion.java
* 
hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestSplitTransactionOnCluster.java
* 
hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/HRegionFileSystem.java
* 
hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestStoreFile.java
* 
hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/RegionSplitPolicy.java
* 
hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/SplitTransaction.java


 Allow creating reference files even the split row not lies in the storefile 
 range if required
 -

 Key: HBASE-12583
 URL: https://issues.apache.org/jira/browse/HBASE-12583
 Project: HBase
  Issue Type: Improvement
Reporter: rajeshbabu
Assignee: rajeshbabu
  Labels: Phoenix
 Fix For: 1.0.0, 2.0.0, 0.98.9

 Attachments: HBASE-12583.patch, HBASE-12583_98.patch, 
 HBASE-12583_98_v2.patch, HBASE-12583_branch1.patch, 
 HBASE-12583_branch1_v2.patch, HBASE-12583_v2.patch, HBASE-12583_v3.patch


 Currently in HRegionFileSystem#splitStoreFile we are not creating reference 
 files if the split row not lies in the storefile range that means one of the 
 child region doesn't have any data.
 {code}
// Check whether the split row lies in the range of the store file
 // If it is outside the range, return directly.
 if (top) {
   //check if larger than last key.
   KeyValue splitKey = KeyValueUtil.createFirstOnRow(splitRow);
   byte[] lastKey = f.createReader().getLastKey();
   // If lastKey is null means storefile is empty.
   if (lastKey == null) return null;
   if (f.getReader().getComparator().compareFlatKey(splitKey.getBuffer(),
   splitKey.getKeyOffset(), splitKey.getKeyLength(), lastKey, 0, 
 lastKey.length)  0) {
 return null;
   }
 } else {
   //check if smaller than first key
   KeyValue splitKey = KeyValueUtil.createLastOnRow(splitRow);
   byte[] firstKey = f.createReader().getFirstKey();
   // If firstKey is null means storefile is empty.
   if (firstKey == null) return null;
   if (f.getReader().getComparator().compareFlatKey(splitKey.getBuffer(),
   splitKey.getKeyOffset(), splitKey.getKeyLength(), firstKey, 0, 
 firstKey.length)  0) {
 return null;
   }
 }
 {code}
 In some cases when split row should be compared with part of rowkey(in 
 composite rowkey) mainly for secondary index tables we need to create 
 reference files even when split row not lies in the storefile range so that 
 they can be rewritten to it's child regions by some custom half store file 
 reader which compare the part of row key with split row.
 The check of comparing split row with storefile range and returning directly 
 can be avoided by having special boolean attribute in table descriptor when 
 it set to true. Or else we can have coprocessor hooks so that in the hooks we 
 can create the references and bypass.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-10201) Port 'Make flush decisions per column family' to trunk

2014-12-09 Thread stack (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-10201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14239588#comment-14239588
 ] 

stack commented on HBASE-10201:
---

bq. I followed RegionSplitPolicy to write FlushPolicy

I see. Yes you did it seems.

bq. ...Ted Yu suggested using FlushPolicyFactory and placing the factory method 
in it instead of FlushPolicy. 

OK. Its his fault then.

bq. Maybe the code of RegionSplitPolicy is old and need refactoring too...

My comments above apply to it too it seems yes.  The master is checking it can 
load the split policy reaching across into the regionserver package. I suppose 
the idea is checking split policy in one central place.  Should just load 
default on regionserver if we can't find the configured one.

bq. ReflectionUtils.newInstance(clazz, conf) will call setConf. 

ok

bq. Can be fixed later.

ok

Yeah, looks like you followed pattern in code base so not a problem of your 
making. Can fix both in a followup issue.

bq. flushSeqId will not be bumped if we do not flush all stores.

Because?

bq. And actually I do not know where we use FlushMarker so I do not know the 
meaning of flushSeqId in the Marker...

It may not be used just yet but it will be used soon by following read replicas.

 Port 'Make flush decisions per column family' to trunk
 --

 Key: HBASE-10201
 URL: https://issues.apache.org/jira/browse/HBASE-10201
 Project: HBase
  Issue Type: Improvement
  Components: wal
Reporter: Ted Yu
Assignee: zhangduo
Priority: Critical
 Fix For: 1.0.0, 2.0.0, 0.98.9

 Attachments: 3149-trunk-v1.txt, HBASE-10201-0.98.patch, 
 HBASE-10201-0.98_1.patch, HBASE-10201-0.98_2.patch, HBASE-10201-0.99.patch, 
 HBASE-10201.patch, HBASE-10201_1.patch, HBASE-10201_10.patch, 
 HBASE-10201_11.patch, HBASE-10201_12.patch, HBASE-10201_13.patch, 
 HBASE-10201_13.patch, HBASE-10201_14.patch, HBASE-10201_15.patch, 
 HBASE-10201_16.patch, HBASE-10201_17.patch, HBASE-10201_2.patch, 
 HBASE-10201_3.patch, HBASE-10201_4.patch, HBASE-10201_5.patch, 
 HBASE-10201_6.patch, HBASE-10201_7.patch, HBASE-10201_8.patch, 
 HBASE-10201_9.patch, compactions.png, count.png, io.png, memstore.png


 Currently the flush decision is made using the aggregate size of all column 
 families. When large and small column families co-exist, this causes many 
 small flushes of the smaller CF. We need to make per-CF flush decisions.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-12662) region_status.rb is failing with NoMethodError

2014-12-09 Thread Hadoop QA (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-12662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14239593#comment-14239593
 ] 

Hadoop QA commented on HBASE-12662:
---

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12686013/HBASE-12662.patch
  against master branch at commit 0354128780abc41b4a0018a3f0712330952ebd83.
  ATTACHMENT ID: 12686013

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:red}-1 tests included{color}.  The patch doesn't appear to include 
any new or modified tests.
Please justify why no new tests are needed for this 
patch.
Also please list what manual steps were performed to 
verify this patch.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:red}-1 javadoc{color}.  The javadoc tool appears to have generated 1 
warning messages.

{color:green}+1 checkstyle{color}.  The applied patch does not increase the 
total number of checkstyle errors

{color:green}+1 findbugs{color}.  The patch does not introduce any new 
Findbugs (version 2.0.3) warnings.

{color:red}-1 release audit{color}.  The applied patch generated 1 release 
audit warnings (more than the master's current 0 warnings).

{color:green}+1 lineLengths{color}.  The patch does not introduce lines 
longer than 100

  {color:green}+1 site{color}.  The mvn site goal succeeds with this patch.

{color:green}+1 core tests{color}.  The patch passed unit tests in .

Test results: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12016//testReport/
Release audit warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12016//artifact/patchprocess/patchReleaseAuditWarnings.txt
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12016//artifact/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12016//artifact/patchprocess/newPatchFindbugsWarningshbase-annotations.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12016//artifact/patchprocess/newPatchFindbugsWarningshbase-thrift.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12016//artifact/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12016//artifact/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12016//artifact/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12016//artifact/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12016//artifact/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12016//artifact/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12016//artifact/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12016//artifact/patchprocess/newPatchFindbugsWarningshbase-rest.html
Checkstyle Errors: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12016//artifact/patchprocess/checkstyle-aggregate.html

  Javadoc warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12016//artifact/patchprocess/patchJavadocWarnings.txt
Console output: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12016//console

This message is automatically generated.

 region_status.rb is failing with NoMethodError
 --

 Key: HBASE-12662
 URL: https://issues.apache.org/jira/browse/HBASE-12662
 Project: HBase
  Issue Type: Bug
  Components: shell
Affects Versions: 2.0.0
Reporter: Ashish Singhi
Assignee: Ashish Singhi
 Attachments: HBASE-12662.patch


 {noformat}
 $/hbase-2.0.0-SNAPSHOT/bin hbase org.jruby.Main region_status.rb --table t
 2014-12-09 19:33:06,839 WARN  [main] util.NativeCodeLoader: Unable to load 
 native-hadoop library for your platform... using builtin-java classes where 
 applicable
 NoMethodError: undefined method `cache_blocks=' for 
 #Java::OrgApacheHadoopHbaseClient::Scan:0x1c7abd4c
   (root) at region_status.rb:93
 {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-12645) HBaseTestingUtility is using ${$HOME} for rootDir

2014-12-09 Thread stack (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-12645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14239598#comment-14239598
 ] 

stack commented on HBASE-12645:
---

See comments above. I think its difference between local and hdfs fs.  Could do 
as [~enis] suggests?  We want all tests using UUID test dir if possible.

 HBaseTestingUtility is using ${$HOME} for rootDir
 -

 Key: HBASE-12645
 URL: https://issues.apache.org/jira/browse/HBASE-12645
 Project: HBase
  Issue Type: Test
  Components: test
Affects Versions: 1.0.0
Reporter: Nick Dimiduk
Assignee: Varun Saxena
Priority: Critical
 Fix For: 1.0.0, 2.0.0

 Attachments: HBASE-12645.002.patch, HBASE-12645.patch


 I noticed this while running tests on branch-1
 {noformat}
 Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.009 sec  
 FAILURE! - in 
 org.apache.hadoop.hbase.regionserver.wal.TestReadOldRootAndMetaEdits
 org.apache.hadoop.hbase.regionserver.wal.TestReadOldRootAndMetaEdits  Time 
 elapsed: 0.009 sec   ERROR!
 java.io.FileNotFoundException: Destination exists and is not a directory: 
 /homes/hortonnd/hbase
 at 
 org.apache.hadoop.fs.RawLocalFileSystem.mkdirs(RawLocalFileSystem.java:423)
 at 
 org.apache.hadoop.fs.ChecksumFileSystem.mkdirs(ChecksumFileSystem.java:588)
 at 
 org.apache.hadoop.hbase.HBaseTestingUtility.createRootDir(HBaseTestingUtility.java:1053)
 at 
 org.apache.hadoop.hbase.regionserver.wal.TestReadOldRootAndMetaEdits.setupBeforeClass(TestReadOldRootAndMetaEdits.java:70)
 {noformat}
 Either the testing utility has a regression or there's a config regression in 
 this test.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-12661) rat check fails for several files

2014-12-09 Thread Hadoop QA (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-12661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14239611#comment-14239611
 ] 

Hadoop QA commented on HBASE-12661:
---

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  
http://issues.apache.org/jira/secure/attachment/12686017/HBASE-12661.2.patch.txt
  against master branch at commit 0354128780abc41b4a0018a3f0712330952ebd83.
  ATTACHMENT ID: 12686017

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:green}+1 tests included{color}.  The patch appears to include 4 new 
or modified tests.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:red}-1 javadoc{color}.  The javadoc tool appears to have generated 1 
warning messages.

{color:green}+1 checkstyle{color}.  The applied patch does not increase the 
total number of checkstyle errors

{color:green}+1 findbugs{color}.  The patch does not introduce any new 
Findbugs (version 2.0.3) warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:green}+1 lineLengths{color}.  The patch does not introduce lines 
longer than 100

  {color:green}+1 site{color}.  The mvn site goal succeeds with this patch.

{color:green}+1 core tests{color}.  The patch passed unit tests in .

Test results: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12017//testReport/
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12017//artifact/patchprocess/newPatchFindbugsWarningshbase-rest.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12017//artifact/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12017//artifact/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12017//artifact/patchprocess/newPatchFindbugsWarningshbase-annotations.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12017//artifact/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12017//artifact/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12017//artifact/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12017//artifact/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12017//artifact/patchprocess/newPatchFindbugsWarningshbase-thrift.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12017//artifact/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12017//artifact/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html
Checkstyle Errors: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12017//artifact/patchprocess/checkstyle-aggregate.html

  Javadoc warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12017//artifact/patchprocess/patchJavadocWarnings.txt
Console output: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12017//console

This message is automatically generated.

 rat check fails for several files
 -

 Key: HBASE-12661
 URL: https://issues.apache.org/jira/browse/HBASE-12661
 Project: HBase
  Issue Type: Bug
Affects Versions: 1.0.0, 2.0.0
Reporter: Sean Busbey
Assignee: Sean Busbey
Priority: Blocker
 Fix For: 1.0.0, 2.0.0

 Attachments: HBASE-12661.1.patch.txt, HBASE-12661.2.patch.txt


 newly added files missing a license header:
 * MetricsReplicationSinkSource
 * MetricsReplicationSourceFactoryImpl
 * MetricsReplicationSourceSourceImpl
 * TestMetricsReplicationSourceFactoryImpl



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-12653) Move TestRegionServerOnlineConfigChange TestConfigurationManager to Junit4 tests

2014-12-09 Thread Hudson (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-12653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14239640#comment-14239640
 ] 

Hudson commented on HBASE-12653:


FAILURE: Integrated in HBase-1.0 #557 (See 
[https://builds.apache.org/job/HBase-1.0/557/])
HBASE-12653 Move TestRegionServerOnlineConfigChange  TestConfigurationManager 
to Junit4 tests (Ashish) (tedyu: rev 553c386c8c89ca0be0ca55d65aa22fdb5ff3302b)
* 
hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestRegionServerOnlineConfigChange.java
* 
hbase-server/src/test/java/org/apache/hadoop/hbase/conf/TestConfigurationManager.java


 Move TestRegionServerOnlineConfigChange  TestConfigurationManager to Junit4 
 tests
 --

 Key: HBASE-12653
 URL: https://issues.apache.org/jira/browse/HBASE-12653
 Project: HBase
  Issue Type: Improvement
  Components: test
Affects Versions: 2.0.0, 0.99.2
Reporter: Ashish Singhi
Assignee: Ashish Singhi
Priority: Minor
 Fix For: 1.0.0, 2.0.0

 Attachments: HBASE-12653.patch






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-12583) Allow creating reference files even the split row not lies in the storefile range if required

2014-12-09 Thread rajeshbabu (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-12583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14239655#comment-14239655
 ] 

rajeshbabu commented on HBASE-12583:


[~anoop.hbase]
I will update the javadoc and commit. Thanks

 Allow creating reference files even the split row not lies in the storefile 
 range if required
 -

 Key: HBASE-12583
 URL: https://issues.apache.org/jira/browse/HBASE-12583
 Project: HBase
  Issue Type: Improvement
Reporter: rajeshbabu
Assignee: rajeshbabu
  Labels: Phoenix
 Fix For: 1.0.0, 2.0.0, 0.98.9

 Attachments: HBASE-12583.patch, HBASE-12583_98.patch, 
 HBASE-12583_98_v2.patch, HBASE-12583_branch1.patch, 
 HBASE-12583_branch1_v2.patch, HBASE-12583_v2.patch, HBASE-12583_v3.patch


 Currently in HRegionFileSystem#splitStoreFile we are not creating reference 
 files if the split row not lies in the storefile range that means one of the 
 child region doesn't have any data.
 {code}
// Check whether the split row lies in the range of the store file
 // If it is outside the range, return directly.
 if (top) {
   //check if larger than last key.
   KeyValue splitKey = KeyValueUtil.createFirstOnRow(splitRow);
   byte[] lastKey = f.createReader().getLastKey();
   // If lastKey is null means storefile is empty.
   if (lastKey == null) return null;
   if (f.getReader().getComparator().compareFlatKey(splitKey.getBuffer(),
   splitKey.getKeyOffset(), splitKey.getKeyLength(), lastKey, 0, 
 lastKey.length)  0) {
 return null;
   }
 } else {
   //check if smaller than first key
   KeyValue splitKey = KeyValueUtil.createLastOnRow(splitRow);
   byte[] firstKey = f.createReader().getFirstKey();
   // If firstKey is null means storefile is empty.
   if (firstKey == null) return null;
   if (f.getReader().getComparator().compareFlatKey(splitKey.getBuffer(),
   splitKey.getKeyOffset(), splitKey.getKeyLength(), firstKey, 0, 
 firstKey.length)  0) {
 return null;
   }
 }
 {code}
 In some cases when split row should be compared with part of rowkey(in 
 composite rowkey) mainly for secondary index tables we need to create 
 reference files even when split row not lies in the storefile range so that 
 they can be rewritten to it's child regions by some custom half store file 
 reader which compare the part of row key with split row.
 The check of comparing split row with storefile range and returning directly 
 can be avoided by having special boolean attribute in table descriptor when 
 it set to true. Or else we can have coprocessor hooks so that in the hooks we 
 can create the references and bypass.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Created] (HBASE-12663) unify getTableDescriptors() and listTableDescriptorsByNamespace()

2014-12-09 Thread Matteo Bertozzi (JIRA)
Matteo Bertozzi created HBASE-12663:
---

 Summary: unify getTableDescriptors() and 
listTableDescriptorsByNamespace()
 Key: HBASE-12663
 URL: https://issues.apache.org/jira/browse/HBASE-12663
 Project: HBase
  Issue Type: Bug
  Components: master, security
Affects Versions: 1.0.0, 2.0.0
Reporter: Matteo Bertozzi






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-10201) Port 'Make flush decisions per column family' to trunk

2014-12-09 Thread Ted Yu (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-10201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14239658#comment-14239658
 ] 

Ted Yu commented on HBASE-10201:


w.r.t. FlushPolicyFactory, I made the comment before 
sanityCheckTableDescriptor() was added.

It was not my intention that master directly references class in region server 
module.

 Port 'Make flush decisions per column family' to trunk
 --

 Key: HBASE-10201
 URL: https://issues.apache.org/jira/browse/HBASE-10201
 Project: HBase
  Issue Type: Improvement
  Components: wal
Reporter: Ted Yu
Assignee: zhangduo
Priority: Critical
 Fix For: 1.0.0, 2.0.0, 0.98.9

 Attachments: 3149-trunk-v1.txt, HBASE-10201-0.98.patch, 
 HBASE-10201-0.98_1.patch, HBASE-10201-0.98_2.patch, HBASE-10201-0.99.patch, 
 HBASE-10201.patch, HBASE-10201_1.patch, HBASE-10201_10.patch, 
 HBASE-10201_11.patch, HBASE-10201_12.patch, HBASE-10201_13.patch, 
 HBASE-10201_13.patch, HBASE-10201_14.patch, HBASE-10201_15.patch, 
 HBASE-10201_16.patch, HBASE-10201_17.patch, HBASE-10201_2.patch, 
 HBASE-10201_3.patch, HBASE-10201_4.patch, HBASE-10201_5.patch, 
 HBASE-10201_6.patch, HBASE-10201_7.patch, HBASE-10201_8.patch, 
 HBASE-10201_9.patch, compactions.png, count.png, io.png, memstore.png


 Currently the flush decision is made using the aggregate size of all column 
 families. When large and small column families co-exist, this causes many 
 small flushes of the smaller CF. We need to make per-CF flush decisions.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (HBASE-12663) unify getTableDescriptors() and listTableDescriptorsByNamespace()

2014-12-09 Thread Matteo Bertozzi (JIRA)

 [ 
https://issues.apache.org/jira/browse/HBASE-12663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Matteo Bertozzi updated HBASE-12663:

Attachment: HBASE-12663-v0.patch

 unify getTableDescriptors() and listTableDescriptorsByNamespace()
 -

 Key: HBASE-12663
 URL: https://issues.apache.org/jira/browse/HBASE-12663
 Project: HBase
  Issue Type: Bug
  Components: master, security
Affects Versions: 1.0.0, 2.0.0
Reporter: Matteo Bertozzi
 Attachments: HBASE-12663-v0.patch


 currently we have getTableDescriptors()/listTableNames()
 and listTableDescriptorsByNamespace()/listTableNamesByNamespace()
 which are just filtering by namespace.
 The first two are already able to filter tables by regex,
 and there is also an ACL check which shows only the table the user have 
 access to,
 while the namespace version just return a list without any ACLs check.
 to me there is no point to keep the *ByNamespace() version on the server 
 side, 
 since the base version must be able to do the filtering by
 namespace and the ACLs check must be the same for both anyway.
 or at least we can just call the base version with the ns filtering.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (HBASE-12663) unify getTableDescriptors() and listTableDescriptorsByNamespace()

2014-12-09 Thread Matteo Bertozzi (JIRA)

 [ 
https://issues.apache.org/jira/browse/HBASE-12663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Matteo Bertozzi updated HBASE-12663:

Description: 
currently we have getTableDescriptors()/listTableNames()
and listTableDescriptorsByNamespace()/listTableNamesByNamespace()
which are just filtering by namespace.

The first two are already able to filter tables by regex,
and there is also an ACL check which shows only the table the user have access 
to,
while the namespace version just return a list without any ACLs check.

to me there is no point to keep the *ByNamespace() version on the server side, 
since the base version must be able to do the filtering by
namespace and the ACLs check must be the same for both anyway.
or at least we can just call the base version with the ns filtering.


 unify getTableDescriptors() and listTableDescriptorsByNamespace()
 -

 Key: HBASE-12663
 URL: https://issues.apache.org/jira/browse/HBASE-12663
 Project: HBase
  Issue Type: Bug
  Components: master, security
Affects Versions: 1.0.0, 2.0.0
Reporter: Matteo Bertozzi
 Attachments: HBASE-12663-v0.patch


 currently we have getTableDescriptors()/listTableNames()
 and listTableDescriptorsByNamespace()/listTableNamesByNamespace()
 which are just filtering by namespace.
 The first two are already able to filter tables by regex,
 and there is also an ACL check which shows only the table the user have 
 access to,
 while the namespace version just return a list without any ACLs check.
 to me there is no point to keep the *ByNamespace() version on the server 
 side, 
 since the base version must be able to do the filtering by
 namespace and the ACLs check must be the same for both anyway.
 or at least we can just call the base version with the ns filtering.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Assigned] (HBASE-12663) unify getTableDescriptors() and listTableDescriptorsByNamespace()

2014-12-09 Thread Matteo Bertozzi (JIRA)

 [ 
https://issues.apache.org/jira/browse/HBASE-12663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Matteo Bertozzi reassigned HBASE-12663:
---

Assignee: Matteo Bertozzi

 unify getTableDescriptors() and listTableDescriptorsByNamespace()
 -

 Key: HBASE-12663
 URL: https://issues.apache.org/jira/browse/HBASE-12663
 Project: HBase
  Issue Type: Bug
  Components: master, security
Affects Versions: 1.0.0, 2.0.0
Reporter: Matteo Bertozzi
Assignee: Matteo Bertozzi
 Attachments: HBASE-12663-v0.patch


 currently we have getTableDescriptors()/listTableNames()
 and listTableDescriptorsByNamespace()/listTableNamesByNamespace()
 which are just filtering by namespace.
 The first two are already able to filter tables by regex,
 and there is also an ACL check which shows only the table the user have 
 access to,
 while the namespace version just return a list without any ACLs check.
 to me there is no point to keep the *ByNamespace() version on the server 
 side, 
 since the base version must be able to do the filtering by
 namespace and the ACLs check must be the same for both anyway.
 or at least we can just call the base version with the ns filtering.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (HBASE-12663) unify getTableDescriptors() and listTableDescriptorsByNamespace()

2014-12-09 Thread Matteo Bertozzi (JIRA)

 [ 
https://issues.apache.org/jira/browse/HBASE-12663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Matteo Bertozzi updated HBASE-12663:

Status: Patch Available  (was: Open)

 unify getTableDescriptors() and listTableDescriptorsByNamespace()
 -

 Key: HBASE-12663
 URL: https://issues.apache.org/jira/browse/HBASE-12663
 Project: HBase
  Issue Type: Bug
  Components: master, security
Affects Versions: 1.0.0, 2.0.0
Reporter: Matteo Bertozzi
Assignee: Matteo Bertozzi
 Attachments: HBASE-12663-v0.patch


 currently we have getTableDescriptors()/listTableNames()
 and listTableDescriptorsByNamespace()/listTableNamesByNamespace()
 which are just filtering by namespace.
 The first two are already able to filter tables by regex,
 and there is also an ACL check which shows only the table the user have 
 access to,
 while the namespace version just return a list without any ACLs check.
 to me there is no point to keep the *ByNamespace() version on the server 
 side, 
 since the base version must be able to do the filtering by
 namespace and the ACLs check must be the same for both anyway.
 or at least we can just call the base version with the ns filtering.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-11979) Compaction progress reporting is wrong

2014-12-09 Thread Andrew Purtell (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-11979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14239661#comment-14239661
 ] 

Andrew Purtell commented on HBASE-11979:


+1, ok

I will commit this to 0.98+ shortly unless objection.

Thanks for looking at this [~esteban]! 

 Compaction progress reporting is wrong
 --

 Key: HBASE-11979
 URL: https://issues.apache.org/jira/browse/HBASE-11979
 Project: HBase
  Issue Type: Bug
Reporter: Andrew Purtell
Assignee: Esteban Gutierrez
Priority: Minor
 Fix For: 1.0.0, 2.0.0, 0.98.9

 Attachments: HBASE-11979.v0.patch


 This is a long standing problem and previously could be observed in 
 regionserver metrics, but, we recently added logging for long running 
 compactions, and this has exposed the issue in a new way, e.g.
 {noformat}
 2014-09-15 14:20:59,450 DEBUG 
 [regionserver8120-largeCompactions-1410813534627]
 compactions.Compactor: Compaction progress: 22683625/6808179 (333.18%), 
 rate=162.08 kB/sec
 {noformat}
 The 'rate' reported in such logging is consistent and what we were really 
 after, but the progress indication is clearly broken and should be fixed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-12652) Allow unmanaged connections in MetaTableAccessor

2014-12-09 Thread Hadoop QA (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-12652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14239666#comment-14239666
 ] 

Hadoop QA commented on HBASE-12652:
---

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12686023/HBASE-12652B.patch
  against master branch at commit 0354128780abc41b4a0018a3f0712330952ebd83.
  ATTACHMENT ID: 12686023

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:green}+1 tests included{color}.  The patch appears to include 15 new 
or modified tests.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:red}-1 javadoc{color}.  The javadoc tool appears to have generated 2 
warning messages.

{color:red}-1 checkstyle{color}.  The applied patch generated 
2095 checkstyle errors (more than the master's current 2093 errors).

{color:green}+1 findbugs{color}.  The patch does not introduce any new 
Findbugs (version 2.0.3) warnings.

{color:red}-1 release audit{color}.  The applied patch generated 1 release 
audit warnings (more than the master's current 0 warnings).

{color:green}+1 lineLengths{color}.  The patch does not introduce lines 
longer than 100

  {color:green}+1 site{color}.  The mvn site goal succeeds with this patch.

{color:green}+1 core tests{color}.  The patch passed unit tests in .

Test results: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12018//testReport/
Release audit warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12018//artifact/patchprocess/patchReleaseAuditWarnings.txt
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12018//artifact/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12018//artifact/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12018//artifact/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12018//artifact/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12018//artifact/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12018//artifact/patchprocess/newPatchFindbugsWarningshbase-rest.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12018//artifact/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12018//artifact/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12018//artifact/patchprocess/newPatchFindbugsWarningshbase-thrift.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12018//artifact/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12018//artifact/patchprocess/newPatchFindbugsWarningshbase-annotations.html
Checkstyle Errors: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12018//artifact/patchprocess/checkstyle-aggregate.html

Javadoc warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12018//artifact/patchprocess/patchJavadocWarnings.txt
Console output: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12018//console

This message is automatically generated.

 Allow unmanaged connections in MetaTableAccessor
 

 Key: HBASE-12652
 URL: https://issues.apache.org/jira/browse/HBASE-12652
 Project: HBase
  Issue Type: Bug
Affects Versions: 1.0.0, 2.0.0
Reporter: Solomon Duskis
Assignee: Solomon Duskis
 Attachments: HBASE-12652.patch, HBASE-12652.patch, HBASE-12652B.patch


 Passing in an unmanaged connnection to MetaTableAccessor causes an exception. 
  MetaTableAccessor should be able to use both unmanaged and managed 
 connections.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (HBASE-12630) Provide capability for dropping malfunctioning ConfigurationObserver automatically

2014-12-09 Thread Ashish Singhi (JIRA)

 [ 
https://issues.apache.org/jira/browse/HBASE-12630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ashish Singhi updated HBASE-12630:
--
Attachment: HBASE-12630-v3.patch

 Provide capability for dropping malfunctioning ConfigurationObserver 
 automatically
 --

 Key: HBASE-12630
 URL: https://issues.apache.org/jira/browse/HBASE-12630
 Project: HBase
  Issue Type: Improvement
Reporter: Ted Yu
Assignee: Ashish Singhi
 Fix For: 1.0.0, 2.0.0

 Attachments: HBASE-12630-v2.patch, HBASE-12630-v3.patch, 
 HBASE-12630.patch


 Chatting with Manukranth, online config update feature should handle the case 
 where certain ConfigurationObserver(s) constantly produce exception when 
 notified of config update.
 We can handle such ConfigurationObserver by sidelining it after configurable 
 number of exceptions seen from the ConfigurationObserver.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-12661) rat check fails for several files

2014-12-09 Thread Hudson (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-12661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14239669#comment-14239669
 ] 

Hudson commented on HBASE-12661:


FAILURE: Integrated in HBase-TRUNK #5893 (See 
[https://builds.apache.org/job/HBase-TRUNK/5893/])
HBASE-12661 add missing licenses. (busbey: rev 
a6093139ebceec76ef5092486221f872983419e6)
* 
hbase-hadoop2-compat/src/main/java/org/apache/hadoop/hbase/replication/regionserver/MetricsReplicationSourceFactoryImpl.java
* 
hbase-hadoop2-compat/src/test/java/org/apache/hadoop/hbase/replication/regionserver/TestMetricsReplicationSourceFactoryImpl.java
* 
hbase-hadoop2-compat/src/main/java/org/apache/hadoop/hbase/replication/regionserver/MetricsReplicationSourceSourceImpl.java
* 
hbase-hadoop-compat/src/main/java/org/apache/hadoop/hbase/replication/regionserver/MetricsReplicationSinkSource.java


 rat check fails for several files
 -

 Key: HBASE-12661
 URL: https://issues.apache.org/jira/browse/HBASE-12661
 Project: HBase
  Issue Type: Bug
Affects Versions: 1.0.0, 2.0.0
Reporter: Sean Busbey
Assignee: Sean Busbey
Priority: Blocker
 Fix For: 1.0.0, 2.0.0

 Attachments: HBASE-12661.1.patch.txt, HBASE-12661.2.patch.txt


 newly added files missing a license header:
 * MetricsReplicationSinkSource
 * MetricsReplicationSourceFactoryImpl
 * MetricsReplicationSourceSourceImpl
 * TestMetricsReplicationSourceFactoryImpl



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-12655) WALPerformanceEvaluation miscalculates append/sync statistics for multiple regions

2014-12-09 Thread Hudson (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-12655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14239670#comment-14239670
 ] 

Hudson commented on HBASE-12655:


FAILURE: Integrated in HBase-TRUNK #5893 (See 
[https://builds.apache.org/job/HBase-TRUNK/5893/])
HBASE-12655 WALPerformanceEvaluation should only add stat gathering listener 
once per WAL. (busbey: rev 33d79bb5eca16edc61a81c87676f866613c06ce8)
* 
hbase-server/src/test/java/org/apache/hadoop/hbase/wal/TestDefaultWALProvider.java
* 
hbase-server/src/test/java/org/apache/hadoop/hbase/wal/WALPerformanceEvaluation.java
* hbase-server/src/main/java/org/apache/hadoop/hbase/wal/WAL.java


 WALPerformanceEvaluation miscalculates append/sync statistics for multiple 
 regions
 --

 Key: HBASE-12655
 URL: https://issues.apache.org/jira/browse/HBASE-12655
 Project: HBase
  Issue Type: Bug
  Components: wal
Affects Versions: 0.99.2
Reporter: Sean Busbey
Assignee: Sean Busbey
Priority: Minor
 Fix For: 1.0.0, 2.0.0

 Attachments: HBASE-12655.1.patch.txt


 Right now the WALPerformaceEvaluation tool sets up each new region by asking 
 for a WAL and then adding a listener. The listener updates running stats on 
 appends / syncs using a shared object in the evaluation tool.
 For WALProviders that reuse WALs (such as the default one always using a 
 single WAL), this results in adding a listener to WALs that already have 
 them. Each of those listeners is then updated on each append/sync.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-12653) Move TestRegionServerOnlineConfigChange TestConfigurationManager to Junit4 tests

2014-12-09 Thread Hudson (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-12653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14239668#comment-14239668
 ] 

Hudson commented on HBASE-12653:


FAILURE: Integrated in HBase-TRUNK #5893 (See 
[https://builds.apache.org/job/HBase-TRUNK/5893/])
HBASE-12653 Move TestRegionServerOnlineConfigChange  TestConfigurationManager 
to Junit4 tests (Ashish) (tedyu: rev c42c36521d67c1add6ea9024b584d3e40389c89b)
* 
hbase-server/src/test/java/org/apache/hadoop/hbase/conf/TestConfigurationManager.java
* 
hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestRegionServerOnlineConfigChange.java


 Move TestRegionServerOnlineConfigChange  TestConfigurationManager to Junit4 
 tests
 --

 Key: HBASE-12653
 URL: https://issues.apache.org/jira/browse/HBASE-12653
 Project: HBase
  Issue Type: Improvement
  Components: test
Affects Versions: 2.0.0, 0.99.2
Reporter: Ashish Singhi
Assignee: Ashish Singhi
Priority: Minor
 Fix For: 1.0.0, 2.0.0

 Attachments: HBASE-12653.patch






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-12659) Replace the method calls to grant and revoke in shell scripts with AccessControlClient

2014-12-09 Thread Andrew Purtell (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-12659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14239671#comment-14239671
 ] 

Andrew Purtell commented on HBASE-12659:


That release audit issue isn't related to this patch. It's good to go. Seems a 
backward compatible change.

+1 for 0.98 and up

 Replace the method calls to grant and revoke in shell scripts with 
 AccessControlClient 
 ---

 Key: HBASE-12659
 URL: https://issues.apache.org/jira/browse/HBASE-12659
 Project: HBase
  Issue Type: Improvement
  Components: security, shell
Reporter: Srikanth Srungarapu
Assignee: Srikanth Srungarapu
Priority: Minor
 Attachments: HBASE-12659.patch


 Currently, the grant and revoke methods of ProtobufUtil methods are being 
 used in ruby shell scripts. Using AccessControlClient methods instead will 
 provide cleaner separation and easier maintenance. Thanks to [~mbertozzi] for 
 making this suggestion.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (HBASE-12630) Provide capability for dropping malfunctioning ConfigurationObserver automatically

2014-12-09 Thread Ashish Singhi (JIRA)

 [ 
https://issues.apache.org/jira/browse/HBASE-12630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ashish Singhi updated HBASE-12630:
--
Status: Patch Available  (was: Open)

Thanks for the reviews [~tedyu]
bq. How about naming the above map configurationObserverExceptionTracker ?
Looks better. Addressed in v3.

bq. Typo: continuosly
Addressed in v3.

bq. There is no need to retrieve the max retry count every time, right ?
Yes. Addressed in v3.

bq. Where are the above methods accessed ?
Not used removed them in v3.

bq. Can you expand the following data structure to include count of failed 
notifications ?
I did not won't to change the existing map structure. Instead changed 
configurationObserverExceptionTracker from HashMap to WeakHashMap. 

 Provide capability for dropping malfunctioning ConfigurationObserver 
 automatically
 --

 Key: HBASE-12630
 URL: https://issues.apache.org/jira/browse/HBASE-12630
 Project: HBase
  Issue Type: Improvement
Reporter: Ted Yu
Assignee: Ashish Singhi
 Fix For: 1.0.0, 2.0.0

 Attachments: HBASE-12630-v2.patch, HBASE-12630-v3.patch, 
 HBASE-12630.patch


 Chatting with Manukranth, online config update feature should handle the case 
 where certain ConfigurationObserver(s) constantly produce exception when 
 notified of config update.
 We can handle such ConfigurationObserver by sidelining it after configurable 
 number of exceptions seen from the ConfigurationObserver.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-12630) Provide capability for dropping malfunctioning ConfigurationObserver automatically

2014-12-09 Thread Ashish Singhi (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-12630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14239683#comment-14239683
 ] 

Ashish Singhi commented on HBASE-12630:
---

bq. Why we need this? If problematic config, load a replacement or a restore?
[~saint@gmail.com], I am not pretty sure why we are doing this way! 
[~tedyu] or [~manukranthk] will have a answer to this.

 Provide capability for dropping malfunctioning ConfigurationObserver 
 automatically
 --

 Key: HBASE-12630
 URL: https://issues.apache.org/jira/browse/HBASE-12630
 Project: HBase
  Issue Type: Improvement
Reporter: Ted Yu
Assignee: Ashish Singhi
 Fix For: 1.0.0, 2.0.0

 Attachments: HBASE-12630-v2.patch, HBASE-12630-v3.patch, 
 HBASE-12630.patch


 Chatting with Manukranth, online config update feature should handle the case 
 where certain ConfigurationObserver(s) constantly produce exception when 
 notified of config update.
 We can handle such ConfigurationObserver by sidelining it after configurable 
 number of exceptions seen from the ConfigurationObserver.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (HBASE-12583) Allow creating reference files even the split row not lies in the storefile range if required

2014-12-09 Thread rajeshbabu (JIRA)

 [ 
https://issues.apache.org/jira/browse/HBASE-12583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

rajeshbabu updated HBASE-12583:
---
Attachment: HBASE-12583_addendum.patch

Here is the addendum corrects the javadoc.

 Allow creating reference files even the split row not lies in the storefile 
 range if required
 -

 Key: HBASE-12583
 URL: https://issues.apache.org/jira/browse/HBASE-12583
 Project: HBase
  Issue Type: Improvement
Reporter: rajeshbabu
Assignee: rajeshbabu
  Labels: Phoenix
 Fix For: 1.0.0, 2.0.0, 0.98.9

 Attachments: HBASE-12583.patch, HBASE-12583_98.patch, 
 HBASE-12583_98_v2.patch, HBASE-12583_addendum.patch, 
 HBASE-12583_branch1.patch, HBASE-12583_branch1_v2.patch, 
 HBASE-12583_v2.patch, HBASE-12583_v3.patch


 Currently in HRegionFileSystem#splitStoreFile we are not creating reference 
 files if the split row not lies in the storefile range that means one of the 
 child region doesn't have any data.
 {code}
// Check whether the split row lies in the range of the store file
 // If it is outside the range, return directly.
 if (top) {
   //check if larger than last key.
   KeyValue splitKey = KeyValueUtil.createFirstOnRow(splitRow);
   byte[] lastKey = f.createReader().getLastKey();
   // If lastKey is null means storefile is empty.
   if (lastKey == null) return null;
   if (f.getReader().getComparator().compareFlatKey(splitKey.getBuffer(),
   splitKey.getKeyOffset(), splitKey.getKeyLength(), lastKey, 0, 
 lastKey.length)  0) {
 return null;
   }
 } else {
   //check if smaller than first key
   KeyValue splitKey = KeyValueUtil.createLastOnRow(splitRow);
   byte[] firstKey = f.createReader().getFirstKey();
   // If firstKey is null means storefile is empty.
   if (firstKey == null) return null;
   if (f.getReader().getComparator().compareFlatKey(splitKey.getBuffer(),
   splitKey.getKeyOffset(), splitKey.getKeyLength(), firstKey, 0, 
 firstKey.length)  0) {
 return null;
   }
 }
 {code}
 In some cases when split row should be compared with part of rowkey(in 
 composite rowkey) mainly for secondary index tables we need to create 
 reference files even when split row not lies in the storefile range so that 
 they can be rewritten to it's child regions by some custom half store file 
 reader which compare the part of row key with split row.
 The check of comparing split row with storefile range and returning directly 
 can be avoided by having special boolean attribute in table descriptor when 
 it set to true. Or else we can have coprocessor hooks so that in the hooks we 
 can create the references and bypass.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-12662) region_status.rb is failing with NoMethodError

2014-12-09 Thread Ashish Singhi (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-12662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14239690#comment-14239690
 ] 

Ashish Singhi commented on HBASE-12662:
---

-1s not related to patch.

 region_status.rb is failing with NoMethodError
 --

 Key: HBASE-12662
 URL: https://issues.apache.org/jira/browse/HBASE-12662
 Project: HBase
  Issue Type: Bug
  Components: shell
Affects Versions: 2.0.0
Reporter: Ashish Singhi
Assignee: Ashish Singhi
 Attachments: HBASE-12662.patch


 {noformat}
 $/hbase-2.0.0-SNAPSHOT/bin hbase org.jruby.Main region_status.rb --table t
 2014-12-09 19:33:06,839 WARN  [main] util.NativeCodeLoader: Unable to load 
 native-hadoop library for your platform... using builtin-java classes where 
 applicable
 NoMethodError: undefined method `cache_blocks=' for 
 #Java::OrgApacheHadoopHbaseClient::Scan:0x1c7abd4c
   (root) at region_status.rb:93
 {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-12630) Provide capability for dropping malfunctioning ConfigurationObserver automatically

2014-12-09 Thread Ted Yu (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-12630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14239715#comment-14239715
 ] 

Ted Yu commented on HBASE-12630:


As shown in description, this JIRA handles ConfigurationObserver(s) which 
constantly produce exception when notified.

 Provide capability for dropping malfunctioning ConfigurationObserver 
 automatically
 --

 Key: HBASE-12630
 URL: https://issues.apache.org/jira/browse/HBASE-12630
 Project: HBase
  Issue Type: Improvement
Reporter: Ted Yu
Assignee: Ashish Singhi
 Fix For: 1.0.0, 2.0.0

 Attachments: HBASE-12630-v2.patch, HBASE-12630-v3.patch, 
 HBASE-12630.patch


 Chatting with Manukranth, online config update feature should handle the case 
 where certain ConfigurationObserver(s) constantly produce exception when 
 notified of config update.
 We can handle such ConfigurationObserver by sidelining it after configurable 
 number of exceptions seen from the ConfigurationObserver.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-11677) Make Logger instance modifiers consistent

2014-12-09 Thread Andrew Purtell (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-11677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14239719#comment-14239719
 ] 

Andrew Purtell commented on HBASE-11677:


bq. For Logs that end up shared amongst non-test classes, what are people's 
thoughts? Worth the trouble to transition to independent loggers? 

Sure

bq. Just change without deprecation? 

If I recall correctly generally it's fine but there are a couple of special 
cases, for example trace logging in RPC. 

bq. Double log to the current logger and the eventual logger with a note in 
release notes that the former is going away?

Overkill?

 Make Logger instance modifiers consistent
 -

 Key: HBASE-11677
 URL: https://issues.apache.org/jira/browse/HBASE-11677
 Project: HBase
  Issue Type: Task
Reporter: Sean Busbey
Priority: Minor
  Labels: beginner, sonar
 Attachments: HBASE-11677-v1.patch, HBASE-11677.patch


 We have some instances of Logger that are missing one of being private, 
 static, and final.
 ex from HealthChecker.java, missing final
 {code}
 private static Log LOG = LogFactory.getLog(HealthChecker.class);
 {code}
 * Clean up where possible by making {{private static final}}
 * If we can't, add a non-javadoc note about why
 One way to look for problematic instances is to grep for initial assignment 
 for the commonly used LOG member, e.g.
 * missing final: {{grep -r LOG = * | grep -v final}}
 * missing static: {{grep -r LOG = * | grep -v static}}
 * missing private: {{grep -r LOG = * | grep -v private}}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (HBASE-12662) region_status.rb is failing with NoMethodError

2014-12-09 Thread Ted Yu (JIRA)

 [ 
https://issues.apache.org/jira/browse/HBASE-12662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ted Yu updated HBASE-12662:
---
   Resolution: Fixed
Fix Version/s: 2.0.0
   1.0.0
 Hadoop Flags: Reviewed
   Status: Resolved  (was: Patch Available)

Thanks for the patch, Ashish.

 region_status.rb is failing with NoMethodError
 --

 Key: HBASE-12662
 URL: https://issues.apache.org/jira/browse/HBASE-12662
 Project: HBase
  Issue Type: Bug
  Components: shell
Affects Versions: 2.0.0
Reporter: Ashish Singhi
Assignee: Ashish Singhi
 Fix For: 1.0.0, 2.0.0

 Attachments: HBASE-12662.patch


 {noformat}
 $/hbase-2.0.0-SNAPSHOT/bin hbase org.jruby.Main region_status.rb --table t
 2014-12-09 19:33:06,839 WARN  [main] util.NativeCodeLoader: Unable to load 
 native-hadoop library for your platform... using builtin-java classes where 
 applicable
 NoMethodError: undefined method `cache_blocks=' for 
 #Java::OrgApacheHadoopHbaseClient::Scan:0x1c7abd4c
   (root) at region_status.rb:93
 {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-12655) WALPerformanceEvaluation miscalculates append/sync statistics for multiple regions

2014-12-09 Thread Hudson (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-12655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14239744#comment-14239744
 ] 

Hudson commented on HBASE-12655:


FAILURE: Integrated in HBase-1.0 #558 (See 
[https://builds.apache.org/job/HBase-1.0/558/])
HBASE-12655 WALPerformanceEvaluation should only add stat gathering listener 
once per WAL. (busbey: rev d2d6945e8951391a3b04d89f2879b51d7df26bb7)
* hbase-server/src/main/java/org/apache/hadoop/hbase/wal/WAL.java
* 
hbase-server/src/test/java/org/apache/hadoop/hbase/wal/WALPerformanceEvaluation.java
* 
hbase-server/src/test/java/org/apache/hadoop/hbase/wal/TestDefaultWALProvider.java


 WALPerformanceEvaluation miscalculates append/sync statistics for multiple 
 regions
 --

 Key: HBASE-12655
 URL: https://issues.apache.org/jira/browse/HBASE-12655
 Project: HBase
  Issue Type: Bug
  Components: wal
Affects Versions: 0.99.2
Reporter: Sean Busbey
Assignee: Sean Busbey
Priority: Minor
 Fix For: 1.0.0, 2.0.0

 Attachments: HBASE-12655.1.patch.txt


 Right now the WALPerformaceEvaluation tool sets up each new region by asking 
 for a WAL and then adding a listener. The listener updates running stats on 
 appends / syncs using a shared object in the evaluation tool.
 For WALProviders that reuse WALs (such as the default one always using a 
 single WAL), this results in adding a listener to WALs that already have 
 them. Each of those listeners is then updated on each append/sync.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-12661) rat check fails for several files

2014-12-09 Thread Hudson (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-12661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14239743#comment-14239743
 ] 

Hudson commented on HBASE-12661:


FAILURE: Integrated in HBase-1.0 #558 (See 
[https://builds.apache.org/job/HBase-1.0/558/])
HBASE-12661 add missing licenses. (busbey: rev 
2372739e462bc4ee404815657f37141a2599177b)
* 
hbase-hadoop2-compat/src/main/java/org/apache/hadoop/hbase/replication/regionserver/MetricsReplicationSourceFactoryImpl.java
* 
hbase-hadoop-compat/src/main/java/org/apache/hadoop/hbase/replication/regionserver/MetricsReplicationSinkSource.java
* 
hbase-hadoop2-compat/src/test/java/org/apache/hadoop/hbase/replication/regionserver/TestMetricsReplicationSourceFactoryImpl.java
* 
hbase-hadoop2-compat/src/main/java/org/apache/hadoop/hbase/replication/regionserver/MetricsReplicationSourceSourceImpl.java


 rat check fails for several files
 -

 Key: HBASE-12661
 URL: https://issues.apache.org/jira/browse/HBASE-12661
 Project: HBase
  Issue Type: Bug
Affects Versions: 1.0.0, 2.0.0
Reporter: Sean Busbey
Assignee: Sean Busbey
Priority: Blocker
 Fix For: 1.0.0, 2.0.0

 Attachments: HBASE-12661.1.patch.txt, HBASE-12661.2.patch.txt


 newly added files missing a license header:
 * MetricsReplicationSinkSource
 * MetricsReplicationSourceFactoryImpl
 * MetricsReplicationSourceSourceImpl
 * TestMetricsReplicationSourceFactoryImpl



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Created] (HBASE-12664) TestDefaultLoadBalancer.testBalanceCluster fails in CachedDNSToSwitchMapping

2014-12-09 Thread stack (JIRA)
stack created HBASE-12664:
-

 Summary: TestDefaultLoadBalancer.testBalanceCluster fails in 
CachedDNSToSwitchMapping
 Key: HBASE-12664
 URL: https://issues.apache.org/jira/browse/HBASE-12664
 Project: HBase
  Issue Type: Bug
  Components: test
Reporter: stack
Priority: Minor
 Fix For: 1.0.0, 2.0.0


https://builds.apache.org/job/HBase-TRUNK/5893/testReport/org.apache.hadoop.hbase.master.balancer/TestDefaultLoadBalancer/testBalanceCluster/

{code}
java.lang.Exception: test timed out after 6 milliseconds
at java.net.Inet4AddressImpl.lookupAllHostAddr(Native Method)
at java.net.InetAddress$1.lookupAllHostAddr(InetAddress.java:894)
at 
java.net.InetAddress.getAddressesFromNameService(InetAddress.java:1286)
at java.net.InetAddress.getAllByName0(InetAddress.java:1239)
at java.net.InetAddress.getAllByName(InetAddress.java:1155)
at java.net.InetAddress.getAllByName(InetAddress.java:1091)
at java.net.InetAddress.getByName(InetAddress.java:1041)
at org.apache.hadoop.net.NetUtils.normalizeHostName(NetUtils.java:561)
at org.apache.hadoop.net.NetUtils.normalizeHostNames(NetUtils.java:578)
at 
org.apache.hadoop.net.CachedDNSToSwitchMapping.resolve(CachedDNSToSwitchMapping.java:109)
at 
org.apache.hadoop.hbase.master.RackManager.getRack(RackManager.java:66)
at 
org.apache.hadoop.hbase.master.balancer.BaseLoadBalancer$Cluster.init(BaseLoadBalancer.java:274)
at 
org.apache.hadoop.hbase.master.balancer.BaseLoadBalancer$Cluster.init(BaseLoadBalancer.java:152)
at 
org.apache.hadoop.hbase.master.balancer.SimpleLoadBalancer.balanceCluster(SimpleLoadBalancer.java:201)
at 
org.apache.hadoop.hbase.master.balancer.TestDefaultLoadBalancer.testBalanceCluster(TestDefaultLoadBalancer.java:119)
{code}




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (HBASE-12583) Allow creating reference files even the split row not lies in the storefile range if required

2014-12-09 Thread rajeshbabu (JIRA)

 [ 
https://issues.apache.org/jira/browse/HBASE-12583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

rajeshbabu updated HBASE-12583:
---
  Resolution: Fixed
Hadoop Flags: Reviewed
  Status: Resolved  (was: Patch Available)

Pushed to 0.98,branch-1 and master branches.
Thanks all for the reviews.

 Allow creating reference files even the split row not lies in the storefile 
 range if required
 -

 Key: HBASE-12583
 URL: https://issues.apache.org/jira/browse/HBASE-12583
 Project: HBase
  Issue Type: Improvement
Reporter: rajeshbabu
Assignee: rajeshbabu
  Labels: Phoenix
 Fix For: 1.0.0, 2.0.0, 0.98.9

 Attachments: HBASE-12583.patch, HBASE-12583_98.patch, 
 HBASE-12583_98_v2.patch, HBASE-12583_addendum.patch, 
 HBASE-12583_branch1.patch, HBASE-12583_branch1_v2.patch, 
 HBASE-12583_v2.patch, HBASE-12583_v3.patch


 Currently in HRegionFileSystem#splitStoreFile we are not creating reference 
 files if the split row not lies in the storefile range that means one of the 
 child region doesn't have any data.
 {code}
// Check whether the split row lies in the range of the store file
 // If it is outside the range, return directly.
 if (top) {
   //check if larger than last key.
   KeyValue splitKey = KeyValueUtil.createFirstOnRow(splitRow);
   byte[] lastKey = f.createReader().getLastKey();
   // If lastKey is null means storefile is empty.
   if (lastKey == null) return null;
   if (f.getReader().getComparator().compareFlatKey(splitKey.getBuffer(),
   splitKey.getKeyOffset(), splitKey.getKeyLength(), lastKey, 0, 
 lastKey.length)  0) {
 return null;
   }
 } else {
   //check if smaller than first key
   KeyValue splitKey = KeyValueUtil.createLastOnRow(splitRow);
   byte[] firstKey = f.createReader().getFirstKey();
   // If firstKey is null means storefile is empty.
   if (firstKey == null) return null;
   if (f.getReader().getComparator().compareFlatKey(splitKey.getBuffer(),
   splitKey.getKeyOffset(), splitKey.getKeyLength(), firstKey, 0, 
 firstKey.length)  0) {
 return null;
   }
 }
 {code}
 In some cases when split row should be compared with part of rowkey(in 
 composite rowkey) mainly for secondary index tables we need to create 
 reference files even when split row not lies in the storefile range so that 
 they can be rewritten to it's child regions by some custom half store file 
 reader which compare the part of row key with split row.
 The check of comparing split row with storefile range and returning directly 
 can be avoided by having special boolean attribute in table descriptor when 
 it set to true. Or else we can have coprocessor hooks so that in the hooks we 
 can create the references and bypass.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (HBASE-12664) TestDefaultLoadBalancer.testBalanceCluster fails in CachedDNSToSwitchMapping

2014-12-09 Thread stack (JIRA)

 [ 
https://issues.apache.org/jira/browse/HBASE-12664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

stack updated HBASE-12664:
--
Assignee: stack
  Status: Patch Available  (was: Open)

 TestDefaultLoadBalancer.testBalanceCluster fails in CachedDNSToSwitchMapping
 

 Key: HBASE-12664
 URL: https://issues.apache.org/jira/browse/HBASE-12664
 Project: HBase
  Issue Type: Bug
  Components: test
Reporter: stack
Assignee: stack
Priority: Minor
 Fix For: 1.0.0, 2.0.0

 Attachments: 12664.txt


 https://builds.apache.org/job/HBase-TRUNK/5893/testReport/org.apache.hadoop.hbase.master.balancer/TestDefaultLoadBalancer/testBalanceCluster/
 {code}
 java.lang.Exception: test timed out after 6 milliseconds
   at java.net.Inet4AddressImpl.lookupAllHostAddr(Native Method)
   at java.net.InetAddress$1.lookupAllHostAddr(InetAddress.java:894)
   at 
 java.net.InetAddress.getAddressesFromNameService(InetAddress.java:1286)
   at java.net.InetAddress.getAllByName0(InetAddress.java:1239)
   at java.net.InetAddress.getAllByName(InetAddress.java:1155)
   at java.net.InetAddress.getAllByName(InetAddress.java:1091)
   at java.net.InetAddress.getByName(InetAddress.java:1041)
   at org.apache.hadoop.net.NetUtils.normalizeHostName(NetUtils.java:561)
   at org.apache.hadoop.net.NetUtils.normalizeHostNames(NetUtils.java:578)
   at 
 org.apache.hadoop.net.CachedDNSToSwitchMapping.resolve(CachedDNSToSwitchMapping.java:109)
   at 
 org.apache.hadoop.hbase.master.RackManager.getRack(RackManager.java:66)
   at 
 org.apache.hadoop.hbase.master.balancer.BaseLoadBalancer$Cluster.init(BaseLoadBalancer.java:274)
   at 
 org.apache.hadoop.hbase.master.balancer.BaseLoadBalancer$Cluster.init(BaseLoadBalancer.java:152)
   at 
 org.apache.hadoop.hbase.master.balancer.SimpleLoadBalancer.balanceCluster(SimpleLoadBalancer.java:201)
   at 
 org.apache.hadoop.hbase.master.balancer.TestDefaultLoadBalancer.testBalanceCluster(TestDefaultLoadBalancer.java:119)
 {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (HBASE-12664) TestDefaultLoadBalancer.testBalanceCluster fails in CachedDNSToSwitchMapping

2014-12-09 Thread stack (JIRA)

 [ 
https://issues.apache.org/jira/browse/HBASE-12664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

stack updated HBASE-12664:
--
Attachment: 12664.txt

Put mocking of RackManager everywhere it is used.

 TestDefaultLoadBalancer.testBalanceCluster fails in CachedDNSToSwitchMapping
 

 Key: HBASE-12664
 URL: https://issues.apache.org/jira/browse/HBASE-12664
 Project: HBase
  Issue Type: Bug
  Components: test
Reporter: stack
Priority: Minor
 Fix For: 1.0.0, 2.0.0

 Attachments: 12664.txt


 https://builds.apache.org/job/HBase-TRUNK/5893/testReport/org.apache.hadoop.hbase.master.balancer/TestDefaultLoadBalancer/testBalanceCluster/
 {code}
 java.lang.Exception: test timed out after 6 milliseconds
   at java.net.Inet4AddressImpl.lookupAllHostAddr(Native Method)
   at java.net.InetAddress$1.lookupAllHostAddr(InetAddress.java:894)
   at 
 java.net.InetAddress.getAddressesFromNameService(InetAddress.java:1286)
   at java.net.InetAddress.getAllByName0(InetAddress.java:1239)
   at java.net.InetAddress.getAllByName(InetAddress.java:1155)
   at java.net.InetAddress.getAllByName(InetAddress.java:1091)
   at java.net.InetAddress.getByName(InetAddress.java:1041)
   at org.apache.hadoop.net.NetUtils.normalizeHostName(NetUtils.java:561)
   at org.apache.hadoop.net.NetUtils.normalizeHostNames(NetUtils.java:578)
   at 
 org.apache.hadoop.net.CachedDNSToSwitchMapping.resolve(CachedDNSToSwitchMapping.java:109)
   at 
 org.apache.hadoop.hbase.master.RackManager.getRack(RackManager.java:66)
   at 
 org.apache.hadoop.hbase.master.balancer.BaseLoadBalancer$Cluster.init(BaseLoadBalancer.java:274)
   at 
 org.apache.hadoop.hbase.master.balancer.BaseLoadBalancer$Cluster.init(BaseLoadBalancer.java:152)
   at 
 org.apache.hadoop.hbase.master.balancer.SimpleLoadBalancer.balanceCluster(SimpleLoadBalancer.java:201)
   at 
 org.apache.hadoop.hbase.master.balancer.TestDefaultLoadBalancer.testBalanceCluster(TestDefaultLoadBalancer.java:119)
 {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-12630) Provide capability for dropping malfunctioning ConfigurationObserver automatically

2014-12-09 Thread stack (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-12630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14239815#comment-14239815
 ] 

stack commented on HBASE-12630:
---

bq. As shown in description, this JIRA handles ConfigurationObserver(s) which 
constantly produce exception when notified.

Description 'shows' nothing other than that you are probably harrassing 
[~manukranthk] offline.  Is this a problem?  Has it been observed in the wild?

bq. Stack, I am not pretty sure why we are doing this way! 

[~ashish singhi] You do good work.  Suggest you pick clean issues that clearly 
move the project forward.  If you need input, just ask on dev list (Stuff 
marked critical or major against 1.0 would be good in general.  I am not sure 
why this issue is marked major for 1.0...  how often are folks deploying new 
classes with ConfigurationObserver implementations?)

 Provide capability for dropping malfunctioning ConfigurationObserver 
 automatically
 --

 Key: HBASE-12630
 URL: https://issues.apache.org/jira/browse/HBASE-12630
 Project: HBase
  Issue Type: Improvement
Reporter: Ted Yu
Assignee: Ashish Singhi
 Fix For: 1.0.0, 2.0.0

 Attachments: HBASE-12630-v2.patch, HBASE-12630-v3.patch, 
 HBASE-12630.patch


 Chatting with Manukranth, online config update feature should handle the case 
 where certain ConfigurationObserver(s) constantly produce exception when 
 notified of config update.
 We can handle such ConfigurationObserver by sidelining it after configurable 
 number of exceptions seen from the ConfigurationObserver.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-12663) unify getTableDescriptors() and listTableDescriptorsByNamespace()

2014-12-09 Thread Hadoop QA (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-12663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14239827#comment-14239827
 ] 

Hadoop QA commented on HBASE-12663:
---

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12686033/HBASE-12663-v0.patch
  against master branch at commit 51ab8a05b99a13943343f0b55f2dae282a574c68.
  ATTACHMENT ID: 12686033

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:green}+1 tests included{color}.  The patch appears to include 6 new 
or modified tests.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:red}-1 javadoc{color}.  The javadoc tool appears to have generated 1 
warning messages.

{color:green}+1 checkstyle{color}.  The applied patch does not increase the 
total number of checkstyle errors

{color:green}+1 findbugs{color}.  The patch does not introduce any new 
Findbugs (version 2.0.3) warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:green}+1 lineLengths{color}.  The patch does not introduce lines 
longer than 100

  {color:green}+1 site{color}.  The mvn site goal succeeds with this patch.

 {color:red}-1 core tests{color}.  The patch failed these unit tests:
   
org.apache.hadoop.hbase.master.balancer.TestDefaultLoadBalancer

Test results: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12020//testReport/
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12020//artifact/patchprocess/newPatchFindbugsWarningshbase-rest.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12020//artifact/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12020//artifact/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12020//artifact/patchprocess/newPatchFindbugsWarningshbase-annotations.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12020//artifact/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12020//artifact/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12020//artifact/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12020//artifact/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12020//artifact/patchprocess/newPatchFindbugsWarningshbase-thrift.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12020//artifact/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12020//artifact/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html
Checkstyle Errors: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12020//artifact/patchprocess/checkstyle-aggregate.html

  Javadoc warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12020//artifact/patchprocess/patchJavadocWarnings.txt
Console output: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12020//console

This message is automatically generated.

 unify getTableDescriptors() and listTableDescriptorsByNamespace()
 -

 Key: HBASE-12663
 URL: https://issues.apache.org/jira/browse/HBASE-12663
 Project: HBase
  Issue Type: Bug
  Components: master, security
Affects Versions: 1.0.0, 2.0.0
Reporter: Matteo Bertozzi
Assignee: Matteo Bertozzi
 Attachments: HBASE-12663-v0.patch


 currently we have getTableDescriptors()/listTableNames()
 and listTableDescriptorsByNamespace()/listTableNamesByNamespace()
 which are just filtering by namespace.
 The first two are already able to filter tables by regex,
 and there is also an ACL check which shows only the table the user have 
 access to,
 while the namespace version just return a list without any ACLs check.
 to me there is no point to keep the *ByNamespace() version on the server 
 side, 
 since the base version must be able to do the filtering by
 namespace and the ACLs check must be the same for both anyway.
 or at least we can just call the base version with the ns filtering.



--
This message was sent by Atlassian JIRA

[jira] [Commented] (HBASE-12664) TestDefaultLoadBalancer.testBalanceCluster fails in CachedDNSToSwitchMapping

2014-12-09 Thread Andrew Purtell (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-12664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14239850#comment-14239850
 ] 

Andrew Purtell commented on HBASE-12664:


Yep, seeing this locally too.

+1

 TestDefaultLoadBalancer.testBalanceCluster fails in CachedDNSToSwitchMapping
 

 Key: HBASE-12664
 URL: https://issues.apache.org/jira/browse/HBASE-12664
 Project: HBase
  Issue Type: Bug
  Components: test
Reporter: stack
Assignee: stack
Priority: Minor
 Fix For: 1.0.0, 2.0.0

 Attachments: 12664.txt


 https://builds.apache.org/job/HBase-TRUNK/5893/testReport/org.apache.hadoop.hbase.master.balancer/TestDefaultLoadBalancer/testBalanceCluster/
 {code}
 java.lang.Exception: test timed out after 6 milliseconds
   at java.net.Inet4AddressImpl.lookupAllHostAddr(Native Method)
   at java.net.InetAddress$1.lookupAllHostAddr(InetAddress.java:894)
   at 
 java.net.InetAddress.getAddressesFromNameService(InetAddress.java:1286)
   at java.net.InetAddress.getAllByName0(InetAddress.java:1239)
   at java.net.InetAddress.getAllByName(InetAddress.java:1155)
   at java.net.InetAddress.getAllByName(InetAddress.java:1091)
   at java.net.InetAddress.getByName(InetAddress.java:1041)
   at org.apache.hadoop.net.NetUtils.normalizeHostName(NetUtils.java:561)
   at org.apache.hadoop.net.NetUtils.normalizeHostNames(NetUtils.java:578)
   at 
 org.apache.hadoop.net.CachedDNSToSwitchMapping.resolve(CachedDNSToSwitchMapping.java:109)
   at 
 org.apache.hadoop.hbase.master.RackManager.getRack(RackManager.java:66)
   at 
 org.apache.hadoop.hbase.master.balancer.BaseLoadBalancer$Cluster.init(BaseLoadBalancer.java:274)
   at 
 org.apache.hadoop.hbase.master.balancer.BaseLoadBalancer$Cluster.init(BaseLoadBalancer.java:152)
   at 
 org.apache.hadoop.hbase.master.balancer.SimpleLoadBalancer.balanceCluster(SimpleLoadBalancer.java:201)
   at 
 org.apache.hadoop.hbase.master.balancer.TestDefaultLoadBalancer.testBalanceCluster(TestDefaultLoadBalancer.java:119)
 {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-12662) region_status.rb is failing with NoMethodError

2014-12-09 Thread Hudson (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-12662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14239851#comment-14239851
 ] 

Hudson commented on HBASE-12662:


FAILURE: Integrated in HBase-1.0 #559 (See 
[https://builds.apache.org/job/HBase-1.0/559/])
HBASE-12662 region_status.rb is failing with NoMethodError (Ashish Singhi) 
(tedyu: rev 1fae34de56f818a84bde1be33755d4ddf2c04d8f)
* bin/region_status.rb


 region_status.rb is failing with NoMethodError
 --

 Key: HBASE-12662
 URL: https://issues.apache.org/jira/browse/HBASE-12662
 Project: HBase
  Issue Type: Bug
  Components: shell
Affects Versions: 2.0.0
Reporter: Ashish Singhi
Assignee: Ashish Singhi
 Fix For: 1.0.0, 2.0.0

 Attachments: HBASE-12662.patch


 {noformat}
 $/hbase-2.0.0-SNAPSHOT/bin hbase org.jruby.Main region_status.rb --table t
 2014-12-09 19:33:06,839 WARN  [main] util.NativeCodeLoader: Unable to load 
 native-hadoop library for your platform... using builtin-java classes where 
 applicable
 NoMethodError: undefined method `cache_blocks=' for 
 #Java::OrgApacheHadoopHbaseClient::Scan:0x1c7abd4c
   (root) at region_status.rb:93
 {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-12663) unify getTableDescriptors() and listTableDescriptorsByNamespace()

2014-12-09 Thread stack (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-12663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14239864#comment-14239864
 ] 

stack commented on HBASE-12663:
---

Failure is HBASE-12664

Patch LGTM. +1  Safe to add in 1.0 because it is additive, not removing 
anything.


 unify getTableDescriptors() and listTableDescriptorsByNamespace()
 -

 Key: HBASE-12663
 URL: https://issues.apache.org/jira/browse/HBASE-12663
 Project: HBase
  Issue Type: Bug
  Components: master, security
Affects Versions: 1.0.0, 2.0.0
Reporter: Matteo Bertozzi
Assignee: Matteo Bertozzi
 Attachments: HBASE-12663-v0.patch


 currently we have getTableDescriptors()/listTableNames()
 and listTableDescriptorsByNamespace()/listTableNamesByNamespace()
 which are just filtering by namespace.
 The first two are already able to filter tables by regex,
 and there is also an ACL check which shows only the table the user have 
 access to,
 while the namespace version just return a list without any ACLs check.
 to me there is no point to keep the *ByNamespace() version on the server 
 side, 
 since the base version must be able to do the filtering by
 namespace and the ACLs check must be the same for both anyway.
 or at least we can just call the base version with the ns filtering.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-12630) Provide capability for dropping malfunctioning ConfigurationObserver automatically

2014-12-09 Thread Hadoop QA (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-12630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14239876#comment-14239876
 ] 

Hadoop QA commented on HBASE-12630:
---

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12686035/HBASE-12630-v3.patch
  against master branch at commit 51ab8a05b99a13943343f0b55f2dae282a574c68.
  ATTACHMENT ID: 12686035

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:green}+1 tests included{color}.  The patch appears to include 4 new 
or modified tests.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:red}-1 javadoc{color}.  The javadoc tool appears to have generated 1 
warning messages.

{color:green}+1 checkstyle{color}.  The applied patch does not increase the 
total number of checkstyle errors

{color:green}+1 findbugs{color}.  The patch does not introduce any new 
Findbugs (version 2.0.3) warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:green}+1 lineLengths{color}.  The patch does not introduce lines 
longer than 100

  {color:green}+1 site{color}.  The mvn site goal succeeds with this patch.

{color:green}+1 core tests{color}.  The patch passed unit tests in .

Test results: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12021//testReport/
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12021//artifact/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12021//artifact/patchprocess/newPatchFindbugsWarningshbase-annotations.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12021//artifact/patchprocess/newPatchFindbugsWarningshbase-thrift.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12021//artifact/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12021//artifact/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12021//artifact/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12021//artifact/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12021//artifact/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12021//artifact/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12021//artifact/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12021//artifact/patchprocess/newPatchFindbugsWarningshbase-rest.html
Checkstyle Errors: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12021//artifact/patchprocess/checkstyle-aggregate.html

  Javadoc warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12021//artifact/patchprocess/patchJavadocWarnings.txt
Console output: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12021//console

This message is automatically generated.

 Provide capability for dropping malfunctioning ConfigurationObserver 
 automatically
 --

 Key: HBASE-12630
 URL: https://issues.apache.org/jira/browse/HBASE-12630
 Project: HBase
  Issue Type: Improvement
Reporter: Ted Yu
Assignee: Ashish Singhi
 Fix For: 1.0.0, 2.0.0

 Attachments: HBASE-12630-v2.patch, HBASE-12630-v3.patch, 
 HBASE-12630.patch


 Chatting with Manukranth, online config update feature should handle the case 
 where certain ConfigurationObserver(s) constantly produce exception when 
 notified of config update.
 We can handle such ConfigurationObserver by sidelining it after configurable 
 number of exceptions seen from the ConfigurationObserver.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (HBASE-12664) TestDefaultLoadBalancer.testBalanceCluster fails in CachedDNSToSwitchMapping

2014-12-09 Thread stack (JIRA)

 [ 
https://issues.apache.org/jira/browse/HBASE-12664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

stack updated HBASE-12664:
--
  Resolution: Fixed
Hadoop Flags: Reviewed
  Status: Resolved  (was: Patch Available)

Pushed to branch-1+

 TestDefaultLoadBalancer.testBalanceCluster fails in CachedDNSToSwitchMapping
 

 Key: HBASE-12664
 URL: https://issues.apache.org/jira/browse/HBASE-12664
 Project: HBase
  Issue Type: Bug
  Components: test
Reporter: stack
Assignee: stack
Priority: Minor
 Fix For: 1.0.0, 2.0.0

 Attachments: 12664.txt


 https://builds.apache.org/job/HBase-TRUNK/5893/testReport/org.apache.hadoop.hbase.master.balancer/TestDefaultLoadBalancer/testBalanceCluster/
 {code}
 java.lang.Exception: test timed out after 6 milliseconds
   at java.net.Inet4AddressImpl.lookupAllHostAddr(Native Method)
   at java.net.InetAddress$1.lookupAllHostAddr(InetAddress.java:894)
   at 
 java.net.InetAddress.getAddressesFromNameService(InetAddress.java:1286)
   at java.net.InetAddress.getAllByName0(InetAddress.java:1239)
   at java.net.InetAddress.getAllByName(InetAddress.java:1155)
   at java.net.InetAddress.getAllByName(InetAddress.java:1091)
   at java.net.InetAddress.getByName(InetAddress.java:1041)
   at org.apache.hadoop.net.NetUtils.normalizeHostName(NetUtils.java:561)
   at org.apache.hadoop.net.NetUtils.normalizeHostNames(NetUtils.java:578)
   at 
 org.apache.hadoop.net.CachedDNSToSwitchMapping.resolve(CachedDNSToSwitchMapping.java:109)
   at 
 org.apache.hadoop.hbase.master.RackManager.getRack(RackManager.java:66)
   at 
 org.apache.hadoop.hbase.master.balancer.BaseLoadBalancer$Cluster.init(BaseLoadBalancer.java:274)
   at 
 org.apache.hadoop.hbase.master.balancer.BaseLoadBalancer$Cluster.init(BaseLoadBalancer.java:152)
   at 
 org.apache.hadoop.hbase.master.balancer.SimpleLoadBalancer.balanceCluster(SimpleLoadBalancer.java:201)
   at 
 org.apache.hadoop.hbase.master.balancer.TestDefaultLoadBalancer.testBalanceCluster(TestDefaultLoadBalancer.java:119)
 {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-12652) Allow unmanaged connections in MetaTableAccessor

2014-12-09 Thread Nick Dimiduk (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-12652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14239882#comment-14239882
 ] 

Nick Dimiduk commented on HBASE-12652:
--

Looking good [~sduskis].

Can we rename this method getMetaTable? Seems it's signature changed recently, 
so why not remove the 'H' from the name?

{noformat}
+  static Table getMetaHTable(final Connection connection)
{noformat}

I only see 1 javadoc warning, looks like it's

{noformat}
[WARNING] 
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/hbase-server/src/main/java/org/apache/hadoop/hbase/util/HBaseFsckRepair.java:68:
 warning - @param argument admin is not a parameter name.
{noformat}

Checkstyle warnings, again cannot find the other:

MetaTableAccessor, Unused import - org.apache.hadoop.hbase.client.HConnection

+1, will clean these on commit

 Allow unmanaged connections in MetaTableAccessor
 

 Key: HBASE-12652
 URL: https://issues.apache.org/jira/browse/HBASE-12652
 Project: HBase
  Issue Type: Bug
Affects Versions: 1.0.0, 2.0.0
Reporter: Solomon Duskis
Assignee: Solomon Duskis
 Attachments: HBASE-12652.patch, HBASE-12652.patch, HBASE-12652B.patch


 Passing in an unmanaged connnection to MetaTableAccessor causes an exception. 
  MetaTableAccessor should be able to use both unmanaged and managed 
 connections.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-12652) Allow unmanaged connections in MetaTableAccessor

2014-12-09 Thread Nick Dimiduk (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-12652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14239883#comment-14239883
 ] 

Nick Dimiduk commented on HBASE-12652:
--

That is, will clean the warnings on commit. Open question re: method name 
remains.

 Allow unmanaged connections in MetaTableAccessor
 

 Key: HBASE-12652
 URL: https://issues.apache.org/jira/browse/HBASE-12652
 Project: HBase
  Issue Type: Bug
Affects Versions: 1.0.0, 2.0.0
Reporter: Solomon Duskis
Assignee: Solomon Duskis
 Attachments: HBASE-12652.patch, HBASE-12652.patch, HBASE-12652B.patch


 Passing in an unmanaged connnection to MetaTableAccessor causes an exception. 
  MetaTableAccessor should be able to use both unmanaged and managed 
 connections.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-12583) Allow creating reference files even the split row not lies in the storefile range if required

2014-12-09 Thread Hadoop QA (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-12583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14239884#comment-14239884
 ] 

Hadoop QA commented on HBASE-12583:
---

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  
http://issues.apache.org/jira/secure/attachment/12686037/HBASE-12583_addendum.patch
  against master branch at commit 51ab8a05b99a13943343f0b55f2dae282a574c68.
  ATTACHMENT ID: 12686037

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:red}-1 tests included{color}.  The patch doesn't appear to include 
any new or modified tests.
Please justify why no new tests are needed for this 
patch.
Also please list what manual steps were performed to 
verify this patch.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 javadoc{color}.  The javadoc tool did not generate any 
warning messages.

{color:green}+1 checkstyle{color}.  The applied patch does not increase the 
total number of checkstyle errors

{color:green}+1 findbugs{color}.  The patch does not introduce any new 
Findbugs (version 2.0.3) warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:green}+1 lineLengths{color}.  The patch does not introduce lines 
longer than 100

  {color:green}+1 site{color}.  The mvn site goal succeeds with this patch.

{color:green}+1 core tests{color}.  The patch passed unit tests in .

Test results: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12022//testReport/
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12022//artifact/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12022//artifact/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12022//artifact/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12022//artifact/patchprocess/newPatchFindbugsWarningshbase-annotations.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12022//artifact/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12022//artifact/patchprocess/newPatchFindbugsWarningshbase-rest.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12022//artifact/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12022//artifact/patchprocess/newPatchFindbugsWarningshbase-thrift.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12022//artifact/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12022//artifact/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12022//artifact/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html
Checkstyle Errors: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12022//artifact/patchprocess/checkstyle-aggregate.html

  Console output: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12022//console

This message is automatically generated.

 Allow creating reference files even the split row not lies in the storefile 
 range if required
 -

 Key: HBASE-12583
 URL: https://issues.apache.org/jira/browse/HBASE-12583
 Project: HBase
  Issue Type: Improvement
Reporter: rajeshbabu
Assignee: rajeshbabu
  Labels: Phoenix
 Fix For: 1.0.0, 2.0.0, 0.98.9

 Attachments: HBASE-12583.patch, HBASE-12583_98.patch, 
 HBASE-12583_98_v2.patch, HBASE-12583_addendum.patch, 
 HBASE-12583_branch1.patch, HBASE-12583_branch1_v2.patch, 
 HBASE-12583_v2.patch, HBASE-12583_v3.patch


 Currently in HRegionFileSystem#splitStoreFile we are not creating reference 
 files if the split row not lies in the storefile range that means one of the 
 child region doesn't have any data.
 {code}
// Check whether the split row lies in the range of the store file
 // If it is outside the range, return directly.
 if (top) {
   //check if larger than last key.
   KeyValue splitKey = KeyValueUtil.createFirstOnRow(splitRow);
   byte[] lastKey = f.createReader().getLastKey();

[jira] [Commented] (HBASE-12652) Allow unmanaged connections in MetaTableAccessor

2014-12-09 Thread Nick Dimiduk (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-12652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14239899#comment-14239899
 ] 

Nick Dimiduk commented on HBASE-12652:
--

getMetaHTable is an internal API but it's used a bunch of places. Can leave 
that for a separate ticket.

 Allow unmanaged connections in MetaTableAccessor
 

 Key: HBASE-12652
 URL: https://issues.apache.org/jira/browse/HBASE-12652
 Project: HBase
  Issue Type: Bug
Affects Versions: 1.0.0, 2.0.0
Reporter: Solomon Duskis
Assignee: Solomon Duskis
 Attachments: HBASE-12652.patch, HBASE-12652.patch, HBASE-12652B.patch


 Passing in an unmanaged connnection to MetaTableAccessor causes an exception. 
  MetaTableAccessor should be able to use both unmanaged and managed 
 connections.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-12652) Allow unmanaged connections in MetaTableAccessor

2014-12-09 Thread Enis Soztutar (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-12652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14239904#comment-14239904
 ] 

Enis Soztutar commented on HBASE-12652:
---

Skimmed the patch. Looks good. 

 Allow unmanaged connections in MetaTableAccessor
 

 Key: HBASE-12652
 URL: https://issues.apache.org/jira/browse/HBASE-12652
 Project: HBase
  Issue Type: Bug
Affects Versions: 1.0.0, 2.0.0
Reporter: Solomon Duskis
Assignee: Solomon Duskis
 Attachments: HBASE-12652.patch, HBASE-12652.patch, HBASE-12652B.patch


 Passing in an unmanaged connnection to MetaTableAccessor causes an exception. 
  MetaTableAccessor should be able to use both unmanaged and managed 
 connections.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-12662) region_status.rb is failing with NoMethodError

2014-12-09 Thread Hudson (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-12662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14239925#comment-14239925
 ] 

Hudson commented on HBASE-12662:


FAILURE: Integrated in HBase-TRUNK #5895 (See 
[https://builds.apache.org/job/HBase-TRUNK/5895/])
HBASE-12662 region_status.rb is failing with NoMethodError (Ashish Singhi) 
(tedyu: rev 0a22196468dc7baff5df39b73f286e1dd23d45e7)
* bin/region_status.rb


 region_status.rb is failing with NoMethodError
 --

 Key: HBASE-12662
 URL: https://issues.apache.org/jira/browse/HBASE-12662
 Project: HBase
  Issue Type: Bug
  Components: shell
Affects Versions: 2.0.0
Reporter: Ashish Singhi
Assignee: Ashish Singhi
 Fix For: 1.0.0, 2.0.0

 Attachments: HBASE-12662.patch


 {noformat}
 $/hbase-2.0.0-SNAPSHOT/bin hbase org.jruby.Main region_status.rb --table t
 2014-12-09 19:33:06,839 WARN  [main] util.NativeCodeLoader: Unable to load 
 native-hadoop library for your platform... using builtin-java classes where 
 applicable
 NoMethodError: undefined method `cache_blocks=' for 
 #Java::OrgApacheHadoopHbaseClient::Scan:0x1c7abd4c
   (root) at region_status.rb:93
 {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-12583) Allow creating reference files even the split row not lies in the storefile range if required

2014-12-09 Thread Hudson (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-12583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14239926#comment-14239926
 ] 

Hudson commented on HBASE-12583:


FAILURE: Integrated in HBase-TRUNK #5895 (See 
[https://builds.apache.org/job/HBase-TRUNK/5895/])
HBASE-12583 Allow creating reference files even the split row not lies in the 
storefile range if required - Addendum(Rajeshbabu) (rajeshbabu: rev 
53493ff5db40dd61eebbcb24a81ac57ff724274f)
* 
hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/RegionSplitPolicy.java


 Allow creating reference files even the split row not lies in the storefile 
 range if required
 -

 Key: HBASE-12583
 URL: https://issues.apache.org/jira/browse/HBASE-12583
 Project: HBase
  Issue Type: Improvement
Reporter: rajeshbabu
Assignee: rajeshbabu
  Labels: Phoenix
 Fix For: 1.0.0, 2.0.0, 0.98.9

 Attachments: HBASE-12583.patch, HBASE-12583_98.patch, 
 HBASE-12583_98_v2.patch, HBASE-12583_addendum.patch, 
 HBASE-12583_branch1.patch, HBASE-12583_branch1_v2.patch, 
 HBASE-12583_v2.patch, HBASE-12583_v3.patch


 Currently in HRegionFileSystem#splitStoreFile we are not creating reference 
 files if the split row not lies in the storefile range that means one of the 
 child region doesn't have any data.
 {code}
// Check whether the split row lies in the range of the store file
 // If it is outside the range, return directly.
 if (top) {
   //check if larger than last key.
   KeyValue splitKey = KeyValueUtil.createFirstOnRow(splitRow);
   byte[] lastKey = f.createReader().getLastKey();
   // If lastKey is null means storefile is empty.
   if (lastKey == null) return null;
   if (f.getReader().getComparator().compareFlatKey(splitKey.getBuffer(),
   splitKey.getKeyOffset(), splitKey.getKeyLength(), lastKey, 0, 
 lastKey.length)  0) {
 return null;
   }
 } else {
   //check if smaller than first key
   KeyValue splitKey = KeyValueUtil.createLastOnRow(splitRow);
   byte[] firstKey = f.createReader().getFirstKey();
   // If firstKey is null means storefile is empty.
   if (firstKey == null) return null;
   if (f.getReader().getComparator().compareFlatKey(splitKey.getBuffer(),
   splitKey.getKeyOffset(), splitKey.getKeyLength(), firstKey, 0, 
 firstKey.length)  0) {
 return null;
   }
 }
 {code}
 In some cases when split row should be compared with part of rowkey(in 
 composite rowkey) mainly for secondary index tables we need to create 
 reference files even when split row not lies in the storefile range so that 
 they can be rewritten to it's child regions by some custom half store file 
 reader which compare the part of row key with split row.
 The check of comparing split row with storefile range and returning directly 
 can be avoided by having special boolean attribute in table descriptor when 
 it set to true. Or else we can have coprocessor hooks so that in the hooks we 
 can create the references and bypass.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (HBASE-12664) TestDefaultLoadBalancer.testBalanceCluster fails in CachedDNSToSwitchMapping

2014-12-09 Thread Nick Dimiduk (JIRA)

 [ 
https://issues.apache.org/jira/browse/HBASE-12664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nick Dimiduk updated HBASE-12664:
-
Attachment: HBASE-12664-0.99-addendum.patch

Looks like this one mussed some imports on branch-1. Here's an addendum to fix 
it up.

 TestDefaultLoadBalancer.testBalanceCluster fails in CachedDNSToSwitchMapping
 

 Key: HBASE-12664
 URL: https://issues.apache.org/jira/browse/HBASE-12664
 Project: HBase
  Issue Type: Bug
  Components: test
Reporter: stack
Assignee: stack
Priority: Minor
 Fix For: 1.0.0, 2.0.0

 Attachments: 12664.txt, HBASE-12664-0.99-addendum.patch


 https://builds.apache.org/job/HBase-TRUNK/5893/testReport/org.apache.hadoop.hbase.master.balancer/TestDefaultLoadBalancer/testBalanceCluster/
 {code}
 java.lang.Exception: test timed out after 6 milliseconds
   at java.net.Inet4AddressImpl.lookupAllHostAddr(Native Method)
   at java.net.InetAddress$1.lookupAllHostAddr(InetAddress.java:894)
   at 
 java.net.InetAddress.getAddressesFromNameService(InetAddress.java:1286)
   at java.net.InetAddress.getAllByName0(InetAddress.java:1239)
   at java.net.InetAddress.getAllByName(InetAddress.java:1155)
   at java.net.InetAddress.getAllByName(InetAddress.java:1091)
   at java.net.InetAddress.getByName(InetAddress.java:1041)
   at org.apache.hadoop.net.NetUtils.normalizeHostName(NetUtils.java:561)
   at org.apache.hadoop.net.NetUtils.normalizeHostNames(NetUtils.java:578)
   at 
 org.apache.hadoop.net.CachedDNSToSwitchMapping.resolve(CachedDNSToSwitchMapping.java:109)
   at 
 org.apache.hadoop.hbase.master.RackManager.getRack(RackManager.java:66)
   at 
 org.apache.hadoop.hbase.master.balancer.BaseLoadBalancer$Cluster.init(BaseLoadBalancer.java:274)
   at 
 org.apache.hadoop.hbase.master.balancer.BaseLoadBalancer$Cluster.init(BaseLoadBalancer.java:152)
   at 
 org.apache.hadoop.hbase.master.balancer.SimpleLoadBalancer.balanceCluster(SimpleLoadBalancer.java:201)
   at 
 org.apache.hadoop.hbase.master.balancer.TestDefaultLoadBalancer.testBalanceCluster(TestDefaultLoadBalancer.java:119)
 {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Reopened] (HBASE-12664) TestDefaultLoadBalancer.testBalanceCluster fails in CachedDNSToSwitchMapping

2014-12-09 Thread Nick Dimiduk (JIRA)

 [ 
https://issues.apache.org/jira/browse/HBASE-12664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nick Dimiduk reopened HBASE-12664:
--

 TestDefaultLoadBalancer.testBalanceCluster fails in CachedDNSToSwitchMapping
 

 Key: HBASE-12664
 URL: https://issues.apache.org/jira/browse/HBASE-12664
 Project: HBase
  Issue Type: Bug
  Components: test
Reporter: stack
Assignee: stack
Priority: Minor
 Fix For: 1.0.0, 2.0.0

 Attachments: 12664.txt, HBASE-12664-0.99-addendum.patch


 https://builds.apache.org/job/HBase-TRUNK/5893/testReport/org.apache.hadoop.hbase.master.balancer/TestDefaultLoadBalancer/testBalanceCluster/
 {code}
 java.lang.Exception: test timed out after 6 milliseconds
   at java.net.Inet4AddressImpl.lookupAllHostAddr(Native Method)
   at java.net.InetAddress$1.lookupAllHostAddr(InetAddress.java:894)
   at 
 java.net.InetAddress.getAddressesFromNameService(InetAddress.java:1286)
   at java.net.InetAddress.getAllByName0(InetAddress.java:1239)
   at java.net.InetAddress.getAllByName(InetAddress.java:1155)
   at java.net.InetAddress.getAllByName(InetAddress.java:1091)
   at java.net.InetAddress.getByName(InetAddress.java:1041)
   at org.apache.hadoop.net.NetUtils.normalizeHostName(NetUtils.java:561)
   at org.apache.hadoop.net.NetUtils.normalizeHostNames(NetUtils.java:578)
   at 
 org.apache.hadoop.net.CachedDNSToSwitchMapping.resolve(CachedDNSToSwitchMapping.java:109)
   at 
 org.apache.hadoop.hbase.master.RackManager.getRack(RackManager.java:66)
   at 
 org.apache.hadoop.hbase.master.balancer.BaseLoadBalancer$Cluster.init(BaseLoadBalancer.java:274)
   at 
 org.apache.hadoop.hbase.master.balancer.BaseLoadBalancer$Cluster.init(BaseLoadBalancer.java:152)
   at 
 org.apache.hadoop.hbase.master.balancer.SimpleLoadBalancer.balanceCluster(SimpleLoadBalancer.java:201)
   at 
 org.apache.hadoop.hbase.master.balancer.TestDefaultLoadBalancer.testBalanceCluster(TestDefaultLoadBalancer.java:119)
 {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Resolved] (HBASE-12664) TestDefaultLoadBalancer.testBalanceCluster fails in CachedDNSToSwitchMapping

2014-12-09 Thread Nick Dimiduk (JIRA)

 [ 
https://issues.apache.org/jira/browse/HBASE-12664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nick Dimiduk resolved HBASE-12664.
--
Resolution: Fixed

pushed addendum to branch-1.

 TestDefaultLoadBalancer.testBalanceCluster fails in CachedDNSToSwitchMapping
 

 Key: HBASE-12664
 URL: https://issues.apache.org/jira/browse/HBASE-12664
 Project: HBase
  Issue Type: Bug
  Components: test
Reporter: stack
Assignee: stack
Priority: Minor
 Fix For: 1.0.0, 2.0.0

 Attachments: 12664.txt, HBASE-12664-0.99-addendum.patch


 https://builds.apache.org/job/HBase-TRUNK/5893/testReport/org.apache.hadoop.hbase.master.balancer/TestDefaultLoadBalancer/testBalanceCluster/
 {code}
 java.lang.Exception: test timed out after 6 milliseconds
   at java.net.Inet4AddressImpl.lookupAllHostAddr(Native Method)
   at java.net.InetAddress$1.lookupAllHostAddr(InetAddress.java:894)
   at 
 java.net.InetAddress.getAddressesFromNameService(InetAddress.java:1286)
   at java.net.InetAddress.getAllByName0(InetAddress.java:1239)
   at java.net.InetAddress.getAllByName(InetAddress.java:1155)
   at java.net.InetAddress.getAllByName(InetAddress.java:1091)
   at java.net.InetAddress.getByName(InetAddress.java:1041)
   at org.apache.hadoop.net.NetUtils.normalizeHostName(NetUtils.java:561)
   at org.apache.hadoop.net.NetUtils.normalizeHostNames(NetUtils.java:578)
   at 
 org.apache.hadoop.net.CachedDNSToSwitchMapping.resolve(CachedDNSToSwitchMapping.java:109)
   at 
 org.apache.hadoop.hbase.master.RackManager.getRack(RackManager.java:66)
   at 
 org.apache.hadoop.hbase.master.balancer.BaseLoadBalancer$Cluster.init(BaseLoadBalancer.java:274)
   at 
 org.apache.hadoop.hbase.master.balancer.BaseLoadBalancer$Cluster.init(BaseLoadBalancer.java:152)
   at 
 org.apache.hadoop.hbase.master.balancer.SimpleLoadBalancer.balanceCluster(SimpleLoadBalancer.java:201)
   at 
 org.apache.hadoop.hbase.master.balancer.TestDefaultLoadBalancer.testBalanceCluster(TestDefaultLoadBalancer.java:119)
 {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-12657) The Region is not being split and far exceeds the desired maximum size.

2014-12-09 Thread Vladimir Rodionov (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-12657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14239944#comment-14239944
 ] 

Vladimir Rodionov commented on HBASE-12657:
---

I checked trunk code and I think the issue is still there:

HStore:

{code}
  /**
   * @param candidates pre-filtrate
   * @return filtered subset
   * take upto maxFilesToCompact from the start
   */
  private ArrayListStoreFile removeExcessFiles(ArrayListStoreFile 
candidates,
  boolean isUserCompaction, boolean isMajorCompaction) {
int excess = candidates.size() - comConf.getMaxFilesToCompact();
if (excess  0) {
  if (isMajorCompaction  isUserCompaction) {
LOG.debug(Warning, compacting more than  + 
comConf.getMaxFilesToCompact() +
 files because of a user-requested major compaction);
  } else {
LOG.debug(Too many admissible files. Excluding  + excess
  +  files from compaction candidates);
candidates.subList(comConf.getMaxFilesToCompact(), 
candidates.size()).clear();
  }
}
return candidates;
  }
{code}

Even if this is a first after split compaction request we remove excess files 
from the list and this is the root cause of HBASE-12657 (imo). Reference files 
must be compacted immediately after split, all of them.

 The Region is not being split and far exceeds the desired maximum size.
 ---

 Key: HBASE-12657
 URL: https://issues.apache.org/jira/browse/HBASE-12657
 Project: HBase
  Issue Type: Bug
  Components: Compaction
Affects Versions: 0.98.8, 0.94.25, 0.99.2
Reporter: Vladimir Rodionov
Assignee: Vladimir Rodionov
 Fix For: 1.0.0, 2.0.0, 0.94.26, 0.98.9


 We are seeing this behavior when creating indexes in one of our environment.
 When an index is being created, most of the requests go into a single 
 region.  The amount of time to create an index seems to take longer than 
 usual and it can take days for the regions to compact and split after the 
 index is created.
 Here is a du of the HBase index table:
 {code}
 -bash-4.1$ sudo -su hdfs hadoop fs -du /hbase/43681
 705  /hbase/43681/.tableinfo.01
 0/hbase/43681/.tmp
 27981697293  /hbase/43681/0492e22092e21d35fca8e779b21ec797
 539687093/hbase/43681/832298c4e975fc47210feb6bac3d2f71
 560660531/hbase/43681/be9bdb3bdf9365afe5fe90db4247d82c
 7081938297   /hbase/43681/cd440e524f96fbe0719b2fe969848560
 6297860287   /hbase/43681/dc893a2d8daa08c689dc69e6bb2c5b50
 7189607722   /hbase/43681/ffbceaea5e2f142dbe6cd4cbeacc00e8
 ...
 {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Reopened] (HBASE-10554) Please delete old releases from mirroring system

2014-12-09 Thread Sebb (JIRA)

 [ 
https://issues.apache.org/jira/browse/HBASE-10554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sebb reopened HBASE-10554:
--

Please tidy up the release area. Again.

It looks to me like the following can be deleted:

hbase-0.94.23/
hbase-0.94.24/
hbase-0.96.2/
hbase-0.98.7/
hbase-0.99.0/
hbase-0.99.1/

The directory to_remove does not look as though it belongs there.
Remember that this directory is mirrored.

 Please delete old releases from mirroring system
 

 Key: HBASE-10554
 URL: https://issues.apache.org/jira/browse/HBASE-10554
 Project: HBase
  Issue Type: Task
Affects Versions: 0.96.0, 0.96.1, 0.94.14, 0.94.15
Reporter: Sebb

 To reduce the load on the ASF mirrors, projects are required to delete old 
 releases [1]
 Please can you remove all non-current releases?
 Thanks!
 [1] http://www.apache.org/dev/release.html#when-to-archive



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (HBASE-12652) Allow unmanaged connections in MetaTableAccessor

2014-12-09 Thread Nick Dimiduk (JIRA)

 [ 
https://issues.apache.org/jira/browse/HBASE-12652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nick Dimiduk updated HBASE-12652:
-
Resolution: Fixed
Status: Resolved  (was: Patch Available)

Thanks for the patch [~sduskis].

 Allow unmanaged connections in MetaTableAccessor
 

 Key: HBASE-12652
 URL: https://issues.apache.org/jira/browse/HBASE-12652
 Project: HBase
  Issue Type: Bug
Affects Versions: 1.0.0, 2.0.0
Reporter: Solomon Duskis
Assignee: Solomon Duskis
 Fix For: 1.0.0, 2.0.0

 Attachments: HBASE-12652.patch, HBASE-12652.patch, 
 HBASE-12652B.patch, HBASE-12652C-0.99.patch, HBASE-12652C.patch


 Passing in an unmanaged connnection to MetaTableAccessor causes an exception. 
  MetaTableAccessor should be able to use both unmanaged and managed 
 connections.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (HBASE-12652) Allow unmanaged connections in MetaTableAccessor

2014-12-09 Thread Nick Dimiduk (JIRA)

 [ 
https://issues.apache.org/jira/browse/HBASE-12652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nick Dimiduk updated HBASE-12652:
-
Attachment: HBASE-12652C.patch
HBASE-12652C-0.99.patch

Pushed to branch-1+. Attaching what was committed.

 Allow unmanaged connections in MetaTableAccessor
 

 Key: HBASE-12652
 URL: https://issues.apache.org/jira/browse/HBASE-12652
 Project: HBase
  Issue Type: Bug
Affects Versions: 1.0.0, 2.0.0
Reporter: Solomon Duskis
Assignee: Solomon Duskis
 Fix For: 1.0.0, 2.0.0

 Attachments: HBASE-12652.patch, HBASE-12652.patch, 
 HBASE-12652B.patch, HBASE-12652C-0.99.patch, HBASE-12652C.patch


 Passing in an unmanaged connnection to MetaTableAccessor causes an exception. 
  MetaTableAccessor should be able to use both unmanaged and managed 
 connections.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (HBASE-12652) Allow unmanaged connections in MetaTableAccessor

2014-12-09 Thread Nick Dimiduk (JIRA)

 [ 
https://issues.apache.org/jira/browse/HBASE-12652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nick Dimiduk updated HBASE-12652:
-
Fix Version/s: 2.0.0
   1.0.0

 Allow unmanaged connections in MetaTableAccessor
 

 Key: HBASE-12652
 URL: https://issues.apache.org/jira/browse/HBASE-12652
 Project: HBase
  Issue Type: Bug
Affects Versions: 1.0.0, 2.0.0
Reporter: Solomon Duskis
Assignee: Solomon Duskis
 Fix For: 1.0.0, 2.0.0

 Attachments: HBASE-12652.patch, HBASE-12652.patch, 
 HBASE-12652B.patch, HBASE-12652C-0.99.patch, HBASE-12652C.patch


 Passing in an unmanaged connnection to MetaTableAccessor causes an exception. 
  MetaTableAccessor should be able to use both unmanaged and managed 
 connections.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-10201) Port 'Make flush decisions per column family' to trunk

2014-12-09 Thread Jeffrey Zhong (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-10201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14239958#comment-14239958
 ] 

Jeffrey Zhong commented on HBASE-10201:
---

This is a nice feature. I scan through the patch and below are my comments:

1) There may be a correctness issue for same version(same row key  version) 
updates. Because you use following code as store file flush id, we could end up 
multiple hstore files with exact same flush seq id. While HBase resolve same 
version updates by store files' seqid(flush id). Therefore, we may end up with 
incorrect results.  This issue may only happen in 0.98 though.
{code}
+  long oldestUnflushedSeqId = wal
+  .getEarliestMemstoreSeqNum(encodedRegionName);
{code} 
In order to fix the issue, we should use current store's max flushed seq id as 
its real hstore seq id. While we need to change HRegion.lastFlushSeqId to use 
oldestUnflushedSeqId to report back Master otherwise we may have data loss 
issue.

2)  We have a feature where we force a flush by 
hbase.regionserver.optionalcacheflushinterval or 
hbase.regionserver.flush.per.changes while I didn't see you handle both cases 
in selectStoresToFlush() function. This may cause HRegion.shouldFlush() always 
return true and end up with small hstore files.

3) For region server recovery, we have an optimization by using lastFlushSeqId 
reported by region servers to skip writing edits into recovered.edits files. 
With this feature, we may unnecessarily write much more data into 
recovered.edits. This issue doesn't happen in log replay case.

4) Relating to your FlushMarker question, FulshMarker(or similar 
RegionEventWALEdit) are used for region replica feature and reasoning on 
region/store state. As you can see(in WALEdit class), those special events are 
using special column family METAFAMILY which doesn't exist for data regions. 
You should handle those events specially in getFamilyNames() otherwise they may 
affect your book keeping on oldest un-flushed seqid.  


 Port 'Make flush decisions per column family' to trunk
 --

 Key: HBASE-10201
 URL: https://issues.apache.org/jira/browse/HBASE-10201
 Project: HBase
  Issue Type: Improvement
  Components: wal
Reporter: Ted Yu
Assignee: zhangduo
Priority: Critical
 Fix For: 1.0.0, 2.0.0, 0.98.9

 Attachments: 3149-trunk-v1.txt, HBASE-10201-0.98.patch, 
 HBASE-10201-0.98_1.patch, HBASE-10201-0.98_2.patch, HBASE-10201-0.99.patch, 
 HBASE-10201.patch, HBASE-10201_1.patch, HBASE-10201_10.patch, 
 HBASE-10201_11.patch, HBASE-10201_12.patch, HBASE-10201_13.patch, 
 HBASE-10201_13.patch, HBASE-10201_14.patch, HBASE-10201_15.patch, 
 HBASE-10201_16.patch, HBASE-10201_17.patch, HBASE-10201_2.patch, 
 HBASE-10201_3.patch, HBASE-10201_4.patch, HBASE-10201_5.patch, 
 HBASE-10201_6.patch, HBASE-10201_7.patch, HBASE-10201_8.patch, 
 HBASE-10201_9.patch, compactions.png, count.png, io.png, memstore.png


 Currently the flush decision is made using the aggregate size of all column 
 families. When large and small column families co-exist, this causes many 
 small flushes of the smaller CF. We need to make per-CF flush decisions.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Resolved] (HBASE-10554) Please delete old releases from mirroring system

2014-12-09 Thread Andrew Purtell (JIRA)

 [ 
https://issues.apache.org/jira/browse/HBASE-10554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrew Purtell resolved HBASE-10554.

Resolution: Fixed

We have the latest release of each active release line and the one previous 
release available only. 

 Please delete old releases from mirroring system
 

 Key: HBASE-10554
 URL: https://issues.apache.org/jira/browse/HBASE-10554
 Project: HBase
  Issue Type: Task
Affects Versions: 0.96.0, 0.96.1, 0.94.14, 0.94.15
Reporter: Sebb

 To reduce the load on the ASF mirrors, projects are required to delete old 
 releases [1]
 Please can you remove all non-current releases?
 Thanks!
 [1] http://www.apache.org/dev/release.html#when-to-archive



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-12657) The Region is not being split and far exceeds the desired maximum size.

2014-12-09 Thread Vladimir Rodionov (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-12657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14239966#comment-14239966
 ] 

Vladimir Rodionov commented on HBASE-12657:
---

Sorry, that was RatioBasedCompactionPolicy.

 The Region is not being split and far exceeds the desired maximum size.
 ---

 Key: HBASE-12657
 URL: https://issues.apache.org/jira/browse/HBASE-12657
 Project: HBase
  Issue Type: Bug
  Components: Compaction
Affects Versions: 0.98.8, 0.94.25, 0.99.2
Reporter: Vladimir Rodionov
Assignee: Vladimir Rodionov
 Fix For: 1.0.0, 2.0.0, 0.94.26, 0.98.9


 We are seeing this behavior when creating indexes in one of our environment.
 When an index is being created, most of the requests go into a single 
 region.  The amount of time to create an index seems to take longer than 
 usual and it can take days for the regions to compact and split after the 
 index is created.
 Here is a du of the HBase index table:
 {code}
 -bash-4.1$ sudo -su hdfs hadoop fs -du /hbase/43681
 705  /hbase/43681/.tableinfo.01
 0/hbase/43681/.tmp
 27981697293  /hbase/43681/0492e22092e21d35fca8e779b21ec797
 539687093/hbase/43681/832298c4e975fc47210feb6bac3d2f71
 560660531/hbase/43681/be9bdb3bdf9365afe5fe90db4247d82c
 7081938297   /hbase/43681/cd440e524f96fbe0719b2fe969848560
 6297860287   /hbase/43681/dc893a2d8daa08c689dc69e6bb2c5b50
 7189607722   /hbase/43681/ffbceaea5e2f142dbe6cd4cbeacc00e8
 ...
 {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Comment Edited] (HBASE-10554) Please delete old releases from mirroring system

2014-12-09 Thread Andrew Purtell (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-10554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14239964#comment-14239964
 ] 

Andrew Purtell edited comment on HBASE-10554 at 12/9/14 8:06 PM:
-

We have four active release branches: 0.94, 0.96, 0.98, 0.99 (1.0 preview). For 
each active branch, we have the latest release and the one previous, in case 
users need to roll back. I think this is completely reasonable.


was (Author: apurtell):
We have the latest release of each active release line and the one previous 
release available only. 

 Please delete old releases from mirroring system
 

 Key: HBASE-10554
 URL: https://issues.apache.org/jira/browse/HBASE-10554
 Project: HBase
  Issue Type: Task
Affects Versions: 0.96.0, 0.96.1, 0.94.14, 0.94.15
Reporter: Sebb

 To reduce the load on the ASF mirrors, projects are required to delete old 
 releases [1]
 Please can you remove all non-current releases?
 Thanks!
 [1] http://www.apache.org/dev/release.html#when-to-archive



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


  1   2   3   >