date:20120827

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

Hadoop QA commented on HBASE-6477:
--

-1 overall. Here are the results of testing the latest attachment

http://issues.apache.org/jira/secure/attachment/12542584/HBASE-6477-addendum.patch
against trunk revision .

+1 @author. The patch does not contain any @author tags.

-1 tests included. 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.

+1 hadoop2.0. The patch compiles against the hadoop 2.0 profile.

-1 javadoc. The javadoc tool appears to have generated 94 warning messages.

-1 javac. The applied patch generated 5 javac compiler warnings (more than
the trunk's current 4 warnings).

-1 findbugs. The patch appears to introduce 13 new Findbugs (version
1.3.9) warnings.

+1 release audit. The applied patch does not increase the total number of
release audit warnings.

-1 core tests. The patch failed these unit tests:
org.apache.hadoop.hbase.regionserver.TestStore

Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/2699//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/2699//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/2699//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/2699//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/2699//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/2699//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/2699//console

This message is automatically generated.

Use PB filter definitions in RPC

Key: HBASE-6477
URL: https://issues.apache.org/jira/browse/HBASE-6477
Project: HBase
Issue Type: Task
Components: ipc, migration
Reporter: Gregory Chanan
Assignee: Gregory Chanan
Fix For: 0.96.0

Attachments: HBASE-6477-addendum.patch, HBASE-6477-nonrb.patch,
HBASE-6477-nonrb-v3.patch, HBASE-6477-nonrb-v4.patch

Use the filters introduced in HBASE-6454 in the rpc so they are extensible

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Assigned] (HBASE-6642) disable_all '*' is not performing disable operation.


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

rajeshbabu reassigned HBASE-6642:
-

Assignee: rajeshbabu

 disable_all '*' is not performing disable operation.
 

 Key: HBASE-6642
 URL: https://issues.apache.org/jira/browse/HBASE-6642
 Project: HBase
  Issue Type: Bug
  Components: shell
Reporter: Y. SREENIVASULU REDDY
Assignee: rajeshbabu

 created few tables. then performing disable_all operation in shell prompt.
 but it is not performing operation successfully.
 {noformat}
 hbase(main):043:0 disable_all '*'
 table12
 zk0113
 zk0114
 Disable the above 3 tables (y/n)?
 y/
 3 tables successfully disabled
 just it is showing the message but operation is not success.
 but the following way only performing successfully
 hbase(main):043:0 disable_all '*.*'
 table12
 zk0113
 zk0114
 Disable the above 3 tables (y/n)?
 y
 3 tables successfully disabled
 {noformat}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HBASE-6642) disable_all '*' is not performing disable operation.


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

rajeshbabu commented on HBASE-6642:
---

This problem is because below code in disable_all.rb
{code}
regex = /^#{regex}$/ unless regex.is_a?(Regexp)
list = admin.list.grep(regex)
count = list.size

{code}
in case of * regex will become ^*$ which is valid in Ruby and 
admin.list.grep(regex) gives all available tables.
But same expression(^*$) in Java returns empty list.
{code}
failed = admin.disable_all(regex)
puts #{count - failed.size} tables successfully disabled
puts #{failed.size} tables not disabled due to an exception: 
#{failed.join ','} unless failed.size == 0
{code}
Even the number of tables to disabled is zero, output is #{count - 
failed.size} tables successfully disabled.
This is applicable for enable_all and drop_all also.

 disable_all '*' is not performing disable operation.
 

 Key: HBASE-6642
 URL: https://issues.apache.org/jira/browse/HBASE-6642
 Project: HBase
  Issue Type: Bug
  Components: shell
Reporter: Y. SREENIVASULU REDDY
Assignee: rajeshbabu

 created few tables. then performing disable_all operation in shell prompt.
 but it is not performing operation successfully.
 {noformat}
 hbase(main):043:0 disable_all '*'
 table12
 zk0113
 zk0114
 Disable the above 3 tables (y/n)?
 y/
 3 tables successfully disabled
 just it is showing the message but operation is not success.
 but the following way only performing successfully
 hbase(main):043:0 disable_all '*.*'
 table12
 zk0113
 zk0114
 Disable the above 3 tables (y/n)?
 y
 3 tables successfully disabled
 {noformat}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HBASE-6642) disable_all '*' is not performing disable operation.


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

rajeshbabu commented on HBASE-6642:
---

Small change in above comment:
Even the number of disabled tables is zero, We are priting #{count} tables 
successfully disabled.
Here count is total number of available tables.


 disable_all '*' is not performing disable operation.
 

 Key: HBASE-6642
 URL: https://issues.apache.org/jira/browse/HBASE-6642
 Project: HBase
  Issue Type: Bug
  Components: shell
Reporter: Y. SREENIVASULU REDDY
Assignee: rajeshbabu

 created few tables. then performing disable_all operation in shell prompt.
 but it is not performing operation successfully.
 {noformat}
 hbase(main):043:0 disable_all '*'
 table12
 zk0113
 zk0114
 Disable the above 3 tables (y/n)?
 y/
 3 tables successfully disabled
 just it is showing the message but operation is not success.
 but the following way only performing successfully
 hbase(main):043:0 disable_all '*.*'
 table12
 zk0113
 zk0114
 Disable the above 3 tables (y/n)?
 y
 3 tables successfully disabled
 {noformat}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HBASE-6669) Add BigDecimalColumnInterpreter for doing aggregations using AggregationClient

2012-08-27 Thread Himanshu Vashishtha (JIRA)


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

Himanshu Vashishtha commented on HBASE-6669:


Please upload the patch :)

 Add BigDecimalColumnInterpreter for doing aggregations using AggregationClient
 --

 Key: HBASE-6669
 URL: https://issues.apache.org/jira/browse/HBASE-6669
 Project: HBase
  Issue Type: New Feature
  Components: client, coprocessors
Reporter: Anil Gupta
Priority: Minor
  Labels: client, coprocessors

 I recently created a Class for doing aggregations(sum,min,max,std) on values 
 stored as BigDecimal in HBase. I would like to commit the 
 BigDecimalColumnInterpreter into HBase. In my opinion this class can be used 
 by a wide variety of users. Please let me know if its not appropriate to add 
 this class in HBase.
 Thanks,
 Anil Gupta
 Software Engineer II, Intuit, Inc 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (HBASE-6659) Port HBASE-6508 Filter out edits at log split time


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

Ted Yu updated HBASE-6659:
--

Attachment: 6508-v4.txt

Removed some white spaces.
Plan to integrate this evening if there is no objection.

 Port HBASE-6508 Filter out edits at log split time
 --

 Key: HBASE-6659
 URL: https://issues.apache.org/jira/browse/HBASE-6659
 Project: HBase
  Issue Type: Bug
Reporter: Zhihong Ted Yu
Assignee: Zhihong Ted Yu
 Fix For: 0.96.0

 Attachments: 6508-v2.txt, 6508-v3.txt, 6508-v4.txt, 6508-v4.txt


 HBASE-6508 is for 0.89-fb branch.
 This JIRA ports the feature to trunk.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HBASE-6080) site.xml - adding ReviewBoard to main page left-hand nav

2012-08-27 Thread Michael Drzal (JIRA)


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

Michael Drzal commented on HBASE-6080:
--

[~dmeil] looking over old bugs, and I saw this one.  It looks like the link 
already exists.  Any reason this can't be closed out?

 site.xml - adding ReviewBoard to main page left-hand nav
 

 Key: HBASE-6080
 URL: https://issues.apache.org/jira/browse/HBASE-6080
 Project: HBase
  Issue Type: Improvement
Reporter: Doug Meil
Assignee: Doug Meil
Priority: Trivial
 Attachments: src_hbase_6080.patch


 By request, adding ReviewBoard to left-hand nav on website

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Assigned] (HBASE-6401) HBase may lose edits after a crash if used with HDFS 1.0.3 or older

2012-08-27 Thread nkeywal (JIRA)

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

nkeywal reassigned HBASE-6401:
--

Assignee: nkeywal

HBase may lose edits after a crash if used with HDFS 1.0.3 or older
---

Key: HBASE-6401
URL: https://issues.apache.org/jira/browse/HBASE-6401
Project: HBase
Issue Type: Bug
Components: regionserver
Affects Versions: 0.96.0
Environment: all
Reporter: nkeywal
Assignee: nkeywal
Priority: Critical
Attachments: TestReadAppendWithDeadDN.java

This comes from a hdfs bug, fixed in some hdfs versions. I haven't found the
hdfs jira for this.
Context: HBase Write Ahead Log features. This is using hdfs append. If the
node crashes, the file that was written is read by other processes to replay
the action.
- So we have in hdfs one (dead) process writing with another process reading.
- But, despite the call to syncFs, we don't always see the data when we have
a dead node. It seems to be because the call in DFSClient#updateBlockInfo
ignores the ipc errors and set the length to 0.
- So we may miss all the writes to the last block if we try to connect to the
dead DN.
hdfs 1.0.3, branch-1 or branch-1-win: we have the issue
http://svn.apache.org/viewvc/hadoop/common/branches/branch-1/src/hdfs/org/apache/hadoop/hdfs/DFSClient.java?revision=1359853view=markup
hdfs branch-2 or trunk: we should not have the issue (but not tested)
http://svn.apache.org/viewvc/hadoop/common/branches/branch-2/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/DFSInputStream.java?view=markup
The attached test will fail ~50 of the time.

[jira] [Commented] (HBASE-6659) Port HBASE-6508 Filter out edits at log split time

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

Hadoop QA commented on HBASE-6659:
--

-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12542608/6508-v4.txt
against trunk revision .

+1 @author. The patch does not contain any @author tags.

+1 tests included. The patch appears to include 12 new or modified tests.

+1 hadoop2.0. The patch compiles against the hadoop 2.0 profile.

-1 javadoc. The javadoc tool appears to have generated 92 warning messages.

-1 javac. The applied patch generated 5 javac compiler warnings (more than
the trunk's current 4 warnings).

-1 findbugs. The patch appears to introduce 13 new Findbugs (version
1.3.9) warnings.

+1 release audit. The applied patch does not increase the total number of
release audit warnings.

-1 core tests. The patch failed these unit tests:

Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/2700//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/2700//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/2700//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/2700//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/2700//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/2700//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/2700//console

This message is automatically generated.

Port HBASE-6508 Filter out edits at log split time
--

Key: HBASE-6659
URL: https://issues.apache.org/jira/browse/HBASE-6659
Project: HBase
Issue Type: Bug
Reporter: Zhihong Ted Yu
Assignee: Zhihong Ted Yu
Fix For: 0.96.0

Attachments: 6508-v2.txt, 6508-v3.txt, 6508-v4.txt, 6508-v4.txt

HBASE-6508 is for 0.89-fb branch.
This JIRA ports the feature to trunk.

[jira] [Updated] (HBASE-6477) Use PB filter definitions in RPC


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

Ted Yu updated HBASE-6477:
--

Attachment: 6477-addendum.patch

Same addendum from Gregory.

 Use PB filter definitions in RPC
 

 Key: HBASE-6477
 URL: https://issues.apache.org/jira/browse/HBASE-6477
 Project: HBase
  Issue Type: Task
  Components: ipc, migration
Reporter: Gregory Chanan
Assignee: Gregory Chanan
 Fix For: 0.96.0

 Attachments: 6477-addendum.patch, HBASE-6477-addendum.patch, 
 HBASE-6477-nonrb.patch, HBASE-6477-nonrb-v3.patch, HBASE-6477-nonrb-v4.patch


 Use the filters introduced in HBASE-6454 in the rpc so they are extensible

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HBASE-4907) Port 89-fb changes to trunk


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

Ted Yu commented on HBASE-4907:
---

Out of the 14 tasks, only two have been completed.
It would be nice to prioritize the remaining 12 tasks so that we can prepare 
for 0.96 RC0

 Port 89-fb changes to trunk
 ---

 Key: HBASE-4907
 URL: https://issues.apache.org/jira/browse/HBASE-4907
 Project: HBase
  Issue Type: Improvement
  Components: client, regionserver
Reporter: Nicolas Spiegelberg
Assignee: Nicolas Spiegelberg
Priority: Blocker
 Fix For: 0.96.0


 A super task to track the progress of porting 89-fb functionality  fixes to 
 trunk.  Note that these tasks are focused on RegionServer functionality.  
 89-specific master functionality doesn't have a time frame for porting.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (HBASE-6316) Confirm can upgrade to 0.96 from 0.94 by just stopping and restarting


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

Ted Yu updated HBASE-6316:
--

Fix Version/s: 0.96.0
  Summary: Confirm can upgrade to 0.96 from 0.94 by just stopping and 
restarting  (was: Confirm can upgrade from 0.96 from 0.94 by just stopping and 
restarting)

 Confirm can upgrade to 0.96 from 0.94 by just stopping and restarting
 -

 Key: HBASE-6316
 URL: https://issues.apache.org/jira/browse/HBASE-6316
 Project: HBase
  Issue Type: Bug
Reporter: stack
Priority: Blocker
 Fix For: 0.96.0


 Over in HBASE-6294, LarsH says you have to currently clear zk to get a 0.96 
 to start over data written by a 0.94.  Need to fix it so don't have to do 
 this -- that zk state left over gets auto-migrated.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HBASE-6477) Use PB filter definitions in RPC


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

Ted Yu commented on HBASE-6477:
---

I ran addendum through test suite and TestStore passed:
{code}
Running org.apache.hadoop.hbase.regionserver.TestStore
Tests run: 12, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 12.304 sec
...
Running org.apache.hadoop.hbase.coprocessor.TestAggregateProtocol
Tests run: 45, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 20.151 sec
{code}
Recommend integrating the addendum and leave the remaining issues (w.r.t. 
removing HbaseObjectWritable.writeObject call in ProtobufUtil.toParameter) to 
other JIRA.

 Use PB filter definitions in RPC
 

 Key: HBASE-6477
 URL: https://issues.apache.org/jira/browse/HBASE-6477
 Project: HBase
  Issue Type: Task
  Components: ipc, migration
Reporter: Gregory Chanan
Assignee: Gregory Chanan
 Fix For: 0.96.0

 Attachments: 6477-addendum.patch, HBASE-6477-addendum.patch, 
 HBASE-6477-nonrb.patch, HBASE-6477-nonrb-v3.patch, HBASE-6477-nonrb-v4.patch


 Use the filters introduced in HBASE-6454 in the rpc so they are extensible

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (HBASE-6670) Untangle mixture of protobuf and Writable reference / usage

Ted Yu created HBASE-6670:
-

 Summary: Untangle mixture of protobuf and Writable reference / 
usage
 Key: HBASE-6670
 URL: https://issues.apache.org/jira/browse/HBASE-6670
 Project: HBase
  Issue Type: Bug
Reporter: Ted Yu
 Fix For: 0.96.0


Currently HbaseObjectWritable uses ProtobufUtil to perform serialization of 
Scan objects, ProtobufUtil.toParameter() calls 
HbaseObjectWritable.writeObject().

We should untangle such mixture and ultimately remove HbaseObjectWritable

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HBASE-6291) Don't retry increments on an invalid cell


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

Jean-Daniel Cryans commented on HBASE-6291:
---

Yes +1

 Don't retry increments on an invalid cell
 -

 Key: HBASE-6291
 URL: https://issues.apache.org/jira/browse/HBASE-6291
 Project: HBase
  Issue Type: Improvement
Affects Versions: 0.90.6, 0.92.1, 0.94.0
Reporter: Jean-Daniel Cryans
Assignee: Lars Hofhansl
 Fix For: 0.92.2, 0.94.2, 0.90.8

 Attachments: 6291-0.96.txt


 This says it all:
 {noformat}
 ERROR: org.apache.hadoop.hbase.client.RetriesExhaustedException: Failed after 
 attempts=7, exceptions:
 Thu Jun 28 18:34:44 UTC 2012, 
 org.apache.hadoop.hbase.client.HTable$8@4eabaf8c, java.io.IOException: 
 java.io.IOException: Attempted to increment field that isn't 64 bits wide
 {noformat}
 {{HRegion}} should be modified here to send a DoNotRetryIOException:
 {code}
 if (wrongLength) {
   throw new DoNotRetryIOException(
 Attempted to increment field that isn't 64 bits wide);
 }
 {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HBASE-6661) Mark single parameter HTable constructors as deprecated in 0.90 and 0.92


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

Jean-Daniel Cryans commented on HBASE-6661:
---

+1, it shouldn't be much different for 0.90?

 Mark single parameter HTable constructors as deprecated in 0.90 and 0.92
 

 Key: HBASE-6661
 URL: https://issues.apache.org/jira/browse/HBASE-6661
 Project: HBase
  Issue Type: Improvement
Reporter: Jean-Daniel Cryans
Assignee: Zhihong Ted Yu
Priority: Critical
 Fix For: 0.90.7, 0.92.2

 Attachments: 6661.92


 HBASE-4746 removed 2 constructors from HTable for 0.94.0 but we never marked 
 them as deprecated. It's not too late to fix it in 0.90 and 0.92 point 
 releases.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (HBASE-5826) Improve sync of HLog edits


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

Ted Yu updated HBASE-5826:
--

Attachment: 5826-v5.txt

Rebased against trunk.

 Improve sync of HLog edits
 --

 Key: HBASE-5826
 URL: https://issues.apache.org/jira/browse/HBASE-5826
 Project: HBase
  Issue Type: Improvement
Reporter: Zhihong Ted Yu
Assignee: Todd Lipcon
 Fix For: 0.96.0

 Attachments: 5826.txt, 5826-v2.txt, 5826-v3.txt, 5826-v4.txt, 
 5826-v5.txt


 HBASE-5782 solved the correctness issue for the sync of HLog edits.
 Todd provided a patch that would achieve higher throughput.
 This JIRA is a continuation of Todd's work submitted there.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HBASE-6477) Use PB filter definitions in RPC

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

Hadoop QA commented on HBASE-6477:
--

-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12542615/6477-addendum.patch
against trunk revision .

+1 @author. The patch does not contain any @author tags.

+1 hadoop2.0. The patch compiles against the hadoop 2.0 profile.

-1 javadoc. The javadoc tool appears to have generated 94 warning messages.

-1 javac. The applied patch generated 5 javac compiler warnings (more than
the trunk's current 4 warnings).

-1 findbugs. The patch appears to introduce 13 new Findbugs (version
1.3.9) warnings.

+1 release audit. The applied patch does not increase the total number of
release audit warnings.

+1 core tests. The patch passed unit tests in .

Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/2701//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/2701//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/2701//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/2701//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/2701//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/2701//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/2701//console

This message is automatically generated.

Use PB filter definitions in RPC

Key: HBASE-6477
URL: https://issues.apache.org/jira/browse/HBASE-6477
Project: HBase
Issue Type: Task
Components: ipc, migration
Reporter: Gregory Chanan
Assignee: Gregory Chanan
Fix For: 0.96.0

Attachments: 6477-addendum.patch, HBASE-6477-addendum.patch,
HBASE-6477-nonrb.patch, HBASE-6477-nonrb-v3.patch, HBASE-6477-nonrb-v4.patch

Use the filters introduced in HBASE-6454 in the rpc so they are extensible

[jira] [Commented] (HBASE-6661) Mark single parameter HTable constructors as deprecated in 0.90 and 0.92


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

Ted Yu commented on HBASE-6661:
---

Integrated to 0.90 and 0.92

Thanks for the review, J-D.

Same patch applies cleanly to 0.90 branch.

 Mark single parameter HTable constructors as deprecated in 0.90 and 0.92
 

 Key: HBASE-6661
 URL: https://issues.apache.org/jira/browse/HBASE-6661
 Project: HBase
  Issue Type: Improvement
Reporter: Jean-Daniel Cryans
Assignee: Zhihong Ted Yu
Priority: Critical
 Fix For: 0.90.7, 0.92.2

 Attachments: 6661.92


 HBASE-4746 removed 2 constructors from HTable for 0.94.0 but we never marked 
 them as deprecated. It's not too late to fix it in 0.90 and 0.92 point 
 releases.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HBASE-6643) Accept encoded region name in compacting/spliting region from shell

2012-08-27 Thread Jimmy Xiang (JIRA)


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

Jimmy Xiang commented on HBASE-6643:


@Stack, in patch 2, I removed the double meta scan (one for isRegionName, the 
other to get ServerName in case a region name).
I also moved the change from MetaReader to HBaseAdmin to reduce the scope of 
impact.  Could you please take a loo?

 Accept encoded region name in compacting/spliting region from shell
 ---

 Key: HBASE-6643
 URL: https://issues.apache.org/jira/browse/HBASE-6643
 Project: HBase
  Issue Type: Improvement
  Components: shell
Reporter: Jimmy Xiang
Assignee: Jimmy Xiang
 Attachments: trunk-6643.patch, trunk-6643_v2.patch


 Sometimes, the region name has binary characters. When compacting/splitting 
 it from shell, the region name is not recognized.  If we can support encoded 
 region name, it will make things easier.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (HBASE-5945) Reduce buffer copies in IPC server response path


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

Ted Yu updated HBASE-5945:
--

Priority: Blocker  (was: Critical)

 Reduce buffer copies in IPC server response path
 

 Key: HBASE-5945
 URL: https://issues.apache.org/jira/browse/HBASE-5945
 Project: HBase
  Issue Type: Improvement
  Components: ipc
Affects Versions: 0.96.0
Reporter: Todd Lipcon
Assignee: Todd Lipcon
Priority: Blocker
 Attachments: buffer-copies.txt, even-fewer-copies.txt, hbase-5495.txt


 The new PB code is sloppy with buffers and makes several needless copies. 
 This increases GC time a lot. A few simple changes can cut this back down.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HBASE-6661) Mark single parameter HTable constructors as deprecated in 0.90 and 0.92


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

Hudson commented on HBASE-6661:
---

Integrated in HBase-0.92 #534 (See 
[https://builds.apache.org/job/HBase-0.92/534/])
HBASE-6661 Mark single parameter HTable constructors as deprecated in 0.90 
and 0.92 (Revision 1377743)

 Result = FAILURE
Tedyu : 
Files : 
* /hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/client/HTable.java


 Mark single parameter HTable constructors as deprecated in 0.90 and 0.92
 

 Key: HBASE-6661
 URL: https://issues.apache.org/jira/browse/HBASE-6661
 Project: HBase
  Issue Type: Improvement
Reporter: Jean-Daniel Cryans
Assignee: Zhihong Ted Yu
Priority: Critical
 Fix For: 0.90.7, 0.92.2

 Attachments: 6661.92


 HBASE-4746 removed 2 constructors from HTable for 0.94.0 but we never marked 
 them as deprecated. It's not too late to fix it in 0.90 and 0.92 point 
 releases.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (HBASE-6586) Quarantine Corrupted HFiles


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

Jonathan Hsieh updated HBASE-6586:
--

Status: Open  (was: Patch Available)

 Quarantine Corrupted HFiles
 ---

 Key: HBASE-6586
 URL: https://issues.apache.org/jira/browse/HBASE-6586
 Project: HBase
  Issue Type: Improvement
Reporter: Jonathan Hsieh
Assignee: Jonathan Hsieh
 Attachments: 0001-hbase-6568-hbck-quarantine-v6.patch, 
 hbase-6586-92-v3.patch, hbase-6586-92-v8.patch, hbase-6586-94-v3.patch, 
 hbase-6586-94-v8.patch, hbase-6586.patch, hbase-6586-trunk-v3.patch, 
 hbase-6586-trunk-v4.patch, hbase-6586-trunk-v5.patch, 
 hbase-6586-trunk-v6.patch, hbase-6586-trunk-v7.patch, 
 hbase-6586-trunk-v8.patch


 We've encountered a few upgrades from 0.90 hbases + 20.2/1.x hdfs to 0.92 
 hbases + hdfs 2.x that get stuck.  I haven't been able to duplicate the 
 problem in my dev environment but we suspect this may be related to 
 HDFS-3731.  On the HBase side, it seems reasonable to quarantine what are 
 most likely truncated hfiles, so that can could later be recovered.
 Here's an example of the exception we've encountered:
 {code}
 2012-07-18 05:55:01,152 ERROR handler.OpenRegionHandler 
 (OpenRegionHandler.java:openRegion(346)) - Failed open of 
 region=user_mappings,080112102AA76EF98197605D341B9E6C5824D2BC|1001,1317824890618.eaed0e7abc6d27d28ff0e5a9b49c4c
 0d. 
 java.io.IOException: java.lang.IllegalArgumentException: Invalid HFile 
 version: 842220600 (expected to be between 1 and 2) 
 at 
 org.apache.hadoop.hbase.io.hfile.FixedFileTrailer.readFromStream(FixedFileTrailer.java:306)
  
 at org.apache.hadoop.hbase.io.hfile.HFile.pickReaderVersion(HFile.java:371) 
 at org.apache.hadoop.hbase.io.hfile.HFile.createReader(HFile.java:387) 
 at 
 org.apache.hadoop.hbase.regionserver.StoreFile$Reader.init(StoreFile.java:1026)
  
 at org.apache.hadoop.hbase.regionserver.StoreFile.open(StoreFile.java:485) 
 at 
 org.apache.hadoop.hbase.regionserver.StoreFile.createReader(StoreFile.java:566)
  
 at org.apache.hadoop.hbase.regionserver.Store.loadStoreFiles(Store.java:286) 
 at org.apache.hadoop.hbase.regionserver.Store.init(Store.java:223) 
 at 
 org.apache.hadoop.hbase.regionserver.HRegion.instantiateHStore(HRegion.java:2534)
  
 at org.apache.hadoop.hbase.regionserver.HRegion.initialize(HRegion.java:454) 
 at 
 org.apache.hadoop.hbase.regionserver.HRegion.openHRegion(HRegion.java:3282) 
 at 
 org.apache.hadoop.hbase.regionserver.HRegion.openHRegion(HRegion.java:3230) 
 at 
 org.apache.hadoop.hbase.regionserver.handler.OpenRegionHandler.openRegion(OpenRegionHandler.java:331)
 at 
 org.apache.hadoop.hbase.regionserver.handler.OpenRegionHandler.process(OpenRegionHandler.java:107)
 at org.apache.hadoop.hbase.executor.EventHandler.run(EventHandler.java:169) 
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
  
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
  
 at java.lang.Thread.run(Thread.java:619) 
 Caused by: java.lang.IllegalArgumentException: Invalid HFile version: 
 842220600 (expected to be between 1 and 2) 
 at org.apache.hadoop.hbase.io.hfile.HFile.checkFormatVersion(HFile.java:515) 
 at 
 org.apache.hadoop.hbase.io.hfile.FixedFileTrailer.readFromStream(FixedFileTrailer.java:303)
  
 ... 17 more
 {code}
 Specifically -- the FixedFileTrailer are incorrect, and seemingly missing.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (HBASE-6586) Quarantine Corrupted HFiles


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

Jonathan Hsieh updated HBASE-6586:
--

Attachment: hbase-6586-trunk-v8.patch

Previous run didn't pass but when tested locally it passed.  Trying again.

 Quarantine Corrupted HFiles
 ---

 Key: HBASE-6586
 URL: https://issues.apache.org/jira/browse/HBASE-6586
 Project: HBase
  Issue Type: Improvement
Reporter: Jonathan Hsieh
Assignee: Jonathan Hsieh
 Attachments: 0001-hbase-6568-hbck-quarantine-v6.patch, 
 hbase-6586-92-v3.patch, hbase-6586-92-v8.patch, hbase-6586-94-v3.patch, 
 hbase-6586-94-v8.patch, hbase-6586.patch, hbase-6586-trunk-v3.patch, 
 hbase-6586-trunk-v4.patch, hbase-6586-trunk-v5.patch, 
 hbase-6586-trunk-v6.patch, hbase-6586-trunk-v7.patch, 
 hbase-6586-trunk-v8.patch


 We've encountered a few upgrades from 0.90 hbases + 20.2/1.x hdfs to 0.92 
 hbases + hdfs 2.x that get stuck.  I haven't been able to duplicate the 
 problem in my dev environment but we suspect this may be related to 
 HDFS-3731.  On the HBase side, it seems reasonable to quarantine what are 
 most likely truncated hfiles, so that can could later be recovered.
 Here's an example of the exception we've encountered:
 {code}
 2012-07-18 05:55:01,152 ERROR handler.OpenRegionHandler 
 (OpenRegionHandler.java:openRegion(346)) - Failed open of 
 region=user_mappings,080112102AA76EF98197605D341B9E6C5824D2BC|1001,1317824890618.eaed0e7abc6d27d28ff0e5a9b49c4c
 0d. 
 java.io.IOException: java.lang.IllegalArgumentException: Invalid HFile 
 version: 842220600 (expected to be between 1 and 2) 
 at 
 org.apache.hadoop.hbase.io.hfile.FixedFileTrailer.readFromStream(FixedFileTrailer.java:306)
  
 at org.apache.hadoop.hbase.io.hfile.HFile.pickReaderVersion(HFile.java:371) 
 at org.apache.hadoop.hbase.io.hfile.HFile.createReader(HFile.java:387) 
 at 
 org.apache.hadoop.hbase.regionserver.StoreFile$Reader.init(StoreFile.java:1026)
  
 at org.apache.hadoop.hbase.regionserver.StoreFile.open(StoreFile.java:485) 
 at 
 org.apache.hadoop.hbase.regionserver.StoreFile.createReader(StoreFile.java:566)
  
 at org.apache.hadoop.hbase.regionserver.Store.loadStoreFiles(Store.java:286) 
 at org.apache.hadoop.hbase.regionserver.Store.init(Store.java:223) 
 at 
 org.apache.hadoop.hbase.regionserver.HRegion.instantiateHStore(HRegion.java:2534)
  
 at org.apache.hadoop.hbase.regionserver.HRegion.initialize(HRegion.java:454) 
 at 
 org.apache.hadoop.hbase.regionserver.HRegion.openHRegion(HRegion.java:3282) 
 at 
 org.apache.hadoop.hbase.regionserver.HRegion.openHRegion(HRegion.java:3230) 
 at 
 org.apache.hadoop.hbase.regionserver.handler.OpenRegionHandler.openRegion(OpenRegionHandler.java:331)
 at 
 org.apache.hadoop.hbase.regionserver.handler.OpenRegionHandler.process(OpenRegionHandler.java:107)
 at org.apache.hadoop.hbase.executor.EventHandler.run(EventHandler.java:169) 
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
  
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
  
 at java.lang.Thread.run(Thread.java:619) 
 Caused by: java.lang.IllegalArgumentException: Invalid HFile version: 
 842220600 (expected to be between 1 and 2) 
 at org.apache.hadoop.hbase.io.hfile.HFile.checkFormatVersion(HFile.java:515) 
 at 
 org.apache.hadoop.hbase.io.hfile.FixedFileTrailer.readFromStream(FixedFileTrailer.java:303)
  
 ... 17 more
 {code}
 Specifically -- the FixedFileTrailer are incorrect, and seemingly missing.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (HBASE-6586) Quarantine Corrupted HFiles


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

Jonathan Hsieh updated HBASE-6586:
--

Status: Patch Available  (was: Open)

 Quarantine Corrupted HFiles
 ---

 Key: HBASE-6586
 URL: https://issues.apache.org/jira/browse/HBASE-6586
 Project: HBase
  Issue Type: Improvement
Reporter: Jonathan Hsieh
Assignee: Jonathan Hsieh
 Attachments: 0001-hbase-6568-hbck-quarantine-v6.patch, 
 hbase-6586-92-v3.patch, hbase-6586-92-v8.patch, hbase-6586-94-v3.patch, 
 hbase-6586-94-v8.patch, hbase-6586.patch, hbase-6586-trunk-v3.patch, 
 hbase-6586-trunk-v4.patch, hbase-6586-trunk-v5.patch, 
 hbase-6586-trunk-v6.patch, hbase-6586-trunk-v7.patch, 
 hbase-6586-trunk-v8.patch


 We've encountered a few upgrades from 0.90 hbases + 20.2/1.x hdfs to 0.92 
 hbases + hdfs 2.x that get stuck.  I haven't been able to duplicate the 
 problem in my dev environment but we suspect this may be related to 
 HDFS-3731.  On the HBase side, it seems reasonable to quarantine what are 
 most likely truncated hfiles, so that can could later be recovered.
 Here's an example of the exception we've encountered:
 {code}
 2012-07-18 05:55:01,152 ERROR handler.OpenRegionHandler 
 (OpenRegionHandler.java:openRegion(346)) - Failed open of 
 region=user_mappings,080112102AA76EF98197605D341B9E6C5824D2BC|1001,1317824890618.eaed0e7abc6d27d28ff0e5a9b49c4c
 0d. 
 java.io.IOException: java.lang.IllegalArgumentException: Invalid HFile 
 version: 842220600 (expected to be between 1 and 2) 
 at 
 org.apache.hadoop.hbase.io.hfile.FixedFileTrailer.readFromStream(FixedFileTrailer.java:306)
  
 at org.apache.hadoop.hbase.io.hfile.HFile.pickReaderVersion(HFile.java:371) 
 at org.apache.hadoop.hbase.io.hfile.HFile.createReader(HFile.java:387) 
 at 
 org.apache.hadoop.hbase.regionserver.StoreFile$Reader.init(StoreFile.java:1026)
  
 at org.apache.hadoop.hbase.regionserver.StoreFile.open(StoreFile.java:485) 
 at 
 org.apache.hadoop.hbase.regionserver.StoreFile.createReader(StoreFile.java:566)
  
 at org.apache.hadoop.hbase.regionserver.Store.loadStoreFiles(Store.java:286) 
 at org.apache.hadoop.hbase.regionserver.Store.init(Store.java:223) 
 at 
 org.apache.hadoop.hbase.regionserver.HRegion.instantiateHStore(HRegion.java:2534)
  
 at org.apache.hadoop.hbase.regionserver.HRegion.initialize(HRegion.java:454) 
 at 
 org.apache.hadoop.hbase.regionserver.HRegion.openHRegion(HRegion.java:3282) 
 at 
 org.apache.hadoop.hbase.regionserver.HRegion.openHRegion(HRegion.java:3230) 
 at 
 org.apache.hadoop.hbase.regionserver.handler.OpenRegionHandler.openRegion(OpenRegionHandler.java:331)
 at 
 org.apache.hadoop.hbase.regionserver.handler.OpenRegionHandler.process(OpenRegionHandler.java:107)
 at org.apache.hadoop.hbase.executor.EventHandler.run(EventHandler.java:169) 
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
  
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
  
 at java.lang.Thread.run(Thread.java:619) 
 Caused by: java.lang.IllegalArgumentException: Invalid HFile version: 
 842220600 (expected to be between 1 and 2) 
 at org.apache.hadoop.hbase.io.hfile.HFile.checkFormatVersion(HFile.java:515) 
 at 
 org.apache.hadoop.hbase.io.hfile.FixedFileTrailer.readFromStream(FixedFileTrailer.java:303)
  
 ... 17 more
 {code}
 Specifically -- the FixedFileTrailer are incorrect, and seemingly missing.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (HBASE-6586) Quarantine Corrupted HFiles


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

Jonathan Hsieh updated HBASE-6586:
--

Attachment: (was: hbase-6586-trunk-v8.patch)

 Quarantine Corrupted HFiles
 ---

 Key: HBASE-6586
 URL: https://issues.apache.org/jira/browse/HBASE-6586
 Project: HBase
  Issue Type: Improvement
Reporter: Jonathan Hsieh
Assignee: Jonathan Hsieh
 Attachments: 0001-hbase-6568-hbck-quarantine-v6.patch, 
 hbase-6586-92-v3.patch, hbase-6586-92-v8.patch, hbase-6586-94-v3.patch, 
 hbase-6586-94-v8.patch, hbase-6586.patch, hbase-6586-trunk-v3.patch, 
 hbase-6586-trunk-v4.patch, hbase-6586-trunk-v5.patch, 
 hbase-6586-trunk-v6.patch, hbase-6586-trunk-v7.patch, 
 hbase-6586-trunk-v8.patch


 We've encountered a few upgrades from 0.90 hbases + 20.2/1.x hdfs to 0.92 
 hbases + hdfs 2.x that get stuck.  I haven't been able to duplicate the 
 problem in my dev environment but we suspect this may be related to 
 HDFS-3731.  On the HBase side, it seems reasonable to quarantine what are 
 most likely truncated hfiles, so that can could later be recovered.
 Here's an example of the exception we've encountered:
 {code}
 2012-07-18 05:55:01,152 ERROR handler.OpenRegionHandler 
 (OpenRegionHandler.java:openRegion(346)) - Failed open of 
 region=user_mappings,080112102AA76EF98197605D341B9E6C5824D2BC|1001,1317824890618.eaed0e7abc6d27d28ff0e5a9b49c4c
 0d. 
 java.io.IOException: java.lang.IllegalArgumentException: Invalid HFile 
 version: 842220600 (expected to be between 1 and 2) 
 at 
 org.apache.hadoop.hbase.io.hfile.FixedFileTrailer.readFromStream(FixedFileTrailer.java:306)
  
 at org.apache.hadoop.hbase.io.hfile.HFile.pickReaderVersion(HFile.java:371) 
 at org.apache.hadoop.hbase.io.hfile.HFile.createReader(HFile.java:387) 
 at 
 org.apache.hadoop.hbase.regionserver.StoreFile$Reader.init(StoreFile.java:1026)
  
 at org.apache.hadoop.hbase.regionserver.StoreFile.open(StoreFile.java:485) 
 at 
 org.apache.hadoop.hbase.regionserver.StoreFile.createReader(StoreFile.java:566)
  
 at org.apache.hadoop.hbase.regionserver.Store.loadStoreFiles(Store.java:286) 
 at org.apache.hadoop.hbase.regionserver.Store.init(Store.java:223) 
 at 
 org.apache.hadoop.hbase.regionserver.HRegion.instantiateHStore(HRegion.java:2534)
  
 at org.apache.hadoop.hbase.regionserver.HRegion.initialize(HRegion.java:454) 
 at 
 org.apache.hadoop.hbase.regionserver.HRegion.openHRegion(HRegion.java:3282) 
 at 
 org.apache.hadoop.hbase.regionserver.HRegion.openHRegion(HRegion.java:3230) 
 at 
 org.apache.hadoop.hbase.regionserver.handler.OpenRegionHandler.openRegion(OpenRegionHandler.java:331)
 at 
 org.apache.hadoop.hbase.regionserver.handler.OpenRegionHandler.process(OpenRegionHandler.java:107)
 at org.apache.hadoop.hbase.executor.EventHandler.run(EventHandler.java:169) 
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
  
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
  
 at java.lang.Thread.run(Thread.java:619) 
 Caused by: java.lang.IllegalArgumentException: Invalid HFile version: 
 842220600 (expected to be between 1 and 2) 
 at org.apache.hadoop.hbase.io.hfile.HFile.checkFormatVersion(HFile.java:515) 
 at 
 org.apache.hadoop.hbase.io.hfile.FixedFileTrailer.readFromStream(FixedFileTrailer.java:303)
  
 ... 17 more
 {code}
 Specifically -- the FixedFileTrailer are incorrect, and seemingly missing.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (HBASE-6584) TestAssignmentManager#testDisablingTableRegionsAssignmentDuringCleanClusterStartup fails due to port 60000 already in use.


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

rajeshbabu updated HBASE-6584:
--

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

 TestAssignmentManager#testDisablingTableRegionsAssignmentDuringCleanClusterStartup
  fails due to port 6 already in use.
 --

 Key: HBASE-6584
 URL: https://issues.apache.org/jira/browse/HBASE-6584
 Project: HBase
  Issue Type: Bug
  Components: test
Affects Versions: 0.94.0
Reporter: Sameer Vaishampayan
Assignee: rajeshbabu
Priority: Critical
 Fix For: 0.96.0

 Attachments: HBASE-6584_trunk_2.patch, HBASE-6584_trunk_3.patch, 
 HBASE-6584_trunk.patch, HBASE-6584_trunk.patch, patch2.diff




--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Assigned] (HBASE-5166) MultiThreaded Table Mapper analogous to MultiThreaded Mapper in hadoop


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

Jean-Daniel Cryans reassigned HBASE-5166:
-

Assignee: Jai Kumar Singh

Added Jai as a contributor and assigned the Jira.

 MultiThreaded Table Mapper analogous to MultiThreaded Mapper in hadoop
 --

 Key: HBASE-5166
 URL: https://issues.apache.org/jira/browse/HBASE-5166
 Project: HBase
  Issue Type: Improvement
Reporter: Jai Kumar Singh
Assignee: Jai Kumar Singh
Priority: Minor
  Labels: multithreaded, tablemapper
 Fix For: 0.94.0

 Attachments: 0001-Added-MultithreadedTableMapper-HBASE-5166.patch, 
 0003-Added-MultithreadedTableMapper-HBASE-5166.patch, 
 0005-HBASE-5166-Added-MultithreadedTableMapper.patch, 
 0006-HBASE-5166-Added-MultithreadedTableMapper.patch, 
 0008-HBASE-5166-Added-MultithreadedTableMapper.patch, 5166-v9.txt

   Original Estimate: 0.5h
  Remaining Estimate: 0.5h

 There is no MultiThreadedTableMapper in hbase currently just like we have a 
 MultiThreadedMapper in Hadoop for IO Bound Jobs. 
 UseCase, webcrawler: take input (urls) from a hbase table and put the content 
 (urls, content) back into hbase. 
 Running these kind of hbase mapreduce job with normal table mapper is quite 
 slow as we are not utilizing CPU fully (N/W IO Bound).
 Moreover, I want to know whether It would be a good/bad idea to use HBase for 
 these kind of usecases ?. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HBASE-6477) Use PB filter definitions in RPC


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

Ted Yu commented on HBASE-6477:
---

@Stack:
What's your opinion ?

 Use PB filter definitions in RPC
 

 Key: HBASE-6477
 URL: https://issues.apache.org/jira/browse/HBASE-6477
 Project: HBase
  Issue Type: Task
  Components: ipc, migration
Reporter: Gregory Chanan
Assignee: Gregory Chanan
 Fix For: 0.96.0

 Attachments: 6477-addendum.patch, HBASE-6477-addendum.patch, 
 HBASE-6477-nonrb.patch, HBASE-6477-nonrb-v3.patch, HBASE-6477-nonrb-v4.patch


 Use the filters introduced in HBASE-6454 in the rpc so they are extensible

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (HBASE-6586) Quarantine Corrupted HFiles


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

Jonathan Hsieh updated HBASE-6586:
--

Attachment: hbase-6586-92-v8a.patch

Previous 92 version was missing new HBaseIOException.java file.

 Quarantine Corrupted HFiles
 ---

 Key: HBASE-6586
 URL: https://issues.apache.org/jira/browse/HBASE-6586
 Project: HBase
  Issue Type: Improvement
Reporter: Jonathan Hsieh
Assignee: Jonathan Hsieh
 Attachments: 0001-hbase-6568-hbck-quarantine-v6.patch, 
 hbase-6586-92-v3.patch, hbase-6586-92-v8a.patch, hbase-6586-92-v8.patch, 
 hbase-6586-94-v3.patch, hbase-6586-94-v8.patch, hbase-6586.patch, 
 hbase-6586-trunk-v3.patch, hbase-6586-trunk-v4.patch, 
 hbase-6586-trunk-v5.patch, hbase-6586-trunk-v6.patch, 
 hbase-6586-trunk-v7.patch, hbase-6586-trunk-v8.patch


 We've encountered a few upgrades from 0.90 hbases + 20.2/1.x hdfs to 0.92 
 hbases + hdfs 2.x that get stuck.  I haven't been able to duplicate the 
 problem in my dev environment but we suspect this may be related to 
 HDFS-3731.  On the HBase side, it seems reasonable to quarantine what are 
 most likely truncated hfiles, so that can could later be recovered.
 Here's an example of the exception we've encountered:
 {code}
 2012-07-18 05:55:01,152 ERROR handler.OpenRegionHandler 
 (OpenRegionHandler.java:openRegion(346)) - Failed open of 
 region=user_mappings,080112102AA76EF98197605D341B9E6C5824D2BC|1001,1317824890618.eaed0e7abc6d27d28ff0e5a9b49c4c
 0d. 
 java.io.IOException: java.lang.IllegalArgumentException: Invalid HFile 
 version: 842220600 (expected to be between 1 and 2) 
 at 
 org.apache.hadoop.hbase.io.hfile.FixedFileTrailer.readFromStream(FixedFileTrailer.java:306)
  
 at org.apache.hadoop.hbase.io.hfile.HFile.pickReaderVersion(HFile.java:371) 
 at org.apache.hadoop.hbase.io.hfile.HFile.createReader(HFile.java:387) 
 at 
 org.apache.hadoop.hbase.regionserver.StoreFile$Reader.init(StoreFile.java:1026)
  
 at org.apache.hadoop.hbase.regionserver.StoreFile.open(StoreFile.java:485) 
 at 
 org.apache.hadoop.hbase.regionserver.StoreFile.createReader(StoreFile.java:566)
  
 at org.apache.hadoop.hbase.regionserver.Store.loadStoreFiles(Store.java:286) 
 at org.apache.hadoop.hbase.regionserver.Store.init(Store.java:223) 
 at 
 org.apache.hadoop.hbase.regionserver.HRegion.instantiateHStore(HRegion.java:2534)
  
 at org.apache.hadoop.hbase.regionserver.HRegion.initialize(HRegion.java:454) 
 at 
 org.apache.hadoop.hbase.regionserver.HRegion.openHRegion(HRegion.java:3282) 
 at 
 org.apache.hadoop.hbase.regionserver.HRegion.openHRegion(HRegion.java:3230) 
 at 
 org.apache.hadoop.hbase.regionserver.handler.OpenRegionHandler.openRegion(OpenRegionHandler.java:331)
 at 
 org.apache.hadoop.hbase.regionserver.handler.OpenRegionHandler.process(OpenRegionHandler.java:107)
 at org.apache.hadoop.hbase.executor.EventHandler.run(EventHandler.java:169) 
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
  
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
  
 at java.lang.Thread.run(Thread.java:619) 
 Caused by: java.lang.IllegalArgumentException: Invalid HFile version: 
 842220600 (expected to be between 1 and 2) 
 at org.apache.hadoop.hbase.io.hfile.HFile.checkFormatVersion(HFile.java:515) 
 at 
 org.apache.hadoop.hbase.io.hfile.FixedFileTrailer.readFromStream(FixedFileTrailer.java:303)
  
 ... 17 more
 {code}
 Specifically -- the FixedFileTrailer are incorrect, and seemingly missing.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (HBASE-6671) Kerberos authenticated super user should be able to retrieve proxied delegation tokens


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

Francis Liu updated HBASE-6671:
---

Attachment: proxy_fix_trunk.patch

Logic is culled from the namenode and jobtracker for consistency.

 Kerberos authenticated super user should be able to retrieve proxied 
 delegation tokens
 --

 Key: HBASE-6671
 URL: https://issues.apache.org/jira/browse/HBASE-6671
 Project: HBase
  Issue Type: Bug
Affects Versions: 0.94.1
Reporter: Francis Liu
Assignee: Francis Liu
 Attachments: proxy_fix_trunk.patch


 There a services such a oozie which perform actions in behalf of the user 
 using proxy authentication. Retrieving delegation tokens should support this 
 behavior. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (HBASE-6671) Kerberos authenticated super user should be able to retrieve proxied delegation tokens

Francis Liu created HBASE-6671:
--

 Summary: Kerberos authenticated super user should be able to 
retrieve proxied delegation tokens
 Key: HBASE-6671
 URL: https://issues.apache.org/jira/browse/HBASE-6671
 Project: HBase
  Issue Type: Bug
Affects Versions: 0.94.1
Reporter: Francis Liu
Assignee: Francis Liu
 Attachments: proxy_fix_trunk.patch

There a services such a oozie which perform actions in behalf of the user using 
proxy authentication. Retrieving delegation tokens should support this 
behavior. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (HBASE-6671) Kerberos authenticated super user should be able to retrieve proxied delegation tokens


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

Francis Liu updated HBASE-6671:
---

Attachment: proxy_fix_94.patch

0.94 patch, includes updating the hadoop-0.23 dependency since there are binary 
incompatible changes. Also 0.23.3 should be released in a few weeks.

 Kerberos authenticated super user should be able to retrieve proxied 
 delegation tokens
 --

 Key: HBASE-6671
 URL: https://issues.apache.org/jira/browse/HBASE-6671
 Project: HBase
  Issue Type: Bug
Affects Versions: 0.94.1
Reporter: Francis Liu
Assignee: Francis Liu
 Attachments: proxy_fix_94.patch, proxy_fix_trunk.patch


 There a services such a oozie which perform actions in behalf of the user 
 using proxy authentication. Retrieving delegation tokens should support this 
 behavior. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HBASE-5826) Improve sync of HLog edits

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

Hadoop QA commented on HBASE-5826:
--

-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12542625/5826-v5.txt
against trunk revision .

+1 @author. The patch does not contain any @author tags.

+1 tests included. The patch appears to include 3 new or modified tests.

+1 hadoop2.0. The patch compiles against the hadoop 2.0 profile.

-1 javadoc. The javadoc tool appears to have generated 94 warning messages.

-1 javac. The applied patch generated 5 javac compiler warnings (more than
the trunk's current 4 warnings).

-1 findbugs. The patch appears to introduce 13 new Findbugs (version
1.3.9) warnings.

+1 release audit. The applied patch does not increase the total number of
release audit warnings.

-1 core tests. The patch failed these unit tests:

org.apache.hadoop.hbase.regionserver.wal.TestWALReplayCompressed

org.apache.hadoop.hbase.client.TestFromClientSideWithCoprocessor
org.apache.hadoop.hbase.regionserver.wal.TestWALReplay

Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/2702//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/2702//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/2702//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/2702//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/2702//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/2702//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/2702//console

This message is automatically generated.

Improve sync of HLog edits
--

Key: HBASE-5826
URL: https://issues.apache.org/jira/browse/HBASE-5826
Project: HBase
Issue Type: Improvement
Reporter: Zhihong Ted Yu
Assignee: Todd Lipcon
Fix For: 0.96.0

Attachments: 5826.txt, 5826-v2.txt, 5826-v3.txt, 5826-v4.txt,
5826-v5.txt

HBASE-5782 solved the correctness issue for the sync of HLog edits.
Todd provided a patch that would achieve higher throughput.
This JIRA is a continuation of Todd's work submitted there.

[jira] [Updated] (HBASE-6586) Quarantine Corrupted HFiles


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

Jonathan Hsieh updated HBASE-6586:
--

Attachment: hbase-6586-92-v8b.patch

Cleaned up some a merge conflict that was in a comment that I had missed.

 Quarantine Corrupted HFiles
 ---

 Key: HBASE-6586
 URL: https://issues.apache.org/jira/browse/HBASE-6586
 Project: HBase
  Issue Type: Improvement
Reporter: Jonathan Hsieh
Assignee: Jonathan Hsieh
 Attachments: 0001-hbase-6568-hbck-quarantine-v6.patch, 
 hbase-6586-92-v3.patch, hbase-6586-92-v8a.patch, hbase-6586-92-v8b.patch, 
 hbase-6586-92-v8.patch, hbase-6586-94-v3.patch, hbase-6586-94-v8.patch, 
 hbase-6586.patch, hbase-6586-trunk-v3.patch, hbase-6586-trunk-v4.patch, 
 hbase-6586-trunk-v5.patch, hbase-6586-trunk-v6.patch, 
 hbase-6586-trunk-v7.patch, hbase-6586-trunk-v8.patch


 We've encountered a few upgrades from 0.90 hbases + 20.2/1.x hdfs to 0.92 
 hbases + hdfs 2.x that get stuck.  I haven't been able to duplicate the 
 problem in my dev environment but we suspect this may be related to 
 HDFS-3731.  On the HBase side, it seems reasonable to quarantine what are 
 most likely truncated hfiles, so that can could later be recovered.
 Here's an example of the exception we've encountered:
 {code}
 2012-07-18 05:55:01,152 ERROR handler.OpenRegionHandler 
 (OpenRegionHandler.java:openRegion(346)) - Failed open of 
 region=user_mappings,080112102AA76EF98197605D341B9E6C5824D2BC|1001,1317824890618.eaed0e7abc6d27d28ff0e5a9b49c4c
 0d. 
 java.io.IOException: java.lang.IllegalArgumentException: Invalid HFile 
 version: 842220600 (expected to be between 1 and 2) 
 at 
 org.apache.hadoop.hbase.io.hfile.FixedFileTrailer.readFromStream(FixedFileTrailer.java:306)
  
 at org.apache.hadoop.hbase.io.hfile.HFile.pickReaderVersion(HFile.java:371) 
 at org.apache.hadoop.hbase.io.hfile.HFile.createReader(HFile.java:387) 
 at 
 org.apache.hadoop.hbase.regionserver.StoreFile$Reader.init(StoreFile.java:1026)
  
 at org.apache.hadoop.hbase.regionserver.StoreFile.open(StoreFile.java:485) 
 at 
 org.apache.hadoop.hbase.regionserver.StoreFile.createReader(StoreFile.java:566)
  
 at org.apache.hadoop.hbase.regionserver.Store.loadStoreFiles(Store.java:286) 
 at org.apache.hadoop.hbase.regionserver.Store.init(Store.java:223) 
 at 
 org.apache.hadoop.hbase.regionserver.HRegion.instantiateHStore(HRegion.java:2534)
  
 at org.apache.hadoop.hbase.regionserver.HRegion.initialize(HRegion.java:454) 
 at 
 org.apache.hadoop.hbase.regionserver.HRegion.openHRegion(HRegion.java:3282) 
 at 
 org.apache.hadoop.hbase.regionserver.HRegion.openHRegion(HRegion.java:3230) 
 at 
 org.apache.hadoop.hbase.regionserver.handler.OpenRegionHandler.openRegion(OpenRegionHandler.java:331)
 at 
 org.apache.hadoop.hbase.regionserver.handler.OpenRegionHandler.process(OpenRegionHandler.java:107)
 at org.apache.hadoop.hbase.executor.EventHandler.run(EventHandler.java:169) 
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
  
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
  
 at java.lang.Thread.run(Thread.java:619) 
 Caused by: java.lang.IllegalArgumentException: Invalid HFile version: 
 842220600 (expected to be between 1 and 2) 
 at org.apache.hadoop.hbase.io.hfile.HFile.checkFormatVersion(HFile.java:515) 
 at 
 org.apache.hadoop.hbase.io.hfile.FixedFileTrailer.readFromStream(FixedFileTrailer.java:303)
  
 ... 17 more
 {code}
 Specifically -- the FixedFileTrailer are incorrect, and seemingly missing.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HBASE-6671) Kerberos authenticated super user should be able to retrieve proxied delegation tokens


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

Ted Yu commented on HBASE-6671:
---

@Francis:
Hadoop QA would pick up the latest attachment.
In the future, please attach trunk patch last.

 Kerberos authenticated super user should be able to retrieve proxied 
 delegation tokens
 --

 Key: HBASE-6671
 URL: https://issues.apache.org/jira/browse/HBASE-6671
 Project: HBase
  Issue Type: Bug
Affects Versions: 0.94.1
Reporter: Francis Liu
Assignee: Francis Liu
 Attachments: proxy_fix_94.patch, proxy_fix_trunk.patch


 There a services such a oozie which perform actions in behalf of the user 
 using proxy authentication. Retrieving delegation tokens should support this 
 behavior. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HBASE-6586) Quarantine Corrupted HFiles


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

Hadoop QA commented on HBASE-6586:
--

-1 overall.  Here are the results of testing the latest attachment 
  
http://issues.apache.org/jira/secure/attachment/12542640/hbase-6586-92-v8b.patch
  against trunk revision .

+1 @author.  The patch does not contain any @author tags.

+1 tests included.  The patch appears to include 12 new or modified tests.

-1 patch.  The patch command could not apply the patch.

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

This message is automatically generated.

 Quarantine Corrupted HFiles
 ---

 Key: HBASE-6586
 URL: https://issues.apache.org/jira/browse/HBASE-6586
 Project: HBase
  Issue Type: Improvement
Reporter: Jonathan Hsieh
Assignee: Jonathan Hsieh
 Attachments: 0001-hbase-6568-hbck-quarantine-v6.patch, 
 hbase-6586-92-v3.patch, hbase-6586-92-v8a.patch, hbase-6586-92-v8b.patch, 
 hbase-6586-92-v8.patch, hbase-6586-94-v3.patch, hbase-6586-94-v8.patch, 
 hbase-6586.patch, hbase-6586-trunk-v3.patch, hbase-6586-trunk-v4.patch, 
 hbase-6586-trunk-v5.patch, hbase-6586-trunk-v6.patch, 
 hbase-6586-trunk-v7.patch, hbase-6586-trunk-v8.patch


 We've encountered a few upgrades from 0.90 hbases + 20.2/1.x hdfs to 0.92 
 hbases + hdfs 2.x that get stuck.  I haven't been able to duplicate the 
 problem in my dev environment but we suspect this may be related to 
 HDFS-3731.  On the HBase side, it seems reasonable to quarantine what are 
 most likely truncated hfiles, so that can could later be recovered.
 Here's an example of the exception we've encountered:
 {code}
 2012-07-18 05:55:01,152 ERROR handler.OpenRegionHandler 
 (OpenRegionHandler.java:openRegion(346)) - Failed open of 
 region=user_mappings,080112102AA76EF98197605D341B9E6C5824D2BC|1001,1317824890618.eaed0e7abc6d27d28ff0e5a9b49c4c
 0d. 
 java.io.IOException: java.lang.IllegalArgumentException: Invalid HFile 
 version: 842220600 (expected to be between 1 and 2) 
 at 
 org.apache.hadoop.hbase.io.hfile.FixedFileTrailer.readFromStream(FixedFileTrailer.java:306)
  
 at org.apache.hadoop.hbase.io.hfile.HFile.pickReaderVersion(HFile.java:371) 
 at org.apache.hadoop.hbase.io.hfile.HFile.createReader(HFile.java:387) 
 at 
 org.apache.hadoop.hbase.regionserver.StoreFile$Reader.init(StoreFile.java:1026)
  
 at org.apache.hadoop.hbase.regionserver.StoreFile.open(StoreFile.java:485) 
 at 
 org.apache.hadoop.hbase.regionserver.StoreFile.createReader(StoreFile.java:566)
  
 at org.apache.hadoop.hbase.regionserver.Store.loadStoreFiles(Store.java:286) 
 at org.apache.hadoop.hbase.regionserver.Store.init(Store.java:223) 
 at 
 org.apache.hadoop.hbase.regionserver.HRegion.instantiateHStore(HRegion.java:2534)
  
 at org.apache.hadoop.hbase.regionserver.HRegion.initialize(HRegion.java:454) 
 at 
 org.apache.hadoop.hbase.regionserver.HRegion.openHRegion(HRegion.java:3282) 
 at 
 org.apache.hadoop.hbase.regionserver.HRegion.openHRegion(HRegion.java:3230) 
 at 
 org.apache.hadoop.hbase.regionserver.handler.OpenRegionHandler.openRegion(OpenRegionHandler.java:331)
 at 
 org.apache.hadoop.hbase.regionserver.handler.OpenRegionHandler.process(OpenRegionHandler.java:107)
 at org.apache.hadoop.hbase.executor.EventHandler.run(EventHandler.java:169) 
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
  
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
  
 at java.lang.Thread.run(Thread.java:619) 
 Caused by: java.lang.IllegalArgumentException: Invalid HFile version: 
 842220600 (expected to be between 1 and 2) 
 at org.apache.hadoop.hbase.io.hfile.HFile.checkFormatVersion(HFile.java:515) 
 at 
 org.apache.hadoop.hbase.io.hfile.FixedFileTrailer.readFromStream(FixedFileTrailer.java:303)
  
 ... 17 more
 {code}
 Specifically -- the FixedFileTrailer are incorrect, and seemingly missing.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HBASE-6671) Kerberos authenticated super user should be able to retrieve proxied delegation tokens


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

Francis Liu commented on HBASE-6671:


Will do, thanks for the tip.

 Kerberos authenticated super user should be able to retrieve proxied 
 delegation tokens
 --

 Key: HBASE-6671
 URL: https://issues.apache.org/jira/browse/HBASE-6671
 Project: HBase
  Issue Type: Bug
Affects Versions: 0.94.1
Reporter: Francis Liu
Assignee: Francis Liu
 Attachments: proxy_fix_94.patch, proxy_fix_trunk.patch


 There a services such a oozie which perform actions in behalf of the user 
 using proxy authentication. Retrieving delegation tokens should support this 
 behavior. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HBASE-6671) Kerberos authenticated super user should be able to retrieve proxied delegation tokens


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

Ted Yu commented on HBASE-6671:
---

getConnectionAuthenticationMethod() is a private method, can it be inlined ?

Minor:
javadoc for parameters of getConnectionAuthenticationMethod() and 
isAllowedDelegationTokenOp() is missing.

 Kerberos authenticated super user should be able to retrieve proxied 
 delegation tokens
 --

 Key: HBASE-6671
 URL: https://issues.apache.org/jira/browse/HBASE-6671
 Project: HBase
  Issue Type: Bug
Affects Versions: 0.94.1
Reporter: Francis Liu
Assignee: Francis Liu
 Attachments: proxy_fix_94.patch, proxy_fix_trunk.patch


 There a services such a oozie which perform actions in behalf of the user 
 using proxy authentication. Retrieving delegation tokens should support this 
 behavior. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (HBASE-6586) Quarantine Corrupted HFiles


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

Jonathan Hsieh updated HBASE-6586:
--

Attachment: (was: hbase-6586-trunk-v8.patch)

 Quarantine Corrupted HFiles
 ---

 Key: HBASE-6586
 URL: https://issues.apache.org/jira/browse/HBASE-6586
 Project: HBase
  Issue Type: Improvement
Reporter: Jonathan Hsieh
Assignee: Jonathan Hsieh
 Attachments: 0001-hbase-6568-hbck-quarantine-v6.patch, 
 hbase-6586-92-v3.patch, hbase-6586-92-v8a.patch, hbase-6586-92-v8b.patch, 
 hbase-6586-92-v8.patch, hbase-6586-94-v3.patch, hbase-6586-94-v8.patch, 
 hbase-6586.patch, hbase-6586-trunk-v3.patch, hbase-6586-trunk-v4.patch, 
 hbase-6586-trunk-v5.patch, hbase-6586-trunk-v6.patch, 
 hbase-6586-trunk-v7.patch, hbase-6586-trunk-v8.patch


 We've encountered a few upgrades from 0.90 hbases + 20.2/1.x hdfs to 0.92 
 hbases + hdfs 2.x that get stuck.  I haven't been able to duplicate the 
 problem in my dev environment but we suspect this may be related to 
 HDFS-3731.  On the HBase side, it seems reasonable to quarantine what are 
 most likely truncated hfiles, so that can could later be recovered.
 Here's an example of the exception we've encountered:
 {code}
 2012-07-18 05:55:01,152 ERROR handler.OpenRegionHandler 
 (OpenRegionHandler.java:openRegion(346)) - Failed open of 
 region=user_mappings,080112102AA76EF98197605D341B9E6C5824D2BC|1001,1317824890618.eaed0e7abc6d27d28ff0e5a9b49c4c
 0d. 
 java.io.IOException: java.lang.IllegalArgumentException: Invalid HFile 
 version: 842220600 (expected to be between 1 and 2) 
 at 
 org.apache.hadoop.hbase.io.hfile.FixedFileTrailer.readFromStream(FixedFileTrailer.java:306)
  
 at org.apache.hadoop.hbase.io.hfile.HFile.pickReaderVersion(HFile.java:371) 
 at org.apache.hadoop.hbase.io.hfile.HFile.createReader(HFile.java:387) 
 at 
 org.apache.hadoop.hbase.regionserver.StoreFile$Reader.init(StoreFile.java:1026)
  
 at org.apache.hadoop.hbase.regionserver.StoreFile.open(StoreFile.java:485) 
 at 
 org.apache.hadoop.hbase.regionserver.StoreFile.createReader(StoreFile.java:566)
  
 at org.apache.hadoop.hbase.regionserver.Store.loadStoreFiles(Store.java:286) 
 at org.apache.hadoop.hbase.regionserver.Store.init(Store.java:223) 
 at 
 org.apache.hadoop.hbase.regionserver.HRegion.instantiateHStore(HRegion.java:2534)
  
 at org.apache.hadoop.hbase.regionserver.HRegion.initialize(HRegion.java:454) 
 at 
 org.apache.hadoop.hbase.regionserver.HRegion.openHRegion(HRegion.java:3282) 
 at 
 org.apache.hadoop.hbase.regionserver.HRegion.openHRegion(HRegion.java:3230) 
 at 
 org.apache.hadoop.hbase.regionserver.handler.OpenRegionHandler.openRegion(OpenRegionHandler.java:331)
 at 
 org.apache.hadoop.hbase.regionserver.handler.OpenRegionHandler.process(OpenRegionHandler.java:107)
 at org.apache.hadoop.hbase.executor.EventHandler.run(EventHandler.java:169) 
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
  
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
  
 at java.lang.Thread.run(Thread.java:619) 
 Caused by: java.lang.IllegalArgumentException: Invalid HFile version: 
 842220600 (expected to be between 1 and 2) 
 at org.apache.hadoop.hbase.io.hfile.HFile.checkFormatVersion(HFile.java:515) 
 at 
 org.apache.hadoop.hbase.io.hfile.FixedFileTrailer.readFromStream(FixedFileTrailer.java:303)
  
 ... 17 more
 {code}
 Specifically -- the FixedFileTrailer are incorrect, and seemingly missing.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (HBASE-6586) Quarantine Corrupted HFiles


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

Jonathan Hsieh updated HBASE-6586:
--

Attachment: hbase-6586-trunk-v8.patch

Doing this again because hadoopqa picked up the wrong patch.

 Quarantine Corrupted HFiles
 ---

 Key: HBASE-6586
 URL: https://issues.apache.org/jira/browse/HBASE-6586
 Project: HBase
  Issue Type: Improvement
Reporter: Jonathan Hsieh
Assignee: Jonathan Hsieh
 Attachments: 0001-hbase-6568-hbck-quarantine-v6.patch, 
 hbase-6586-92-v3.patch, hbase-6586-92-v8a.patch, hbase-6586-92-v8b.patch, 
 hbase-6586-92-v8.patch, hbase-6586-94-v3.patch, hbase-6586-94-v8.patch, 
 hbase-6586.patch, hbase-6586-trunk-v3.patch, hbase-6586-trunk-v4.patch, 
 hbase-6586-trunk-v5.patch, hbase-6586-trunk-v6.patch, 
 hbase-6586-trunk-v7.patch, hbase-6586-trunk-v8.patch


 We've encountered a few upgrades from 0.90 hbases + 20.2/1.x hdfs to 0.92 
 hbases + hdfs 2.x that get stuck.  I haven't been able to duplicate the 
 problem in my dev environment but we suspect this may be related to 
 HDFS-3731.  On the HBase side, it seems reasonable to quarantine what are 
 most likely truncated hfiles, so that can could later be recovered.
 Here's an example of the exception we've encountered:
 {code}
 2012-07-18 05:55:01,152 ERROR handler.OpenRegionHandler 
 (OpenRegionHandler.java:openRegion(346)) - Failed open of 
 region=user_mappings,080112102AA76EF98197605D341B9E6C5824D2BC|1001,1317824890618.eaed0e7abc6d27d28ff0e5a9b49c4c
 0d. 
 java.io.IOException: java.lang.IllegalArgumentException: Invalid HFile 
 version: 842220600 (expected to be between 1 and 2) 
 at 
 org.apache.hadoop.hbase.io.hfile.FixedFileTrailer.readFromStream(FixedFileTrailer.java:306)
  
 at org.apache.hadoop.hbase.io.hfile.HFile.pickReaderVersion(HFile.java:371) 
 at org.apache.hadoop.hbase.io.hfile.HFile.createReader(HFile.java:387) 
 at 
 org.apache.hadoop.hbase.regionserver.StoreFile$Reader.init(StoreFile.java:1026)
  
 at org.apache.hadoop.hbase.regionserver.StoreFile.open(StoreFile.java:485) 
 at 
 org.apache.hadoop.hbase.regionserver.StoreFile.createReader(StoreFile.java:566)
  
 at org.apache.hadoop.hbase.regionserver.Store.loadStoreFiles(Store.java:286) 
 at org.apache.hadoop.hbase.regionserver.Store.init(Store.java:223) 
 at 
 org.apache.hadoop.hbase.regionserver.HRegion.instantiateHStore(HRegion.java:2534)
  
 at org.apache.hadoop.hbase.regionserver.HRegion.initialize(HRegion.java:454) 
 at 
 org.apache.hadoop.hbase.regionserver.HRegion.openHRegion(HRegion.java:3282) 
 at 
 org.apache.hadoop.hbase.regionserver.HRegion.openHRegion(HRegion.java:3230) 
 at 
 org.apache.hadoop.hbase.regionserver.handler.OpenRegionHandler.openRegion(OpenRegionHandler.java:331)
 at 
 org.apache.hadoop.hbase.regionserver.handler.OpenRegionHandler.process(OpenRegionHandler.java:107)
 at org.apache.hadoop.hbase.executor.EventHandler.run(EventHandler.java:169) 
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
  
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
  
 at java.lang.Thread.run(Thread.java:619) 
 Caused by: java.lang.IllegalArgumentException: Invalid HFile version: 
 842220600 (expected to be between 1 and 2) 
 at org.apache.hadoop.hbase.io.hfile.HFile.checkFormatVersion(HFile.java:515) 
 at 
 org.apache.hadoop.hbase.io.hfile.FixedFileTrailer.readFromStream(FixedFileTrailer.java:303)
  
 ... 17 more
 {code}
 Specifically -- the FixedFileTrailer are incorrect, and seemingly missing.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HBASE-6477) Use PB filter definitions in RPC


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

stack commented on HBASE-6477:
--

+1 on addendum.  Thanks Gregory for figuring it out (and Ted for finding 
issue).   Good stuff lads.  Will I commit?

 Use PB filter definitions in RPC
 

 Key: HBASE-6477
 URL: https://issues.apache.org/jira/browse/HBASE-6477
 Project: HBase
  Issue Type: Task
  Components: ipc, migration
Reporter: Gregory Chanan
Assignee: Gregory Chanan
 Fix For: 0.96.0

 Attachments: 6477-addendum.patch, HBASE-6477-addendum.patch, 
 HBASE-6477-nonrb.patch, HBASE-6477-nonrb-v3.patch, HBASE-6477-nonrb-v4.patch


 Use the filters introduced in HBASE-6454 in the rpc so they are extensible

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HBASE-6477) Use PB filter definitions in RPC


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

Ted Yu commented on HBASE-6477:
---

Go ahead, Stack.

 Use PB filter definitions in RPC
 

 Key: HBASE-6477
 URL: https://issues.apache.org/jira/browse/HBASE-6477
 Project: HBase
  Issue Type: Task
  Components: ipc, migration
Reporter: Gregory Chanan
Assignee: Gregory Chanan
 Fix For: 0.96.0

 Attachments: 6477-addendum.patch, HBASE-6477-addendum.patch, 
 HBASE-6477-nonrb.patch, HBASE-6477-nonrb-v3.patch, HBASE-6477-nonrb-v4.patch


 Use the filters introduced in HBASE-6454 in the rpc so they are extensible

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (HBASE-6477) Use PB filter definitions in RPC


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

stack updated HBASE-6477:
-

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

I applied the addendum.  Good stuff lads.

 Use PB filter definitions in RPC
 

 Key: HBASE-6477
 URL: https://issues.apache.org/jira/browse/HBASE-6477
 Project: HBase
  Issue Type: Task
  Components: ipc, migration
Reporter: Gregory Chanan
Assignee: Gregory Chanan
 Fix For: 0.96.0

 Attachments: 6477-addendum.patch, HBASE-6477-addendum.patch, 
 HBASE-6477-nonrb.patch, HBASE-6477-nonrb-v3.patch, HBASE-6477-nonrb-v4.patch


 Use the filters introduced in HBASE-6454 in the rpc so they are extensible

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HBASE-6586) Quarantine Corrupted HFiles


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

Hadoop QA commented on HBASE-6586:
--

-1 overall.  Here are the results of testing the latest attachment 
  
http://issues.apache.org/jira/secure/attachment/12542628/hbase-6586-trunk-v8.patch
  against trunk revision .

+1 @author.  The patch does not contain any @author tags.

+1 tests included.  The patch appears to include 12 new or modified tests.

+1 hadoop2.0.  The patch compiles against the hadoop 2.0 profile.

-1 javadoc.  The javadoc tool appears to have generated 106 warning 
messages.

-1 javac.  The applied patch generated 5 javac compiler warnings (more than 
the trunk's current 4 warnings).

-1 findbugs.  The patch appears to introduce 14 new Findbugs (version 
1.3.9) warnings.

+1 release audit.  The applied patch does not increase the total number of 
release audit warnings.

 -1 core tests.  The patch failed these unit tests:
 

Test results: 
https://builds.apache.org/job/PreCommit-HBASE-Build/2703//testReport/
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/2703//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/2703//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/2703//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/2703//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/2703//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output: 
https://builds.apache.org/job/PreCommit-HBASE-Build/2703//console

This message is automatically generated.

 Quarantine Corrupted HFiles
 ---

 Key: HBASE-6586
 URL: https://issues.apache.org/jira/browse/HBASE-6586
 Project: HBase
  Issue Type: Improvement
Reporter: Jonathan Hsieh
Assignee: Jonathan Hsieh
 Attachments: 0001-hbase-6568-hbck-quarantine-v6.patch, 
 hbase-6586-92-v3.patch, hbase-6586-92-v8a.patch, hbase-6586-92-v8b.patch, 
 hbase-6586-92-v8.patch, hbase-6586-94-v3.patch, hbase-6586-94-v8.patch, 
 hbase-6586.patch, hbase-6586-trunk-v3.patch, hbase-6586-trunk-v4.patch, 
 hbase-6586-trunk-v5.patch, hbase-6586-trunk-v6.patch, 
 hbase-6586-trunk-v7.patch, hbase-6586-trunk-v8.patch


 We've encountered a few upgrades from 0.90 hbases + 20.2/1.x hdfs to 0.92 
 hbases + hdfs 2.x that get stuck.  I haven't been able to duplicate the 
 problem in my dev environment but we suspect this may be related to 
 HDFS-3731.  On the HBase side, it seems reasonable to quarantine what are 
 most likely truncated hfiles, so that can could later be recovered.
 Here's an example of the exception we've encountered:
 {code}
 2012-07-18 05:55:01,152 ERROR handler.OpenRegionHandler 
 (OpenRegionHandler.java:openRegion(346)) - Failed open of 
 region=user_mappings,080112102AA76EF98197605D341B9E6C5824D2BC|1001,1317824890618.eaed0e7abc6d27d28ff0e5a9b49c4c
 0d. 
 java.io.IOException: java.lang.IllegalArgumentException: Invalid HFile 
 version: 842220600 (expected to be between 1 and 2) 
 at 
 org.apache.hadoop.hbase.io.hfile.FixedFileTrailer.readFromStream(FixedFileTrailer.java:306)
  
 at org.apache.hadoop.hbase.io.hfile.HFile.pickReaderVersion(HFile.java:371) 
 at org.apache.hadoop.hbase.io.hfile.HFile.createReader(HFile.java:387) 
 at 
 org.apache.hadoop.hbase.regionserver.StoreFile$Reader.init(StoreFile.java:1026)
  
 at org.apache.hadoop.hbase.regionserver.StoreFile.open(StoreFile.java:485) 
 at 
 org.apache.hadoop.hbase.regionserver.StoreFile.createReader(StoreFile.java:566)
  
 at org.apache.hadoop.hbase.regionserver.Store.loadStoreFiles(Store.java:286) 
 at org.apache.hadoop.hbase.regionserver.Store.init(Store.java:223) 
 at 
 org.apache.hadoop.hbase.regionserver.HRegion.instantiateHStore(HRegion.java:2534)
  
 at org.apache.hadoop.hbase.regionserver.HRegion.initialize(HRegion.java:454) 
 at 
 org.apache.hadoop.hbase.regionserver.HRegion.openHRegion(HRegion.java:3282) 
 at 
 org.apache.hadoop.hbase.regionserver.HRegion.openHRegion(HRegion.java:3230) 
 at 
 org.apache.hadoop.hbase.regionserver.handler.OpenRegionHandler.openRegion(OpenRegionHandler.java:331)
 at 
 org.apache.hadoop.hbase.regionserver.handler.OpenRegionHandler.process(OpenRegionHandler.java:107)
 at org.apache.hadoop.hbase.executor.EventHandler.run(EventHandler.java:169) 
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
  
 at

[jira] [Updated] (HBASE-6671) Kerberos authenticated super user should be able to retrieve proxied delegation tokens


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

Ted Yu updated HBASE-6671:
--

Fix Version/s: 0.96.0
 Hadoop Flags: Reviewed
   Status: Patch Available  (was: Open)

 Kerberos authenticated super user should be able to retrieve proxied 
 delegation tokens
 --

 Key: HBASE-6671
 URL: https://issues.apache.org/jira/browse/HBASE-6671
 Project: HBase
  Issue Type: Bug
Affects Versions: 0.94.1
Reporter: Francis Liu
Assignee: Francis Liu
 Fix For: 0.96.0

 Attachments: 6671-trunk-v2.txt, proxy_fix_94.patch, 
 proxy_fix_trunk.patch


 There a services such a oozie which perform actions in behalf of the user 
 using proxy authentication. Retrieving delegation tokens should support this 
 behavior. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (HBASE-6671) Kerberos authenticated super user should be able to retrieve proxied delegation tokens


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

Ted Yu updated HBASE-6671:
--

Attachment: 6671-trunk-v2.txt

v2 addresses the above comments.

 Kerberos authenticated super user should be able to retrieve proxied 
 delegation tokens
 --

 Key: HBASE-6671
 URL: https://issues.apache.org/jira/browse/HBASE-6671
 Project: HBase
  Issue Type: Bug
Affects Versions: 0.94.1
Reporter: Francis Liu
Assignee: Francis Liu
 Fix For: 0.96.0

 Attachments: 6671-trunk-v2.txt, proxy_fix_94.patch, 
 proxy_fix_trunk.patch


 There a services such a oozie which perform actions in behalf of the user 
 using proxy authentication. Retrieving delegation tokens should support this 
 behavior. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HBASE-6586) Quarantine Corrupted HFiles


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

Hadoop QA commented on HBASE-6586:
--

-1 overall.  Here are the results of testing the latest attachment 
  
http://issues.apache.org/jira/secure/attachment/12542644/hbase-6586-trunk-v8.patch
  against trunk revision .

+1 @author.  The patch does not contain any @author tags.

+1 tests included.  The patch appears to include 12 new or modified tests.

+1 hadoop2.0.  The patch compiles against the hadoop 2.0 profile.

-1 javadoc.  The javadoc tool appears to have generated 106 warning 
messages.

-1 javac.  The applied patch generated 5 javac compiler warnings (more than 
the trunk's current 4 warnings).

-1 findbugs.  The patch appears to introduce 14 new Findbugs (version 
1.3.9) warnings.

+1 release audit.  The applied patch does not increase the total number of 
release audit warnings.

 -1 core tests.  The patch failed these unit tests:
   
org.apache.hadoop.hbase.coprocessor.TestRegionServerCoprocessorExceptionWithAbort

Test results: 
https://builds.apache.org/job/PreCommit-HBASE-Build/2705//testReport/
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/2705//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/2705//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/2705//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/2705//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/2705//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output: 
https://builds.apache.org/job/PreCommit-HBASE-Build/2705//console

This message is automatically generated.

 Quarantine Corrupted HFiles
 ---

 Key: HBASE-6586
 URL: https://issues.apache.org/jira/browse/HBASE-6586
 Project: HBase
  Issue Type: Improvement
Reporter: Jonathan Hsieh
Assignee: Jonathan Hsieh
 Attachments: 0001-hbase-6568-hbck-quarantine-v6.patch, 
 hbase-6586-92-v3.patch, hbase-6586-92-v8a.patch, hbase-6586-92-v8b.patch, 
 hbase-6586-92-v8.patch, hbase-6586-94-v3.patch, hbase-6586-94-v8.patch, 
 hbase-6586.patch, hbase-6586-trunk-v3.patch, hbase-6586-trunk-v4.patch, 
 hbase-6586-trunk-v5.patch, hbase-6586-trunk-v6.patch, 
 hbase-6586-trunk-v7.patch, hbase-6586-trunk-v8.patch


 We've encountered a few upgrades from 0.90 hbases + 20.2/1.x hdfs to 0.92 
 hbases + hdfs 2.x that get stuck.  I haven't been able to duplicate the 
 problem in my dev environment but we suspect this may be related to 
 HDFS-3731.  On the HBase side, it seems reasonable to quarantine what are 
 most likely truncated hfiles, so that can could later be recovered.
 Here's an example of the exception we've encountered:
 {code}
 2012-07-18 05:55:01,152 ERROR handler.OpenRegionHandler 
 (OpenRegionHandler.java:openRegion(346)) - Failed open of 
 region=user_mappings,080112102AA76EF98197605D341B9E6C5824D2BC|1001,1317824890618.eaed0e7abc6d27d28ff0e5a9b49c4c
 0d. 
 java.io.IOException: java.lang.IllegalArgumentException: Invalid HFile 
 version: 842220600 (expected to be between 1 and 2) 
 at 
 org.apache.hadoop.hbase.io.hfile.FixedFileTrailer.readFromStream(FixedFileTrailer.java:306)
  
 at org.apache.hadoop.hbase.io.hfile.HFile.pickReaderVersion(HFile.java:371) 
 at org.apache.hadoop.hbase.io.hfile.HFile.createReader(HFile.java:387) 
 at 
 org.apache.hadoop.hbase.regionserver.StoreFile$Reader.init(StoreFile.java:1026)
  
 at org.apache.hadoop.hbase.regionserver.StoreFile.open(StoreFile.java:485) 
 at 
 org.apache.hadoop.hbase.regionserver.StoreFile.createReader(StoreFile.java:566)
  
 at org.apache.hadoop.hbase.regionserver.Store.loadStoreFiles(Store.java:286) 
 at org.apache.hadoop.hbase.regionserver.Store.init(Store.java:223) 
 at 
 org.apache.hadoop.hbase.regionserver.HRegion.instantiateHStore(HRegion.java:2534)
  
 at org.apache.hadoop.hbase.regionserver.HRegion.initialize(HRegion.java:454) 
 at 
 org.apache.hadoop.hbase.regionserver.HRegion.openHRegion(HRegion.java:3282) 
 at 
 org.apache.hadoop.hbase.regionserver.HRegion.openHRegion(HRegion.java:3230) 
 at 
 org.apache.hadoop.hbase.regionserver.handler.OpenRegionHandler.openRegion(OpenRegionHandler.java:331)
 at 
 org.apache.hadoop.hbase.regionserver.handler.OpenRegionHandler.process(OpenRegionHandler.java:107)
 at org.apache.hadoop.hbase.executor.EventHandler.run(EventHandler.java:169) 
 at

[jira] [Commented] (HBASE-6671) Kerberos authenticated super user should be able to retrieve proxied delegation tokens


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

Francis Liu commented on HBASE-6671:


Looks good to me.

 Kerberos authenticated super user should be able to retrieve proxied 
 delegation tokens
 --

 Key: HBASE-6671
 URL: https://issues.apache.org/jira/browse/HBASE-6671
 Project: HBase
  Issue Type: Bug
Affects Versions: 0.94.1
Reporter: Francis Liu
Assignee: Francis Liu
 Fix For: 0.96.0

 Attachments: 6671-trunk-v2.txt, proxy_fix_94.patch, 
 proxy_fix_trunk.patch


 There a services such a oozie which perform actions in behalf of the user 
 using proxy authentication. Retrieving delegation tokens should support this 
 behavior. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (HBASE-6659) Port HBASE-6508 Filter out edits at log split time


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

Ted Yu updated HBASE-6659:
--

Attachment: 6508-v4.txt

 Port HBASE-6508 Filter out edits at log split time
 --

 Key: HBASE-6659
 URL: https://issues.apache.org/jira/browse/HBASE-6659
 Project: HBase
  Issue Type: Bug
Reporter: Zhihong Ted Yu
Assignee: Zhihong Ted Yu
 Fix For: 0.96.0

 Attachments: 6508-v2.txt, 6508-v3.txt, 6508-v4.txt, 6508-v4.txt


 HBASE-6508 is for 0.89-fb branch.
 This JIRA ports the feature to trunk.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (HBASE-6659) Port HBASE-6508 Filter out edits at log split time


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

Ted Yu updated HBASE-6659:
--

Attachment: (was: 6508-v4.txt)

 Port HBASE-6508 Filter out edits at log split time
 --

 Key: HBASE-6659
 URL: https://issues.apache.org/jira/browse/HBASE-6659
 Project: HBase
  Issue Type: Bug
Reporter: Zhihong Ted Yu
Assignee: Zhihong Ted Yu
 Fix For: 0.96.0

 Attachments: 6508-v2.txt, 6508-v3.txt, 6508-v4.txt, 6508-v4.txt


 HBASE-6508 is for 0.89-fb branch.
 This JIRA ports the feature to trunk.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HBASE-6477) Use PB filter definitions in RPC


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

Hudson commented on HBASE-6477:
---

Integrated in HBase-TRUNK #3283 (See 
[https://builds.apache.org/job/HBase-TRUNK/3283/])
HBASE-6477 Use PB filter definitions in RPC (Revision 1377788)

 Result = FAILURE
stack : 
Files : 
* 
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/io/HbaseObjectWritable.java
* 
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/protobuf/ProtobufUtil.java


 Use PB filter definitions in RPC
 

 Key: HBASE-6477
 URL: https://issues.apache.org/jira/browse/HBASE-6477
 Project: HBase
  Issue Type: Task
  Components: ipc, migration
Reporter: Gregory Chanan
Assignee: Gregory Chanan
 Fix For: 0.96.0

 Attachments: 6477-addendum.patch, HBASE-6477-addendum.patch, 
 HBASE-6477-nonrb.patch, HBASE-6477-nonrb-v3.patch, HBASE-6477-nonrb-v4.patch


 Use the filters introduced in HBASE-6454 in the rpc so they are extensible

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (HBASE-6080) site.xml - adding ReviewBoard to main page left-hand nav


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

stack updated HBASE-6080:
-

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

Indeed Michael.  Thanks for pointing it out.  Closing as fixed.

 site.xml - adding ReviewBoard to main page left-hand nav
 

 Key: HBASE-6080
 URL: https://issues.apache.org/jira/browse/HBASE-6080
 Project: HBase
  Issue Type: Improvement
Reporter: Doug Meil
Assignee: Doug Meil
Priority: Trivial
 Fix For: 0.96.0

 Attachments: src_hbase_6080.patch


 By request, adding ReviewBoard to left-hand nav on website

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HBASE-6643) Accept encoded region name in compacting/spliting region from shell


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

stack commented on HBASE-6643:
--

+1 on v2.

 Accept encoded region name in compacting/spliting region from shell
 ---

 Key: HBASE-6643
 URL: https://issues.apache.org/jira/browse/HBASE-6643
 Project: HBase
  Issue Type: Improvement
  Components: shell
Reporter: Jimmy Xiang
Assignee: Jimmy Xiang
 Attachments: trunk-6643.patch, trunk-6643_v2.patch


 Sometimes, the region name has binary characters. When compacting/splitting 
 it from shell, the region name is not recognized.  If we can support encoded 
 region name, it will make things easier.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (HBASE-6647) [performance regression] appendNoSync/HBASE-4528 doesn't take deferred log flush into account


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

Jean-Daniel Cryans updated HBASE-6647:
--

Attachment: HBASE-6647-0.94-v2.patch

Patch with comments.

I started reading more about what's going on since HBASE-4528 and I was this 
close to doing a massive refactoring. Just look at HLog.doWrite and tell me 
it's doing something that's actually a write operation. It's not anymore. I'm 
also wondering what we should do with the coprocs. I'll leave that for another 
jira.

 [performance regression] appendNoSync/HBASE-4528 doesn't take deferred log 
 flush into account
 -

 Key: HBASE-6647
 URL: https://issues.apache.org/jira/browse/HBASE-6647
 Project: HBase
  Issue Type: Bug
Affects Versions: 0.94.0
Reporter: Jean-Daniel Cryans
 Fix For: 0.96.0, 0.94.2

 Attachments: HBASE-6647-0.94.patch, HBASE-6647-0.94-v2.patch


 Since we upgraded to 0.94.1 from 0.92 I saw that our ICVs are about twice as 
 slow as they were. jstack'ing I saw that most of the time we are waiting on 
 sync()... but those tables have deferred log flush turned on so they 
 shouldn't even be calling it.
 HTD.isDeferredLogFlush is currently only called in the append() methods which 
 are pretty much not in use anymore.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HBASE-6647) [performance regression] appendNoSync/HBASE-4528 doesn't take deferred log flush into account


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

Lars Hofhansl commented on HBASE-6647:
--

+1 on patch and +1 on not refactoring now.

There's a small typo: old  hold

 [performance regression] appendNoSync/HBASE-4528 doesn't take deferred log 
 flush into account
 -

 Key: HBASE-6647
 URL: https://issues.apache.org/jira/browse/HBASE-6647
 Project: HBase
  Issue Type: Bug
Affects Versions: 0.94.0
Reporter: Jean-Daniel Cryans
 Fix For: 0.96.0, 0.94.2

 Attachments: HBASE-6647-0.94.patch, HBASE-6647-0.94-v2.patch


 Since we upgraded to 0.94.1 from 0.92 I saw that our ICVs are about twice as 
 slow as they were. jstack'ing I saw that most of the time we are waiting on 
 sync()... but those tables have deferred log flush turned on so they 
 shouldn't even be calling it.
 HTD.isDeferredLogFlush is currently only called in the append() methods which 
 are pretty much not in use anymore.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HBASE-6080) site.xml - adding ReviewBoard to main page left-hand nav

2012-08-27 Thread Doug Meil (JIRA)


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

Doug Meil commented on HBASE-6080:
--

Thanks!  I must have forgotten to close that out at the HBase Hackathon after I 
patched it. 

 site.xml - adding ReviewBoard to main page left-hand nav
 

 Key: HBASE-6080
 URL: https://issues.apache.org/jira/browse/HBASE-6080
 Project: HBase
  Issue Type: Improvement
Reporter: Doug Meil
Assignee: Doug Meil
Priority: Trivial
 Fix For: 0.96.0

 Attachments: src_hbase_6080.patch


 By request, adding ReviewBoard to left-hand nav on website

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (HBASE-6052) Convert .META. and -ROOT- content to pb


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

Ted Yu updated HBASE-6052:
--

Attachment: 6052_v8.patch

Patch v8 attached again.

 Convert .META. and -ROOT- content to pb
 ---

 Key: HBASE-6052
 URL: https://issues.apache.org/jira/browse/HBASE-6052
 Project: HBase
  Issue Type: Sub-task
Reporter: stack
Assignee: Enis Soztutar
Priority: Blocker
 Fix For: 0.96.0

 Attachments: 6052-v5.txt, 6052_v8.patch, HBASE-6052_v1.patch, 
 HBASE-6052_v2.patch, HBASE-6052_v3.patch, HBASE-6052_v4.patch, 
 HBASE-6052_v4.patch, HBASE-6052_v7.patch, HBASE-6052_v8.patch, 
 TestMetaMigrationConvertToPB.tgz




--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HBASE-6671) Kerberos authenticated super user should be able to retrieve proxied delegation tokens

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

Hadoop QA commented on HBASE-6671:
--

-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12542654/6671-trunk-v2.txt
against trunk revision .

+1 @author. The patch does not contain any @author tags.

+1 hadoop2.0. The patch compiles against the hadoop 2.0 profile.

-1 javadoc. The javadoc tool appears to have generated 94 warning messages.

-1 javac. The applied patch generated 5 javac compiler warnings (more than
the trunk's current 4 warnings).

-1 findbugs. The patch appears to introduce 13 new Findbugs (version
1.3.9) warnings.

+1 release audit. The applied patch does not increase the total number of
release audit warnings.

+1 core tests. The patch passed unit tests in .

Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/2706//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/2706//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/2706//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/2706//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/2706//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/2706//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/2706//console

This message is automatically generated.

Kerberos authenticated super user should be able to retrieve proxied
delegation tokens
--

Key: HBASE-6671
URL: https://issues.apache.org/jira/browse/HBASE-6671
Project: HBase
Issue Type: Bug
Affects Versions: 0.94.1
Reporter: Francis Liu
Assignee: Francis Liu
Fix For: 0.96.0

Attachments: 6671-trunk-v2.txt, proxy_fix_94.patch,
proxy_fix_trunk.patch

There a services such a oozie which perform actions in behalf of the user
using proxy authentication. Retrieving delegation tokens should support this
behavior.

[jira] [Commented] (HBASE-6671) Kerberos authenticated super user should be able to retrieve proxied delegation tokens


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

Ted Yu commented on HBASE-6671:
---

@Gary, @Andy:
Do you have further comment about Francis' patch ?

 Kerberos authenticated super user should be able to retrieve proxied 
 delegation tokens
 --

 Key: HBASE-6671
 URL: https://issues.apache.org/jira/browse/HBASE-6671
 Project: HBase
  Issue Type: Bug
Affects Versions: 0.94.1
Reporter: Francis Liu
Assignee: Francis Liu
 Fix For: 0.96.0

 Attachments: 6671-trunk-v2.txt, proxy_fix_94.patch, 
 proxy_fix_trunk.patch


 There a services such a oozie which perform actions in behalf of the user 
 using proxy authentication. Retrieving delegation tokens should support this 
 behavior. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (HBASE-6052) Convert .META. and -ROOT- content to pb

2012-08-27 Thread Enis Soztutar (JIRA)


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

Enis Soztutar updated HBASE-6052:
-

Status: Open  (was: Patch Available)

 Convert .META. and -ROOT- content to pb
 ---

 Key: HBASE-6052
 URL: https://issues.apache.org/jira/browse/HBASE-6052
 Project: HBase
  Issue Type: Sub-task
Reporter: stack
Assignee: Enis Soztutar
Priority: Blocker
 Fix For: 0.96.0

 Attachments: 6052-v5.txt, 6052_v8.patch, HBASE-6052_v1.patch, 
 HBASE-6052_v2.patch, HBASE-6052_v3.patch, HBASE-6052_v4.patch, 
 HBASE-6052_v4.patch, HBASE-6052_v7.patch, HBASE-6052_v8.patch, 
 TestMetaMigrationConvertToPB.tgz




--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (HBASE-6052) Convert .META. and -ROOT- content to pb

2012-08-27 Thread Enis Soztutar (JIRA)


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

Enis Soztutar updated HBASE-6052:
-

Status: Patch Available  (was: Open)

Let's try jenkins one more time.

 Convert .META. and -ROOT- content to pb
 ---

 Key: HBASE-6052
 URL: https://issues.apache.org/jira/browse/HBASE-6052
 Project: HBase
  Issue Type: Sub-task
Reporter: stack
Assignee: Enis Soztutar
Priority: Blocker
 Fix For: 0.96.0

 Attachments: 6052-v5.txt, 6052_v8.patch, HBASE-6052_v1.patch, 
 HBASE-6052_v2.patch, HBASE-6052_v3.patch, HBASE-6052_v4.patch, 
 HBASE-6052_v4.patch, HBASE-6052_v7.patch, HBASE-6052_v8.patch, 
 TestMetaMigrationConvertToPB.tgz




--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HBASE-6052) Convert .META. and -ROOT- content to pb


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

Hadoop QA commented on HBASE-6052:
--

-1 overall.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12542667/6052_v8.patch
  against trunk revision .

+1 @author.  The patch does not contain any @author tags.

+1 tests included.  The patch appears to include 67 new or modified tests.

-1 patch.  The patch command could not apply the patch.

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

This message is automatically generated.

 Convert .META. and -ROOT- content to pb
 ---

 Key: HBASE-6052
 URL: https://issues.apache.org/jira/browse/HBASE-6052
 Project: HBase
  Issue Type: Sub-task
Reporter: stack
Assignee: Enis Soztutar
Priority: Blocker
 Fix For: 0.96.0

 Attachments: 6052-v5.txt, 6052_v8.patch, HBASE-6052_v1.patch, 
 HBASE-6052_v2.patch, HBASE-6052_v3.patch, HBASE-6052_v4.patch, 
 HBASE-6052_v4.patch, HBASE-6052_v7.patch, HBASE-6052_v8.patch, 
 TestMetaMigrationConvertToPB.tgz




--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (HBASE-6643) Accept encoded region name in compacting/spliting region from shell

2012-08-27 Thread Jimmy Xiang (JIRA)


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

Jimmy Xiang updated HBASE-6643:
---

   Resolution: Fixed
Fix Version/s: 0.94.2
   0.96.0
 Hadoop Flags: Reviewed
   Status: Resolved  (was: Patch Available)

 Accept encoded region name in compacting/spliting region from shell
 ---

 Key: HBASE-6643
 URL: https://issues.apache.org/jira/browse/HBASE-6643
 Project: HBase
  Issue Type: Improvement
  Components: shell
Reporter: Jimmy Xiang
Assignee: Jimmy Xiang
 Fix For: 0.96.0, 0.94.2

 Attachments: trunk-6643.patch, trunk-6643_v2.patch


 Sometimes, the region name has binary characters. When compacting/splitting 
 it from shell, the region name is not recognized.  If we can support encoded 
 region name, it will make things easier.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HBASE-6643) Accept encoded region name in compacting/spliting region from shell

2012-08-27 Thread Jimmy Xiang (JIRA)


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

Jimmy Xiang commented on HBASE-6643:


Integrated into trunk(0.96) and 0.94.  Thanks Stack for the review.

 Accept encoded region name in compacting/spliting region from shell
 ---

 Key: HBASE-6643
 URL: https://issues.apache.org/jira/browse/HBASE-6643
 Project: HBase
  Issue Type: Improvement
  Components: shell
Reporter: Jimmy Xiang
Assignee: Jimmy Xiang
 Fix For: 0.96.0, 0.94.2

 Attachments: trunk-6643.patch, trunk-6643_v2.patch


 Sometimes, the region name has binary characters. When compacting/splitting 
 it from shell, the region name is not recognized.  If we can support encoded 
 region name, it will make things easier.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HBASE-6647) [performance regression] appendNoSync/HBASE-4528 doesn't take deferred log flush into account


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

stack commented on HBASE-6647:
--

+1 after making a noob issue to add a test verifying deferred works

 [performance regression] appendNoSync/HBASE-4528 doesn't take deferred log 
 flush into account
 -

 Key: HBASE-6647
 URL: https://issues.apache.org/jira/browse/HBASE-6647
 Project: HBase
  Issue Type: Bug
Affects Versions: 0.94.0
Reporter: Jean-Daniel Cryans
 Fix For: 0.96.0, 0.94.2

 Attachments: HBASE-6647-0.94.patch, HBASE-6647-0.94-v2.patch


 Since we upgraded to 0.94.1 from 0.92 I saw that our ICVs are about twice as 
 slow as they were. jstack'ing I saw that most of the time we are waiting on 
 sync()... but those tables have deferred log flush turned on so they 
 shouldn't even be calling it.
 HTD.isDeferredLogFlush is currently only called in the append() methods which 
 are pretty much not in use anymore.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (HBASE-6647) [performance regression] appendNoSync/HBASE-4528 doesn't take deferred log flush into account


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

Jean-Daniel Cryans updated HBASE-6647:
--

Attachment: HBASE-6647-0.94-v3.patch

Attaching a patch with the typo fixed. I'm going to try that along HBASE-6550 
and HBASE-6165 now.

 [performance regression] appendNoSync/HBASE-4528 doesn't take deferred log 
 flush into account
 -

 Key: HBASE-6647
 URL: https://issues.apache.org/jira/browse/HBASE-6647
 Project: HBase
  Issue Type: Bug
Affects Versions: 0.94.0
Reporter: Jean-Daniel Cryans
 Fix For: 0.96.0, 0.94.2

 Attachments: HBASE-6647-0.94.patch, HBASE-6647-0.94-v2.patch, 
 HBASE-6647-0.94-v3.patch


 Since we upgraded to 0.94.1 from 0.92 I saw that our ICVs are about twice as 
 slow as they were. jstack'ing I saw that most of the time we are waiting on 
 sync()... but those tables have deferred log flush turned on so they 
 shouldn't even be calling it.
 HTD.isDeferredLogFlush is currently only called in the append() methods which 
 are pretty much not in use anymore.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (HBASE-6598) Combine Master Metrics into a single class.


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

stack updated HBASE-6598:
-

   Resolution: Fixed
Fix Version/s: 0.96.0
 Hadoop Flags: Reviewed
   Status: Resolved  (was: Patch Available)

Committed to trunk.  Thanks Elliott.

 Combine Master Metrics into a single class.
 ---

 Key: HBASE-6598
 URL: https://issues.apache.org/jira/browse/HBASE-6598
 Project: HBase
  Issue Type: Sub-task
Affects Versions: 0.96.0
Reporter: Elliott Clark
Assignee: Elliott Clark
Priority: Blocker
 Fix For: 0.96.0

 Attachments: HBASE-6598-0.patch, HBASE-6598-1.patch, 
 HBASE-6598-2.patch, HBASE-6598-3.patch


 Rather than an MBean and a dynamic source.  Lets use just one.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HBASE-6598) Combine Master Metrics into a single class.

2012-08-27 Thread Elliott Clark (JIRA)


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

Elliott Clark commented on HBASE-6598:
--

Thanks.

 Combine Master Metrics into a single class.
 ---

 Key: HBASE-6598
 URL: https://issues.apache.org/jira/browse/HBASE-6598
 Project: HBase
  Issue Type: Sub-task
Affects Versions: 0.96.0
Reporter: Elliott Clark
Assignee: Elliott Clark
Priority: Blocker
 Fix For: 0.96.0

 Attachments: HBASE-6598-0.patch, HBASE-6598-1.patch, 
 HBASE-6598-2.patch, HBASE-6598-3.patch


 Rather than an MBean and a dynamic source.  Lets use just one.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (HBASE-5997) Fix concerns raised in HBASE-5922 related to HalfStoreFileReader


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

stack updated HBASE-5997:
-

Attachment: 5997v3_trunk.txt

 Fix concerns raised in HBASE-5922 related to HalfStoreFileReader
 

 Key: HBASE-5997
 URL: https://issues.apache.org/jira/browse/HBASE-5997
 Project: HBase
  Issue Type: Bug
Affects Versions: 0.90.6, 0.92.1, 0.94.0, 0.96.0
Reporter: ramkrishna.s.vasudevan
Assignee: Anoop Sam John
 Fix For: 0.96.0, 0.94.3

 Attachments: 5997v3_trunk.txt, 5997v3_trunk.txt, 
 HBASE-5997_0.94.patch, HBASE-5997_94 V2.patch, HBASE-5997_94 V3.patch, 
 Testcase.patch.txt


 Pls refer to the comment
 https://issues.apache.org/jira/browse/HBASE-5922?focusedCommentId=13269346page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13269346.
 Raised this issue to solve that comment. Just incase we don't forget it.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (HBASE-5997) Fix concerns raised in HBASE-5922 related to HalfStoreFileReader


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

stack updated HBASE-5997:
-

Status: Open  (was: Patch Available)

 Fix concerns raised in HBASE-5922 related to HalfStoreFileReader
 

 Key: HBASE-5997
 URL: https://issues.apache.org/jira/browse/HBASE-5997
 Project: HBase
  Issue Type: Bug
Affects Versions: 0.94.0, 0.92.1, 0.90.6, 0.96.0
Reporter: ramkrishna.s.vasudevan
Assignee: Anoop Sam John
 Fix For: 0.96.0, 0.94.3

 Attachments: 5997v3_trunk.txt, 5997v3_trunk.txt, 
 HBASE-5997_0.94.patch, HBASE-5997_94 V2.patch, HBASE-5997_94 V3.patch, 
 Testcase.patch.txt


 Pls refer to the comment
 https://issues.apache.org/jira/browse/HBASE-5922?focusedCommentId=13269346page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13269346.
 Raised this issue to solve that comment. Just incase we don't forget it.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HBASE-6643) Accept encoded region name in compacting/spliting region from shell


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

Hudson commented on HBASE-6643:
---

Integrated in HBase-0.94 #440 (See 
[https://builds.apache.org/job/HBase-0.94/440/])
HBASE-6643 Accept encoded region name in compacting/spliting region from 
shell (Revision 1377877)

 Result = FAILURE
jxiang : 
Files : 
* 
/hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/client/HBaseAdmin.java
* 
/hbase/branches/0.94/src/test/java/org/apache/hadoop/hbase/client/TestAdmin.java


 Accept encoded region name in compacting/spliting region from shell
 ---

 Key: HBASE-6643
 URL: https://issues.apache.org/jira/browse/HBASE-6643
 Project: HBase
  Issue Type: Improvement
  Components: shell
Reporter: Jimmy Xiang
Assignee: Jimmy Xiang
 Fix For: 0.96.0, 0.94.2

 Attachments: trunk-6643.patch, trunk-6643_v2.patch


 Sometimes, the region name has binary characters. When compacting/splitting 
 it from shell, the region name is not recognized.  If we can support encoded 
 region name, it will make things easier.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HBASE-6643) Accept encoded region name in compacting/spliting region from shell


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

Hudson commented on HBASE-6643:
---

Integrated in HBase-TRUNK #3285 (See 
[https://builds.apache.org/job/HBase-TRUNK/3285/])
HBASE-6643 Accept encoded region name in compacting/spliting region from 
shell (Revision 1377862)

 Result = FAILURE
jxiang : 
Files : 
* 
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/client/HBaseAdmin.java
* 
/hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/client/TestAdmin.java


 Accept encoded region name in compacting/spliting region from shell
 ---

 Key: HBASE-6643
 URL: https://issues.apache.org/jira/browse/HBASE-6643
 Project: HBase
  Issue Type: Improvement
  Components: shell
Reporter: Jimmy Xiang
Assignee: Jimmy Xiang
 Fix For: 0.96.0, 0.94.2

 Attachments: trunk-6643.patch, trunk-6643_v2.patch


 Sometimes, the region name has binary characters. When compacting/splitting 
 it from shell, the region name is not recognized.  If we can support encoded 
 region name, it will make things easier.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HBASE-6659) Port HBASE-6508 Filter out edits at log split time

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

Hadoop QA commented on HBASE-6659:
--

-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12542656/6508-v4.txt
against trunk revision .

+1 @author. The patch does not contain any @author tags.

+1 tests included. The patch appears to include 12 new or modified tests.

+1 hadoop2.0. The patch compiles against the hadoop 2.0 profile.

-1 javadoc. The javadoc tool appears to have generated 92 warning messages.

-1 javac. The applied patch generated 5 javac compiler warnings (more than
the trunk's current 4 warnings).

-1 findbugs. The patch appears to introduce 13 new Findbugs (version
1.3.9) warnings.

+1 release audit. The applied patch does not increase the total number of
release audit warnings.

-1 core tests. The patch failed these unit tests:

org.apache.hadoop.hbase.coprocessor.TestRegionServerCoprocessorExceptionWithAbort

Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/2708//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/2708//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/2708//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/2708//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/2708//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/2708//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/2708//console

This message is automatically generated.

Port HBASE-6508 Filter out edits at log split time
--

Key: HBASE-6659
URL: https://issues.apache.org/jira/browse/HBASE-6659
Project: HBase
Issue Type: Bug
Reporter: Zhihong Ted Yu
Assignee: Zhihong Ted Yu
Fix For: 0.96.0

Attachments: 6508-v2.txt, 6508-v3.txt, 6508-v4.txt, 6508-v4.txt

HBASE-6508 is for 0.89-fb branch.
This JIRA ports the feature to trunk.

[jira] [Commented] (HBASE-6165) Replication can overrun .META. scans on cluster re-start


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

Jean-Daniel Cryans commented on HBASE-6165:
---

FWIW the v4 patch really doesn't apply on 0.94:

{noformat}

su-jdcryans-2:hbase-git-su jdcryans$ patch -p1 -F 10 --dry-run  
HBase-6165-v4.patch 
patching file src/main/java/org/apache/hadoop/hbase/HConstants.java
Hunk #1 succeeded at 650 with fuzz 2 (offset -42 lines).
patching file src/main/java/org/apache/hadoop/hbase/ipc/HBaseRpcMetrics.java
Hunk #1 succeeded at 98 (offset -11 lines).
patching file src/main/java/org/apache/hadoop/hbase/ipc/HBaseServer.java
Hunk #1 succeeded at 225 (offset -51 lines).
Hunk #2 succeeded at 1304 (offset -360 lines).
Hunk #3 succeeded at 1335 with fuzz 1 (offset -414 lines).
Hunk #4 succeeded at 1356 (offset -415 lines).
Hunk #5 succeeded at 1526 (offset -405 lines).
Hunk #6 succeeded at 1630 with fuzz 3 (offset -415 lines).
Hunk #7 succeeded at 1652 (offset -423 lines).
Hunk #8 succeeded at 1664 (offset -423 lines).
patching file 
src/main/java/org/apache/hadoop/hbase/regionserver/HRegionServer.java
Hunk #1 succeeded at 449 with fuzz 2 (offset 153 lines).
Hunk #2 FAILED at 658.
Hunk #3 succeeded at 486 (offset -87 lines).
Hunk #4 succeeded at 504 (offset -87 lines).
Hunk #5 succeeded at 520 (offset -87 lines).
Hunk #6 succeeded at 536 (offset -87 lines).
Hunk #7 succeeded at 3159 (offset 1061 lines).
Hunk #8 succeeded at 3170 with fuzz 1 (offset 1059 lines).
Hunk #9 succeeded at 3630 with fuzz 3 (offset 529 lines).
Hunk #10 FAILED at 3836.
Hunk #11 FAILED at 3883.
Hunk #12 FAILED at 3911.
Hunk #13 FAILED at 3998.
Hunk #14 FAILED at 4037.
Hunk #15 FAILED at 4068.
Hunk #16 FAILED at 4097.
Hunk #17 FAILED at 4131.
9 out of 17 hunks FAILED -- saving rejects to file 
src/main/java/org/apache/hadoop/hbase/regionserver/HRegionServer.java.rej
{noformat}

 Replication can overrun .META. scans on cluster re-start
 

 Key: HBASE-6165
 URL: https://issues.apache.org/jira/browse/HBASE-6165
 Project: HBase
  Issue Type: Bug
Reporter: Elliott Clark
Assignee: Himanshu Vashishtha
 Fix For: 0.96.0, 0.94.2

 Attachments: HBase-6165-v1.patch, HBase-6165-v2.patch, 
 HBase-6165-v3.patch, HBase-6165-v4.patch


 When restarting a large set of regions on a reasonably small cluster the 
 replication from another cluster tied up every xceiver meaning nothing could 
 be onlined.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HBASE-6165) Replication can overrun .META. scans on cluster re-start

2012-08-27 Thread Himanshu Vashishtha (JIRA)


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

Himanshu Vashishtha commented on HBASE-6165:


The above patch was for trunk;
will upload a 0.94 one.

 Replication can overrun .META. scans on cluster re-start
 

 Key: HBASE-6165
 URL: https://issues.apache.org/jira/browse/HBASE-6165
 Project: HBase
  Issue Type: Bug
Reporter: Elliott Clark
Assignee: Himanshu Vashishtha
 Fix For: 0.96.0, 0.94.2

 Attachments: HBase-6165-v1.patch, HBase-6165-v2.patch, 
 HBase-6165-v3.patch, HBase-6165-v4.patch


 When restarting a large set of regions on a reasonably small cluster the 
 replication from another cluster tied up every xceiver meaning nothing could 
 be onlined.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (HBASE-5997) Fix concerns raised in HBASE-5922 related to HalfStoreFileReader


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

stack updated HBASE-5997:
-

Status: Patch Available  (was: Open)

Try against hadoopqa again.  Uses deprecated API but nothing yet that can be 
used in its stead (can work on this when we remove the deprecated API).

 Fix concerns raised in HBASE-5922 related to HalfStoreFileReader
 

 Key: HBASE-5997
 URL: https://issues.apache.org/jira/browse/HBASE-5997
 Project: HBase
  Issue Type: Bug
Affects Versions: 0.94.0, 0.92.1, 0.90.6, 0.96.0
Reporter: ramkrishna.s.vasudevan
Assignee: Anoop Sam John
 Fix For: 0.96.0, 0.94.3

 Attachments: 5997v3_trunk.txt, 5997v3_trunk.txt, 
 HBASE-5997_0.94.patch, HBASE-5997_94 V2.patch, HBASE-5997_94 V3.patch, 
 Testcase.patch.txt


 Pls refer to the comment
 https://issues.apache.org/jira/browse/HBASE-5922?focusedCommentId=13269346page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13269346.
 Raised this issue to solve that comment. Just incase we don't forget it.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HBASE-6550) Refactoring ReplicationSink to make it more responsive of cluster health


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

Jean-Daniel Cryans commented on HBASE-6550:
---

The 0.94 patch uses Threads.newDaemonThreadFactory I can't really find anywhere.

 Refactoring ReplicationSink to make it more responsive of cluster health
 

 Key: HBASE-6550
 URL: https://issues.apache.org/jira/browse/HBASE-6550
 Project: HBase
  Issue Type: New Feature
  Components: replication
Reporter: Himanshu Vashishtha
Assignee: Himanshu Vashishtha
 Fix For: 0.96.0, 0.94.2

 Attachments: 6550-havealook.txt, HBase-6550-0.94.patch, 
 HBase-6550.patch, HBase-6550-v1.patch, HBase-6550-v3.patch, 
 HBase-6550-v4.patch


 ReplicationSink replicates the WALEdits in the local cluster. It uses native 
 HBase client to insert the mutations. Sometime, it takes a while to process 
 it (may be due to region splitting, gc pause, etc) and it undergoes the 
 retrial phase. 
 It has two repercussions:
 a) The regionserver handler which is serving the request (till now, a 
 priority handler) is blocked for this period.
 b) The caller may get timed out and it will retry it anyway, but the handler 
 serving the ReplicationSink requests is still working.
 Refactoring ReplicationSink to have the following features:
 a) Making it more configurable (have its own number of retrial limit, 
 connection timeout, etc)
 b) Add a fail fast behavior so that it bails out in case caller is timedout, 
 or any exception in processing the mutation batch.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HBASE-6550) Refactoring ReplicationSink to make it more responsive of cluster health


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

Jean-Daniel Cryans commented on HBASE-6550:
---

Ah ok I see it now, it was from a recent patch.

 Refactoring ReplicationSink to make it more responsive of cluster health
 

 Key: HBASE-6550
 URL: https://issues.apache.org/jira/browse/HBASE-6550
 Project: HBase
  Issue Type: New Feature
  Components: replication
Reporter: Himanshu Vashishtha
Assignee: Himanshu Vashishtha
 Fix For: 0.96.0, 0.94.2

 Attachments: 6550-havealook.txt, HBase-6550-0.94.patch, 
 HBase-6550.patch, HBase-6550-v1.patch, HBase-6550-v3.patch, 
 HBase-6550-v4.patch


 ReplicationSink replicates the WALEdits in the local cluster. It uses native 
 HBase client to insert the mutations. Sometime, it takes a while to process 
 it (may be due to region splitting, gc pause, etc) and it undergoes the 
 retrial phase. 
 It has two repercussions:
 a) The regionserver handler which is serving the request (till now, a 
 priority handler) is blocked for this period.
 b) The caller may get timed out and it will retry it anyway, but the handler 
 serving the ReplicationSink requests is still working.
 Refactoring ReplicationSink to have the following features:
 a) Making it more configurable (have its own number of retrial limit, 
 connection timeout, etc)
 b) Add a fail fast behavior so that it bails out in case caller is timedout, 
 or any exception in processing the mutation batch.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HBASE-6586) Quarantine Corrupted HFiles


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

Jonathan Hsieh commented on HBASE-6586:
---

On build 2703, two tests hung:

{code}
./findHangingTest.sh 
https://builds.apache.org/job/PreCommit-HBASE-Build/2703/console
Hanging test: Running org.apache.hadoop.hbase.master.TestDistributedLogSplitting
Hanging test: Running org.apache.hadoop.hbase.rest.TestScannersWithFilters
{code}

On build 2705, the test passes for me locally.  

I believe these are flakey.

I've run them all locally on 94/trunk and they all basically pass.  The 92 
version sees to semi-frequently hangs/bails on TestMergeTool.  This has been 
taking 5 minutes in 94, and 8 mins in 92).  I don't think these are related.


 Quarantine Corrupted HFiles
 ---

 Key: HBASE-6586
 URL: https://issues.apache.org/jira/browse/HBASE-6586
 Project: HBase
  Issue Type: Improvement
Reporter: Jonathan Hsieh
Assignee: Jonathan Hsieh
 Attachments: 0001-hbase-6568-hbck-quarantine-v6.patch, 
 hbase-6586-92-v3.patch, hbase-6586-92-v8a.patch, hbase-6586-92-v8b.patch, 
 hbase-6586-92-v8.patch, hbase-6586-94-v3.patch, hbase-6586-94-v8.patch, 
 hbase-6586.patch, hbase-6586-trunk-v3.patch, hbase-6586-trunk-v4.patch, 
 hbase-6586-trunk-v5.patch, hbase-6586-trunk-v6.patch, 
 hbase-6586-trunk-v7.patch, hbase-6586-trunk-v8.patch


 We've encountered a few upgrades from 0.90 hbases + 20.2/1.x hdfs to 0.92 
 hbases + hdfs 2.x that get stuck.  I haven't been able to duplicate the 
 problem in my dev environment but we suspect this may be related to 
 HDFS-3731.  On the HBase side, it seems reasonable to quarantine what are 
 most likely truncated hfiles, so that can could later be recovered.
 Here's an example of the exception we've encountered:
 {code}
 2012-07-18 05:55:01,152 ERROR handler.OpenRegionHandler 
 (OpenRegionHandler.java:openRegion(346)) - Failed open of 
 region=user_mappings,080112102AA76EF98197605D341B9E6C5824D2BC|1001,1317824890618.eaed0e7abc6d27d28ff0e5a9b49c4c
 0d. 
 java.io.IOException: java.lang.IllegalArgumentException: Invalid HFile 
 version: 842220600 (expected to be between 1 and 2) 
 at 
 org.apache.hadoop.hbase.io.hfile.FixedFileTrailer.readFromStream(FixedFileTrailer.java:306)
  
 at org.apache.hadoop.hbase.io.hfile.HFile.pickReaderVersion(HFile.java:371) 
 at org.apache.hadoop.hbase.io.hfile.HFile.createReader(HFile.java:387) 
 at 
 org.apache.hadoop.hbase.regionserver.StoreFile$Reader.init(StoreFile.java:1026)
  
 at org.apache.hadoop.hbase.regionserver.StoreFile.open(StoreFile.java:485) 
 at 
 org.apache.hadoop.hbase.regionserver.StoreFile.createReader(StoreFile.java:566)
  
 at org.apache.hadoop.hbase.regionserver.Store.loadStoreFiles(Store.java:286) 
 at org.apache.hadoop.hbase.regionserver.Store.init(Store.java:223) 
 at 
 org.apache.hadoop.hbase.regionserver.HRegion.instantiateHStore(HRegion.java:2534)
  
 at org.apache.hadoop.hbase.regionserver.HRegion.initialize(HRegion.java:454) 
 at 
 org.apache.hadoop.hbase.regionserver.HRegion.openHRegion(HRegion.java:3282) 
 at 
 org.apache.hadoop.hbase.regionserver.HRegion.openHRegion(HRegion.java:3230) 
 at 
 org.apache.hadoop.hbase.regionserver.handler.OpenRegionHandler.openRegion(OpenRegionHandler.java:331)
 at 
 org.apache.hadoop.hbase.regionserver.handler.OpenRegionHandler.process(OpenRegionHandler.java:107)
 at org.apache.hadoop.hbase.executor.EventHandler.run(EventHandler.java:169) 
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
  
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
  
 at java.lang.Thread.run(Thread.java:619) 
 Caused by: java.lang.IllegalArgumentException: Invalid HFile version: 
 842220600 (expected to be between 1 and 2) 
 at org.apache.hadoop.hbase.io.hfile.HFile.checkFormatVersion(HFile.java:515) 
 at 
 org.apache.hadoop.hbase.io.hfile.FixedFileTrailer.readFromStream(FixedFileTrailer.java:303)
  
 ... 17 more
 {code}
 Specifically -- the FixedFileTrailer are incorrect, and seemingly missing.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HBASE-4421) [hbck] Verify and test the the number of regions is correct.


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

Jesse Yates commented on HBASE-4421:


@Jon is this still valid? Seems like it should have been subsummed in the 
current testing.

 [hbck] Verify and test the the number of regions is correct.
 

 Key: HBASE-4421
 URL: https://issues.apache.org/jira/browse/HBASE-4421
 Project: HBase
  Issue Type: Task
  Components: hbck
Affects Versions: 0.90.5, 0.94.0
Reporter: Jonathan Hsieh

 HBASE-4322 updated the algorithm behind hbck's region split problem detection 
 but it may be report the an incorrect number of total regions.  Need to 
 investigate and add a test.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HBASE-4436) Remove methods deprecated in 0.90 from TRUNK and 0.92


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

Jesse Yates commented on HBASE-4436:


How much is left on this? Should we even still keep it open, especially given 
that we cut 0.94?

 Remove methods deprecated in 0.90 from TRUNK and 0.92
 -

 Key: HBASE-4436
 URL: https://issues.apache.org/jira/browse/HBASE-4436
 Project: HBase
  Issue Type: Task
Reporter: stack
Assignee: Jonathan Hsieh
  Labels: noob
 Fix For: 0.92.3


 Remove methods deprecated in 0.90 from codebase.  i took a quick look.  The 
 messy bit is thrift referring to old stuff; will take a little work to do the 
 convertion over to the new methods.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (HBASE-6580) New HTable pool, based on HBase(byte[], HConnection, ExecutorService) constructor


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

Lars Hofhansl updated HBASE-6580:
-

Fix Version/s: (was: 0.94.2)
   (was: 0.96.0)
   Issue Type: Improvement  (was: Bug)

I likely won't get time to on this.

 New HTable pool, based on HBase(byte[], HConnection, ExecutorService) 
 constructor
 -

 Key: HBASE-6580
 URL: https://issues.apache.org/jira/browse/HBASE-6580
 Project: HBase
  Issue Type: Improvement
Reporter: Lars Hofhansl
Priority: Minor

 Here I propose a very simple TablePool.
 It could be called LightHTablePool (or something - if you have a better name).
 Internally it would maintain an HConnection and an Executor service and each 
 invocation of getTable(...) would create a new HTable and close() would just 
 close it.
 In testing I find this more light weight than HTablePool and easier to 
 monitor in terms of resources used.
 It would hardly be more than a few dozen lines of code.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (HBASE-6330) TestImportExport has been failing against hadoop 0.23/2.0 profile [Part2]


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

Lars Hofhansl updated HBASE-6330:
-

Fix Version/s: (was: 0.94.2)
   0.94.3

Pushing into the 0.94.3 train

 TestImportExport has been failing against hadoop 0.23/2.0 profile [Part2]
 -

 Key: HBASE-6330
 URL: https://issues.apache.org/jira/browse/HBASE-6330
 Project: HBase
  Issue Type: Sub-task
  Components: test
Affects Versions: 0.96.0, 0.94.1
Reporter: Jonathan Hsieh
Assignee: Jonathan Hsieh
Priority: Critical
  Labels: hadoop-2.0
 Fix For: 0.96.0, 0.94.3

 Attachments: hbase-6330-94.patch, hbase-6330-trunk.patch, 
 hbase-6330-v2.patch


 See HBASE-5876.  I'm going to commit the v3 patches under this name since 
 there has been two months (my bad) since the first half was committed and 
 found to be incomplte.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (HBASE-6305) TestLocalHBaseCluster hangs with hadoop 2.0/0.23 builds.


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

Lars Hofhansl updated HBASE-6305:
-

Fix Version/s: (was: 0.94.2)
   0.94.3

Pushing into the 0.94.3 train

 TestLocalHBaseCluster hangs with hadoop 2.0/0.23 builds.
 

 Key: HBASE-6305
 URL: https://issues.apache.org/jira/browse/HBASE-6305
 Project: HBase
  Issue Type: Bug
  Components: test
Affects Versions: 0.92.2, 0.94.1
Reporter: Jonathan Hsieh
Assignee: Jonathan Hsieh
Priority: Critical
 Fix For: 0.92.2, 0.94.3

 Attachments: hbase-6305-94.patch


 trunk: mvn clean test -Dhadoop.profile=2.0 -Dtest=TestLocalHBaseCluster
 0.94: mvn clean test -Dhadoop.profile=23 -Dtest=TestLocalHBaseCluster
 {code}
 testLocalHBaseCluster(org.apache.hadoop.hbase.TestLocalHBaseCluster)  Time 
 elapsed: 0.022 sec   ERROR!
 java.lang.RuntimeException: Master not initialized after 200 seconds
 at 
 org.apache.hadoop.hbase.util.JVMClusterUtil.startup(JVMClusterUtil.java:208)
 at 
 org.apache.hadoop.hbase.LocalHBaseCluster.startup(LocalHBaseCluster.java:424)
 at 
 org.apache.hadoop.hbase.TestLocalHBaseCluster.testLocalHBaseCluster(TestLocalHBaseCluster.java:66)
 ...
 {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (HBASE-6307) Fix hbase unit tests running on hadoop 2.0


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

Lars Hofhansl updated HBASE-6307:
-

Fix Version/s: (was: 0.94.2)
   0.94.3

Pushing into the 0.94.3 train

 Fix hbase unit tests running on hadoop 2.0
 --

 Key: HBASE-6307
 URL: https://issues.apache.org/jira/browse/HBASE-6307
 Project: HBase
  Issue Type: Umbrella
Reporter: Jonathan Hsieh
Priority: Critical
 Fix For: 0.96.0, 0.94.3


 This is an umbrella issue for fixing unit tests and hbase builds form 0.92+ 
 on top of hadoop 0.23 (currently 0.92/0.94) and hadoop 2.0.x (trunk/0.96).  
 Once these are up and passing properly, we'll close out the umbrella issue by 
 adding hbase-trunk-on-hadoop-2 build to the hadoopqa bot.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (HBASE-6165) Replication can overrun .META. scans on cluster re-start

2012-08-27 Thread Himanshu Vashishtha (JIRA)


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

Himanshu Vashishtha updated HBASE-6165:
---

Attachment: HBase-6165-94-v1.patch

0.94 patch

 Replication can overrun .META. scans on cluster re-start
 

 Key: HBASE-6165
 URL: https://issues.apache.org/jira/browse/HBASE-6165
 Project: HBase
  Issue Type: Bug
Reporter: Elliott Clark
Assignee: Himanshu Vashishtha
 Fix For: 0.96.0, 0.94.2

 Attachments: HBase-6165-94-v1.patch, HBase-6165-v1.patch, 
 HBase-6165-v2.patch, HBase-6165-v3.patch, HBase-6165-v4.patch


 When restarting a large set of regions on a reasonably small cluster the 
 replication from another cluster tied up every xceiver meaning nothing could 
 be onlined.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HBASE-6294) Detect leftover data in ZK after a user delete all its HBase data


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

Lars Hofhansl commented on HBASE-6294:
--

I think this can be moved to 0.94.3 (unless somebody has a concrete plan about 
what to do here).

 Detect leftover data in ZK after a user delete all its HBase data
 -

 Key: HBASE-6294
 URL: https://issues.apache.org/jira/browse/HBASE-6294
 Project: HBase
  Issue Type: Improvement
Affects Versions: 0.94.0
Reporter: Jean-Daniel Cryans
Priority: Critical
 Fix For: 0.96.0, 0.94.2


 It seems we have a new failure mode when a user deletes the hbase root.dir 
 but doesn't delete the ZK data. For example a user on IRC came with this log:
 {noformat}
 2012-06-30 09:07:48,017 INFO 
 org.apache.hadoop.hbase.regionserver.HRegionServer: Received request to open 
 region: kw,,1340981821308.2e8a318837602c9c9961e9d690b7fd02.
 2012-06-30 09:07:48,017 WARN org.apache.hadoop.hbase.util.FSTableDescriptors: 
 The following folder is in HBase's root directory and doesn't contain a table 
 descriptor, do consider deleting it: kw
 2012-06-30 09:07:48,018 DEBUG org.apache.hadoop.hbase.zookeeper.ZKAssign: 
 regionserver:34193-0x1383bfe01b70001 Attempting to transition node 
 2e8a318837602c9c9961e9d690b7fd02 from M_ZK_REGION_OFFLINE to 
 RS_ZK_REGION_OPENING
 2012-06-30 09:07:48,018 DEBUG 
 org.apache.hadoop.hbase.master.AssignmentManager: Handling 
 transition=M_ZK_REGION_OFFLINE, server=localhost,50890,1341036299694, 
 region=2e8a318837602c9c9961e9d690b7fd02
 2012-06-30 09:07:48,020 DEBUG 
 org.apache.hadoop.hbase.master.AssignmentManager: Handling 
 transition=RS_ZK_REGION_FAILED_OPEN, server=localhost,34193,1341036300138, 
 region=b254af24c9127b8bb22cb6d24e523dad
 2012-06-30 09:07:48,020 DEBUG 
 org.apache.hadoop.hbase.master.handler.ClosedRegionHandler: Handling CLOSED 
 event for b254af24c9127b8bb22cb6d24e523dad
 2012-06-30 09:07:48,020 DEBUG 
 org.apache.hadoop.hbase.master.AssignmentManager: Forcing OFFLINE; 
 was=kw_r,,1340981822374.b254af24c9127b8bb22cb6d24e523dad. state=CLOSED, 
 ts=1341036467998, server=localhost,34193,1341036300138
 2012-06-30 09:07:48,020 DEBUG org.apache.hadoop.hbase.zookeeper.ZKAssign: 
 master:50890-0x1383bfe01b7 Creating (or updating) unassigned node for 
 b254af24c9127b8bb22cb6d24e523dad with OFFLINE state
 2012-06-30 09:07:48,028 DEBUG org.apache.hadoop.hbase.zookeeper.ZKAssign: 
 regionserver:34193-0x1383bfe01b70001 Successfully transitioned node 
 2e8a318837602c9c9961e9d690b7fd02 from M_ZK_REGION_OFFLINE to 
 RS_ZK_REGION_OPENING
 2012-06-30 09:07:48,028 DEBUG org.apache.hadoop.hbase.regionserver.HRegion: 
 Opening region: {NAME = 
 'kw,,1340981821308.2e8a318837602c9c9961e9d690b7fd02.', STARTKEY = '', ENDKEY 
 = '', ENCODED = 2e8a318837602c9c9961e9d690b7fd02,}
 2012-06-30 09:07:48,029 ERROR 
 org.apache.hadoop.hbase.regionserver.handler.OpenRegionHandler: Failed open 
 of region=kw,,1340981821308.2e8a318837602c9c9961e9d690b7fd02., starting to 
 roll back the global memstore size.
 java.lang.IllegalStateException: Could not instantiate a region instance.
   at 
 org.apache.hadoop.hbase.regionserver.HRegion.newHRegion(HRegion.java:3490)
   at 
 org.apache.hadoop.hbase.regionserver.HRegion.openHRegion(HRegion.java:3628)
   at 
 org.apache.hadoop.hbase.regionserver.handler.OpenRegionHandler.openRegion(OpenRegionHandler.java:332)
   at 
 org.apache.hadoop.hbase.regionserver.handler.OpenRegionHandler.process(OpenRegionHandler.java:108)
   at 
 org.apache.hadoop.hbase.executor.EventHandler.run(EventHandler.java:169)
   at 
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
   at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
   at java.lang.Thread.run(Thread.java:679)
 Caused by: java.lang.reflect.InvocationTargetException
   at sun.reflect.GeneratedConstructorAccessor15.newInstance(Unknown 
 Source)
   at 
 sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
   at java.lang.reflect.Constructor.newInstance(Constructor.java:532)
   at 
 org.apache.hadoop.hbase.regionserver.HRegion.newHRegion(HRegion.java:3487)
   ... 7 more
 Caused by: java.lang.NullPointerException
   at 
 org.apache.hadoop.hbase.regionserver.RegionCoprocessorHost.loadTableCoprocessors(RegionCoprocessorHost.java:133)
   at 
 org.apache.hadoop.hbase.regionserver.RegionCoprocessorHost.init(RegionCoprocessorHost.java:125)
   at org.apache.hadoop.hbase.regionserver.HRegion.init(HRegion.java:411)
   ... 11 more
 2012-06-30 09:07:48,031 INFO 
 org.apache.hadoop.hbase.regionserver.handler.OpenRegionHandler: Opening of 
 region {NAME =

[jira] [Updated] (HBASE-6586) Quarantine Corrupted HFiles with hbck


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

Jonathan Hsieh updated HBASE-6586:
--

Summary: Quarantine Corrupted HFiles with hbck  (was: Quarantine Corrupted 
HFiles)

 Quarantine Corrupted HFiles with hbck
 -

 Key: HBASE-6586
 URL: https://issues.apache.org/jira/browse/HBASE-6586
 Project: HBase
  Issue Type: Improvement
Reporter: Jonathan Hsieh
Assignee: Jonathan Hsieh
 Attachments: 0001-hbase-6568-hbck-quarantine-v6.patch, 
 hbase-6586-92-v3.patch, hbase-6586-92-v8a.patch, hbase-6586-92-v8b.patch, 
 hbase-6586-92-v8.patch, hbase-6586-94-v3.patch, hbase-6586-94-v8.patch, 
 hbase-6586.patch, hbase-6586-trunk-v3.patch, hbase-6586-trunk-v4.patch, 
 hbase-6586-trunk-v5.patch, hbase-6586-trunk-v6.patch, 
 hbase-6586-trunk-v7.patch, hbase-6586-trunk-v8.patch


 We've encountered a few upgrades from 0.90 hbases + 20.2/1.x hdfs to 0.92 
 hbases + hdfs 2.x that get stuck.  I haven't been able to duplicate the 
 problem in my dev environment but we suspect this may be related to 
 HDFS-3731.  On the HBase side, it seems reasonable to quarantine what are 
 most likely truncated hfiles, so that can could later be recovered.
 Here's an example of the exception we've encountered:
 {code}
 2012-07-18 05:55:01,152 ERROR handler.OpenRegionHandler 
 (OpenRegionHandler.java:openRegion(346)) - Failed open of 
 region=user_mappings,080112102AA76EF98197605D341B9E6C5824D2BC|1001,1317824890618.eaed0e7abc6d27d28ff0e5a9b49c4c
 0d. 
 java.io.IOException: java.lang.IllegalArgumentException: Invalid HFile 
 version: 842220600 (expected to be between 1 and 2) 
 at 
 org.apache.hadoop.hbase.io.hfile.FixedFileTrailer.readFromStream(FixedFileTrailer.java:306)
  
 at org.apache.hadoop.hbase.io.hfile.HFile.pickReaderVersion(HFile.java:371) 
 at org.apache.hadoop.hbase.io.hfile.HFile.createReader(HFile.java:387) 
 at 
 org.apache.hadoop.hbase.regionserver.StoreFile$Reader.init(StoreFile.java:1026)
  
 at org.apache.hadoop.hbase.regionserver.StoreFile.open(StoreFile.java:485) 
 at 
 org.apache.hadoop.hbase.regionserver.StoreFile.createReader(StoreFile.java:566)
  
 at org.apache.hadoop.hbase.regionserver.Store.loadStoreFiles(Store.java:286) 
 at org.apache.hadoop.hbase.regionserver.Store.init(Store.java:223) 
 at 
 org.apache.hadoop.hbase.regionserver.HRegion.instantiateHStore(HRegion.java:2534)
  
 at org.apache.hadoop.hbase.regionserver.HRegion.initialize(HRegion.java:454) 
 at 
 org.apache.hadoop.hbase.regionserver.HRegion.openHRegion(HRegion.java:3282) 
 at 
 org.apache.hadoop.hbase.regionserver.HRegion.openHRegion(HRegion.java:3230) 
 at 
 org.apache.hadoop.hbase.regionserver.handler.OpenRegionHandler.openRegion(OpenRegionHandler.java:331)
 at 
 org.apache.hadoop.hbase.regionserver.handler.OpenRegionHandler.process(OpenRegionHandler.java:107)
 at org.apache.hadoop.hbase.executor.EventHandler.run(EventHandler.java:169) 
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
  
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
  
 at java.lang.Thread.run(Thread.java:619) 
 Caused by: java.lang.IllegalArgumentException: Invalid HFile version: 
 842220600 (expected to be between 1 and 2) 
 at org.apache.hadoop.hbase.io.hfile.HFile.checkFormatVersion(HFile.java:515) 
 at 
 org.apache.hadoop.hbase.io.hfile.FixedFileTrailer.readFromStream(FixedFileTrailer.java:303)
  
 ... 17 more
 {code}
 Specifically -- the FixedFileTrailer are incorrect, and seemingly missing.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (HBASE-6412) Move external servers to metrics2 (thrift,thrift2,rest)

2012-08-27 Thread Elliott Clark (JIRA)


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

Elliott Clark updated HBASE-6412:
-

Attachment: HBASE-6412-0.patch

This patch adds Thrift, Thrift2, and Rest metrics2 implementations.

It also added tests classes for metrics2.  I didn't use hadoop's as they were 
missing some of the asserts that I would need.  And these versions make 
debugging a little bit easier as they have all metrics in a map.

This patch still needs some javadocs all over the place but I wanted to get it 
up so people could comment on the general direction.

 Move external servers to metrics2 (thrift,thrift2,rest)
 ---

 Key: HBASE-6412
 URL: https://issues.apache.org/jira/browse/HBASE-6412
 Project: HBase
  Issue Type: Sub-task
Affects Versions: 0.96.0
Reporter: Elliott Clark
Priority: Blocker
 Attachments: HBASE-6412-0.patch


 Implement metrics2 for all the external servers:
 * Thrift
 * Thrift2
 * Rest

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HBASE-6643) Accept encoded region name in compacting/spliting region from shell


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

Hudson commented on HBASE-6643:
---

Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #151 (See 
[https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/151/])
HBASE-6643 Accept encoded region name in compacting/spliting region from 
shell (Revision 1377862)

 Result = FAILURE
jxiang : 
Files : 
* 
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/client/HBaseAdmin.java
* 
/hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/client/TestAdmin.java


 Accept encoded region name in compacting/spliting region from shell
 ---

 Key: HBASE-6643
 URL: https://issues.apache.org/jira/browse/HBASE-6643
 Project: HBase
  Issue Type: Improvement
  Components: shell
Reporter: Jimmy Xiang
Assignee: Jimmy Xiang
 Fix For: 0.96.0, 0.94.2

 Attachments: trunk-6643.patch, trunk-6643_v2.patch


 Sometimes, the region name has binary characters. When compacting/splitting 
 it from shell, the region name is not recognized.  If we can support encoded 
 region name, it will make things easier.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HBASE-6477) Use PB filter definitions in RPC


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

Hudson commented on HBASE-6477:
---

Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #151 (See 
[https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/151/])
HBASE-6477 Use PB filter definitions in RPC (Revision 1377788)

 Result = FAILURE
stack : 
Files : 
* 
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/io/HbaseObjectWritable.java
* 
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/protobuf/ProtobufUtil.java


 Use PB filter definitions in RPC
 

 Key: HBASE-6477
 URL: https://issues.apache.org/jira/browse/HBASE-6477
 Project: HBase
  Issue Type: Task
  Components: ipc, migration
Reporter: Gregory Chanan
Assignee: Gregory Chanan
 Fix For: 0.96.0

 Attachments: 6477-addendum.patch, HBASE-6477-addendum.patch, 
 HBASE-6477-nonrb.patch, HBASE-6477-nonrb-v3.patch, HBASE-6477-nonrb-v4.patch


 Use the filters introduced in HBASE-6454 in the rpc so they are extensible

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HBASE-4050) Update HBase metrics framework to metrics2 framework


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

Hudson commented on HBASE-4050:
---

Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #151 (See 
[https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/151/])
HBASE-4050 Combine Master Metrics into a single class (Revision 1377896)

 Result = FAILURE
stack : 
Files : 
* 
/hbase/trunk/hbase-hadoop-compat/src/main/java/org/apache/hadoop/hbase/master/metrics/MasterMetricsSource.java
* 
/hbase/trunk/hbase-hadoop-compat/src/main/java/org/apache/hadoop/hbase/master/metrics/MasterMetricsSourceFactory.java
* 
/hbase/trunk/hbase-hadoop-compat/src/main/java/org/apache/hadoop/hbase/master/metrics/MasterMetricsWrapper.java
* 
/hbase/trunk/hbase-hadoop-compat/src/main/java/org/apache/hadoop/hbase/replication/regionserver/metrics/ReplicationMetricsSource.java
* 
/hbase/trunk/hbase-hadoop1-compat/src/main/java/org/apache/hadoop/hbase/master/metrics/MasterMetricsSourceFactoryImpl.java
* 
/hbase/trunk/hbase-hadoop1-compat/src/main/java/org/apache/hadoop/hbase/master/metrics/MasterMetricsSourceImpl.java
* 
/hbase/trunk/hbase-hadoop1-compat/src/main/java/org/apache/hadoop/hbase/metrics/BaseMetricsSourceImpl.java
* 
/hbase/trunk/hbase-hadoop1-compat/src/main/java/org/apache/hadoop/hbase/replication/regionserver/metrics/ReplicationMetricsSourceImpl.java
* 
/hbase/trunk/hbase-hadoop1-compat/src/main/resources/META-INF/services/org.apache.hadoop.hbase.master.metrics.MasterMetricsSource
* 
/hbase/trunk/hbase-hadoop1-compat/src/main/resources/META-INF/services/org.apache.hadoop.hbase.master.metrics.MasterMetricsSourceFactory
* 
/hbase/trunk/hbase-hadoop1-compat/src/test/java/org/apache/hadoop/hbase/master/metrics/MasterMetricsSourceImplTest.java
* 
/hbase/trunk/hbase-hadoop1-compat/src/test/java/org/apache/hadoop/hbase/metrics/BaseMetricsSourceImplTest.java
* 
/hbase/trunk/hbase-hadoop2-compat/src/main/java/org/apache/hadoop/hbase/master/metrics/MasterMetricsSourceFactoryImpl.java
* 
/hbase/trunk/hbase-hadoop2-compat/src/main/java/org/apache/hadoop/hbase/master/metrics/MasterMetricsSourceImpl.java
* 
/hbase/trunk/hbase-hadoop2-compat/src/main/java/org/apache/hadoop/hbase/metrics/BaseMetricsSourceImpl.java
* 
/hbase/trunk/hbase-hadoop2-compat/src/main/java/org/apache/hadoop/hbase/replication/regionserver/metrics/ReplicationMetricsSourceImpl.java
* 
/hbase/trunk/hbase-hadoop2-compat/src/main/resources/META-INF/services/org.apache.hadoop.hbase.master.metrics.MasterMetricsSource
* 
/hbase/trunk/hbase-hadoop2-compat/src/main/resources/META-INF/services/org.apache.hadoop.hbase.master.metrics.MasterMetricsSourceFactory
* 
/hbase/trunk/hbase-hadoop2-compat/src/test/java/org/apache/hadoop/hbase/master/metrics/MasterMetricsSourceImplTest.java
* 
/hbase/trunk/hbase-hadoop2-compat/src/test/java/org/apache/hadoop/hbase/metrics/BaseMetricsSourceImplTest.java
* 
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/master/HMaster.java
* 
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/master/metrics/MXBean.java
* 
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/master/metrics/MXBeanImpl.java
* 
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/master/metrics/MasterMetrics.java
* 
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/master/metrics/MasterMetricsWrapperImpl.java
* 
/hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/master/TestMXBean.java
* /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/master/metrics
* 
/hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/master/metrics/TestMasterMetricsWrapper.java


 Update HBase metrics framework to metrics2 framework
 

 Key: HBASE-4050
 URL: https://issues.apache.org/jira/browse/HBASE-4050
 Project: HBase
  Issue Type: New Feature
  Components: metrics
Affects Versions: 0.90.4
 Environment: Java 6
Reporter: Eric Yang
Assignee: Elliott Clark
Priority: Critical
 Fix For: 0.96.0

 Attachments: 4050-metrics-v2.patch, 4050-metrics-v3.patch, 
 HBASE-4050-0.patch, HBASE-4050-1.patch, HBASE-4050-2.patch, 
 HBASE-4050-3.patch, HBASE-4050-5.patch, HBASE-4050-6.patch, 
 HBASE-4050-7.patch, HBASE-4050-8_1.patch, HBASE-4050-8.patch, HBASE-4050.patch


 Metrics Framework has been marked deprecated in Hadoop 0.20.203+ and 0.22+, 
 and it might get removed in future Hadoop release.  Hence, HBase needs to 
 revise the dependency of MetricsContext to use Metrics2 framework.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (HBASE-2116) Puts and deletes can no longer be applied to the same row with the new client API


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

Lars Hofhansl resolved HBASE-2116.
--

Resolution: Duplicate

Fixed with HBASE-3584

 Puts and deletes can no longer be applied to the same row with the new client 
 API
 -

 Key: HBASE-2116
 URL: https://issues.apache.org/jira/browse/HBASE-2116
 Project: HBase
  Issue Type: Improvement
  Components: client
Affects Versions: 0.20.2
Reporter: Bassam Tabbara

 As of HBASE-1304, it seems like one can no longer apply puts and deletes to 
 the same row, and more importantly in the same transaction. Obviously one 
 could use rowLocks but this seems heavy handed for this. Also, it seems that 
 this limitation is solely due to the new API factoring.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HBASE-4467) Handle inconsistencies in Hadoop libraries naming in hbase script


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

Jesse Yates commented on HBASE-4467:


Can we remove 0.94 from this (if not close)? Looks like the issue is a 
non-starter there.

 Handle inconsistencies in Hadoop libraries naming in hbase script
 -

 Key: HBASE-4467
 URL: https://issues.apache.org/jira/browse/HBASE-4467
 Project: HBase
  Issue Type: Bug
  Components: scripts
Affects Versions: 0.92.0, 0.94.0
Reporter: Lars George
Assignee: Lars George
Priority: Trivial
 Fix For: 0.92.3

 Attachments: HBASE-4467.patch


 When using an Hadoop tarball that has a library naming of hadoop-x.y.z-core 
 as opposed to hadoop-core-x.y.z then the hbase script throws errors.
 {noformat}
 $ bin/start-hbase.sh 
 ls: /projects/opensource/hadoop-0.20.2-append/hadoop-core*.jar: No such file 
 or directory
 Exception in thread main java.lang.NoClassDefFoundError: 
 org/apache/hadoop/util/PlatformName
 Caused by: java.lang.ClassNotFoundException: 
 org.apache.hadoop.util.PlatformName
   at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
   at java.security.AccessController.doPrivileged(Native Method)
   at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
   at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
   at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
   at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
 ls: /projects/opensource/hadoop-0.20.2-append/hadoop-core*.jar: No such file 
 or directory
 Exception in thread main java.lang.NoClassDefFoundError: 
 org/apache/hadoop/util/PlatformName
 Caused by: java.lang.ClassNotFoundException: 
 org.apache.hadoop.util.PlatformName
   at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
   at java.security.AccessController.doPrivileged(Native Method)
   at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
   at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
   at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
   at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
 localhost: starting zookeeper, logging to 
 /projects/opensource/hbase-trunk-rw//logs/hbase-larsgeorge-zookeeper-de1-app-mbp-2.out
 localhost: /projects/opensource/hadoop-0.20.2-append
 localhost: ls: /projects/opensource/hadoop-0.20.2-append/hadoop-core*.jar: No 
 such file or directory
 localhost: Exception in thread main java.lang.NoClassDefFoundError: 
 org/apache/hadoop/util/PlatformName
 localhost: Caused by: java.lang.ClassNotFoundException: 
 org.apache.hadoop.util.PlatformName
 localhost:at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
 localhost:at java.security.AccessController.doPrivileged(Native Method)
 localhost:at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
 localhost:at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
 localhost:at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
 localhost:at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
 starting master, logging to 
 /projects/opensource/hbase-trunk-rw/bin/../logs/hbase-larsgeorge-master-de1-app-mbp-2.out
 /projects/opensource/hadoop-0.20.2-append
 ls: /projects/opensource/hadoop-0.20.2-append/hadoop-core*.jar: No such file 
 or directory
 Exception in thread main java.lang.NoClassDefFoundError: 
 org/apache/hadoop/util/PlatformName
 Caused by: java.lang.ClassNotFoundException: 
 org.apache.hadoop.util.PlatformName
   at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
   at java.security.AccessController.doPrivileged(Native Method)
   at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
   at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
   at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
   at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
 localhost: starting regionserver, logging to 
 /projects/opensource/hbase-trunk-rw//logs/hbase-larsgeorge-regionserver-de1-app-mbp-2.out
 localhost: /projects/opensource/hadoop-0.20.2-append
 localhost: ls: /projects/opensource/hadoop-0.20.2-append/hadoop-core*.jar: No 
 such file or directory
 localhost: Exception in thread main java.lang.NoClassDefFoundError: 
 org/apache/hadoop/util/PlatformName
 localhost: Caused by: java.lang.ClassNotFoundException: 
 org.apache.hadoop.util.PlatformName
 localhost:at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
 localhost:at java.security.AccessController.doPrivileged(Native Method)
 localhost:at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
 localhost:at

[jira] [Commented] (HBASE-4481) TestMergeTool failed in 0.92 build 20


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

Jesse Yates commented on HBASE-4481:


Can we close this out?

 TestMergeTool failed in 0.92 build 20
 -

 Key: HBASE-4481
 URL: https://issues.apache.org/jira/browse/HBASE-4481
 Project: HBase
  Issue Type: Bug
Affects Versions: 0.92.0
Reporter: Ted Yu
Priority: Critical
 Attachments: 4481-dbg.txt, 4481.txt


 TestMergeTool failed due to the following exception:
 {code}
 java.lang.StringIndexOutOfBoundsException: String index out of range: -1
   at java.lang.String.substring(String.java:1937)
   at org.apache.hadoop.hbase.ServerName.parseHostname(ServerName.java:81)
   at org.apache.hadoop.hbase.ServerName.init(ServerName.java:63)
   at 
 org.apache.hadoop.hbase.MasterAddressTracker.getMasterAddress(MasterAddressTracker.java:62)
   at 
 org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.getMaster(HConnectionManager.java:583)
   at org.apache.hadoop.hbase.client.HBaseAdmin.init(HBaseAdmin.java:108)
   at 
 org.apache.hadoop.hbase.client.HBaseAdmin.checkHBaseAvailable(HBaseAdmin.java:1588)
   at org.apache.hadoop.hbase.util.Merge.run(Merge.java:94)
   at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:65)
   at 
 org.apache.hadoop.hbase.util.TestMergeTool.mergeAndVerify(TestMergeTool.java:186)
   at 
 org.apache.hadoop.hbase.util.TestMergeTool.testMergeTool(TestMergeTool.java:264)
 {code}
 Log can be found at:
 https://builds.apache.org/view/G-L/view/HBase/job/HBase-0.92/20/testReport/junit/org.apache.hadoop.hbase.util/TestMergeTool/testMergeTool/

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HBASE-4050) Update HBase metrics framework to metrics2 framework