[jira] [Commented] (HBASE-7923) force unassign can confirm region online on any RS to get rid of double assignments.
[
https://issues.apache.org/jira/browse/HBASE-7923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13621832#comment-13621832
]
Hudson commented on HBASE-7923:
---
Integrated in HBase-TRUNK #4010 (See
[https://builds.apache.org/job/HBase-TRUNK/4010/])
HBASE-7923 force unassign can confirm region online on any RS to get rid of
double assignments (Revision 1464232)
Result = FAILURE
stack :
Files :
*
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/master/HMaster.java
force unassign can confirm region online on any RS to get rid of double
assignments.
Key: HBASE-7923
URL: https://issues.apache.org/jira/browse/HBASE-7923
Project: HBase
Issue Type: Improvement
Reporter: rajeshbabu
Assignee: rajeshbabu
Fix For: 0.95.1
Attachments: HBASE-7923_2.patch, HBASE-7923_3.patch, HBASE-7923.patch
Presently in force unassign we are offlining a region from AM and reassigning
it, which may cause double assignments.
{code}
this.assignmentManager.regionOffline(hri);
assignRegion(hri);
{code}
Any way if a region is not served by any RS we are offlining the region from
AM.
{code}
if (t instanceof NotServingRegionException) {
if (transitionInZK) {
deleteClosingOrClosedNode(region);
}
regionOffline(region);
return;
}
{code}
We can change as below just to confirm whether region online on any RS.
{code}
this.assignmentManager.unassign(hri,force);
if(!this.assignmentManager.getRegionStates().isRegionInTransition(hri)
!this.assignmentManager.getRegionStates().isRegionAssigned(hri) ){
assignRegion(hri);
}
{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-8263) Master LogSplitting metrics update wrong counters
[
https://issues.apache.org/jira/browse/HBASE-8263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13621833#comment-13621833
]
Hudson commented on HBASE-8263:
---
Integrated in HBase-TRUNK #4010 (See
[https://builds.apache.org/job/HBase-TRUNK/4010/])
HBASE-8263 Master LogSplitting metrics update wrong counters (Revision
1464268)
Result = FAILURE
stack :
Files :
*
/hbase/trunk/hbase-hadoop1-compat/src/main/java/org/apache/hadoop/hbase/master/MetricsMasterSourceImpl.java
*
/hbase/trunk/hbase-hadoop2-compat/src/main/java/org/apache/hadoop/hbase/master/MetricsMasterSourceImpl.java
Master LogSplitting metrics update wrong counters
-
Key: HBASE-8263
URL: https://issues.apache.org/jira/browse/HBASE-8263
Project: HBase
Issue Type: Bug
Components: metrics
Reporter: Jeffrey Zhong
Assignee: Jeffrey Zhong
Priority: Minor
Fix For: 0.95.1
Attachments: hbase-8263.patch
Wrong counters are updated as you can see in
MetricsMasterSourceImpl.java#init()
{code}
splitTimeHisto = metricsRegistry.newHistogram(SPLIT_SIZE_NAME,
SPLIT_SIZE_DESC);
splitSizeHisto = metricsRegistry.newHistogram(SPLIT_TIME_NAME,
SPLIT_TIME_DESC);
{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-8231) delete tests in table_tests.rb(TestShell) always running on empty table.
[
https://issues.apache.org/jira/browse/HBASE-8231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13621834#comment-13621834
]
Hudson commented on HBASE-8231:
---
Integrated in HBase-TRUNK #4010 (See
[https://builds.apache.org/job/HBase-TRUNK/4010/])
HBASE-8231 delete tests in table_tests.rb(TestShell) always running on
empty table (Revision 1464283)
Result = FAILURE
stack :
Files :
* /hbase/trunk/hbase-server/src/test/ruby/hbase/table_test.rb
delete tests in table_tests.rb(TestShell) always running on empty table.
Key: HBASE-8231
URL: https://issues.apache.org/jira/browse/HBASE-8231
Project: HBase
Issue Type: Bug
Components: scripts
Affects Versions: 0.95.0, 0.94.6
Reporter: rajeshbabu
Assignee: rajeshbabu
Fix For: 0.95.1, 0.94.7
Attachments: HBASE-8231.patch
In ruby,tests within the same test class are invoked in alphabetical order,so
delete test cases are running on a table before adding any entry.
TestShell logs showing Row not found for each delete test everytime.
{code}
ERROR: Row Not Found
Here is some help for this command:
Delete all cells in a given row; pass a table name, row, and optionally
a column and timestamp. Examples:
hbase deleteall 't1', 'r1'
hbase deleteall 't1', 'r1', 'c1'
hbase deleteall 't1', 'r1', 'c1', ts1
The same commands also can be run on a table reference. Suppose you had a
reference
t to table 't1', the corresponding command would be:
hbase t.deleteall 'r1'
hbase t.deleteall 'r1', 'c1'
hbase t.deleteall 'r1', 'c1', ts1
{code}
Before deleting a row we are checking whether the row is present or not.
{code}
def _deleteall_internal(row, column = nil, timestamp =
org.apache.hadoop.hbase.HConstants::LATEST_TIMESTAMP)
raise ArgumentError, Row Not Found if _get_internal(row).nil?
{code}
Need to improve delete tests in table_tests.rb.
--
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-8230) Possible NPE on regionserver abort if replication service has not been started
[
https://issues.apache.org/jira/browse/HBASE-8230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13621835#comment-13621835
]
Hudson commented on HBASE-8230:
---
Integrated in HBase-TRUNK #4010 (See
[https://builds.apache.org/job/HBase-TRUNK/4010/])
HBASE-8230 Possible NPE on regionserver abort if replication service has
not been started (Revision 1464280)
Result = FAILURE
stack :
Files :
*
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/replication/regionserver/Replication.java
Possible NPE on regionserver abort if replication service has not been started
--
Key: HBASE-8230
URL: https://issues.apache.org/jira/browse/HBASE-8230
Project: HBase
Issue Type: Bug
Components: regionserver, Replication
Affects Versions: 0.94.6
Reporter: Jieshan Bean
Assignee: Jieshan Bean
Fix For: 0.95.1, 0.94.7
Attachments: HBASE-8230-94.patch, HBASE-8230-trunk.patch
RegionServer got Exception on calling setupWALAndReplication, so entered
abort flow. Since replicationSink had not been inialized yet, we got below
exception:
{noformat}
Exception in thread regionserver26003 java.lang.NullPointerException
at
org.apache.hadoop.hbase.replication.regionserver.Replication.join(Replication.java:129)
at
org.apache.hadoop.hbase.replication.regionserver.Replication.stopReplicationService(Replication.java:120)
at
org.apache.hadoop.hbase.regionserver.HRegionServer.join(HRegionServer.java:1803)
at
org.apache.hadoop.hbase.regionserver.HRegionServer.run(HRegionServer.java:834)
at java.lang.Thread.run(Thread.java:662)
{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-7568) [replication] Create an interface for replication queues
[ https://issues.apache.org/jira/browse/HBASE-7568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13621836#comment-13621836 ] Hudson commented on HBASE-7568: --- Integrated in HBase-TRUNK #4010 (See [https://builds.apache.org/job/HBase-TRUNK/4010/]) HBASE-7568 [replication] Create an interface for replication queues (Revision 1464279) Result = FAILURE stack : Files : * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/replication/ReplicationQueues.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/replication/ReplicationQueuesClient.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/replication/ReplicationQueuesClientZKImpl.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/replication/ReplicationQueuesZKImpl.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/replication/ReplicationStateImpl.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/replication/ReplicationStateZKBase.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/replication/ReplicationZookeeper.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/replication/master/ReplicationLogCleaner.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/replication/regionserver/Replication.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/replication/regionserver/ReplicationSourceManager.java * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/client/replication/TestReplicationAdmin.java * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/replication/TestReplicationStateBasic.java * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/replication/TestReplicationStateZKImpl.java * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/replication/regionserver/TestReplicationSourceManager.java [replication] Create an interface for replication queues Key: HBASE-7568 URL: https://issues.apache.org/jira/browse/HBASE-7568 Project: HBase Issue Type: Improvement Components: Replication Reporter: Chris Trezzo Assignee: Chris Trezzo Fix For: 0.95.1 Attachments: HBASE-7568-95-v1.patch, HBASE-7568-trunk-v1.patch, HBASE-7568-trunk-v2.patch, HBASE-7568-trunk-v3.patch, HBASE-7568-trunk-v4.patch -- 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-8188) Avoid unnecessary row compare in StoreScanner
[ https://issues.apache.org/jira/browse/HBASE-8188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13621837#comment-13621837 ] Hudson commented on HBASE-8188: --- Integrated in HBase-TRUNK #4010 (See [https://builds.apache.org/job/HBase-TRUNK/4010/]) HBASE-8188 Avoid unnecessary row compare in StoreScanner (Revision 1464287) Result = FAILURE larsh : Files : * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/StoreScanner.java Avoid unnecessary row compare in StoreScanner - Key: HBASE-8188 URL: https://issues.apache.org/jira/browse/HBASE-8188 Project: HBase Issue Type: Bug Reporter: Lars Hofhansl Assignee: Lars Hofhansl Fix For: 0.95.1, 0.98.0, 0.94.7 Attachments: 8188-0.94-experimental.txt, 8188-0.94.txt, 8188-0.96.txt, 8188-0.96.txt, 8188-0.96.txt, 8188-0.96.txt When scanner batching disable (which is the default) a row compare in StoreScanner avoided, because only entire rows of data are requested. This provides a slight performance gain, especially for tall tables (and when all data is in the cache) -- 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-8229) Replication code logs like crazy if a target table cannot be found.
[ https://issues.apache.org/jira/browse/HBASE-8229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13621838#comment-13621838 ] Hudson commented on HBASE-8229: --- Integrated in HBase-TRUNK #4010 (See [https://builds.apache.org/job/HBase-TRUNK/4010/]) HBASE-8229 Replication code logs like crazy if a target table cannot be found. (Revision 1464278) Result = FAILURE larsh : Files : * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/replication/regionserver/ReplicationSource.java Replication code logs like crazy if a target table cannot be found. --- Key: HBASE-8229 URL: https://issues.apache.org/jira/browse/HBASE-8229 Project: HBase Issue Type: Bug Components: Replication Reporter: Lars Hofhansl Fix For: 0.95.1, 0.98.0, 0.94.7 Attachments: 8229-0.94.txt One of our RS/DN machines ran out of diskspace on the partition to which we write the log files. It turns out we still had a table in our source cluster with REPLICATION_SCOPE=1 that did not have a matching table in the remote cluster. In then logged a long stack trace every 50ms or so, over a few days that filled up our log partition. Since ReplicationSource cannot make any progress in this case anyway, it should probably sleep a bit before retrying (or at least limit the rate at which it spews out these exceptions to the log). -- 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-8240) CompoundConfiguration should implement Iterable
[
https://issues.apache.org/jira/browse/HBASE-8240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13621840#comment-13621840
]
stack commented on HBASE-8240:
--
Suggest removing ... which should only be conducted when absolutely
necessary. on commit.
IterableMap.EntryString,String
Is all config. in this CompoundConfiguration a String key and a String value?
No ints, longs, etc.?
I suppose it is ok because base Configuration does this.
Do we have to save up all of the Configuation into a HashMap to decorate it
with an unmodifiable?
Where do we need this functionatlity?
CompoundConfiguration should implement Iterable
---
Key: HBASE-8240
URL: https://issues.apache.org/jira/browse/HBASE-8240
Project: HBase
Issue Type: Improvement
Reporter: Ted Yu
Assignee: Ted Yu
Fix For: 0.95.1, 0.98.0
Attachments: 8240-v1.txt, 8240-v2.txt, 8240-v3.txt, 8240-v4.txt,
8240-v6.txt
Here is from hadoop Configuration class:
{code}
public class Configuration implements IterableMap.EntryString,String,
{code}
There're 3 addXX() methods for CompoundConfiguration:
{code}
public CompoundConfiguration add(final Configuration conf) {
public CompoundConfiguration addWritableMap(
final MapImmutableBytesWritable, ImmutableBytesWritable map) {
public CompoundConfiguration addStringMap(final MapString, String map) {
{code}
Parameters to these methods all support iteration.
We can enhance ImmutableConfigMap with the following new method:
{code}
public abstract java.util.Iterator iterator();
{code}
Then the following method of CompoundConfiguration can be implemented:
{code}
public IteratorMap.EntryString, String iterator() {
{code}
This enhancement would be useful in scenario where a mutable Configuration is
required.
--
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-7836) Create a new replay command so that recovered edits won't mess up normal coprocessing metrics
[ https://issues.apache.org/jira/browse/HBASE-7836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeffrey Zhong updated HBASE-7836: - Attachment: hbase-7836-combined_v2.patch Trigger QA test Create a new replay command so that recovered edits won't mess up normal coprocessing metrics - Key: HBASE-7836 URL: https://issues.apache.org/jira/browse/HBASE-7836 Project: HBase Issue Type: Sub-task Reporter: Jeffrey Zhong Assignee: Jeffrey Zhong Fix For: 0.95.1 Attachments: hbase-7836-combined.patch, hbase-7836-combined_v2.patch, hbase-7836_v1.patch, hbase-7836_v2.patch -- 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-8240) CompoundConfiguration should implement Iterable
[
https://issues.apache.org/jira/browse/HBASE-8240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-8240:
-
Fix Version/s: (was: 0.95.1)
Moving new feature out of 0.95. Feel free to pull back later.
CompoundConfiguration should implement Iterable
---
Key: HBASE-8240
URL: https://issues.apache.org/jira/browse/HBASE-8240
Project: HBase
Issue Type: Improvement
Reporter: Ted Yu
Assignee: Ted Yu
Fix For: 0.98.0
Attachments: 8240-v1.txt, 8240-v2.txt, 8240-v3.txt, 8240-v4.txt,
8240-v6.txt
Here is from hadoop Configuration class:
{code}
public class Configuration implements IterableMap.EntryString,String,
{code}
There're 3 addXX() methods for CompoundConfiguration:
{code}
public CompoundConfiguration add(final Configuration conf) {
public CompoundConfiguration addWritableMap(
final MapImmutableBytesWritable, ImmutableBytesWritable map) {
public CompoundConfiguration addStringMap(final MapString, String map) {
{code}
Parameters to these methods all support iteration.
We can enhance ImmutableConfigMap with the following new method:
{code}
public abstract java.util.Iterator iterator();
{code}
Then the following method of CompoundConfiguration can be implemented:
{code}
public IteratorMap.EntryString, String iterator() {
{code}
This enhancement would be useful in scenario where a mutable Configuration is
required.
--
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-7836) Create a new replay command so that recovered edits won't mess up normal coprocessing metrics
[ https://issues.apache.org/jira/browse/HBASE-7836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeffrey Zhong updated HBASE-7836: - Status: Patch Available (was: Open) Create a new replay command so that recovered edits won't mess up normal coprocessing metrics - Key: HBASE-7836 URL: https://issues.apache.org/jira/browse/HBASE-7836 Project: HBase Issue Type: Sub-task Reporter: Jeffrey Zhong Assignee: Jeffrey Zhong Fix For: 0.95.1 Attachments: hbase-7836-combined.patch, hbase-7836-combined_v2.patch, hbase-7836_v1.patch, hbase-7836_v2.patch -- 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-7923) force unassign can confirm region online on any RS to get rid of double assignments.
[
https://issues.apache.org/jira/browse/HBASE-7923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13621852#comment-13621852
]
Hudson commented on HBASE-7923:
---
Integrated in hbase-0.95 #122 (See
[https://builds.apache.org/job/hbase-0.95/122/])
HBASE-7923 force unassign can confirm region online on any RS to get rid of
double assignments (Revision 1464233)
Result = FAILURE
stack :
Files :
*
/hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/master/HMaster.java
force unassign can confirm region online on any RS to get rid of double
assignments.
Key: HBASE-7923
URL: https://issues.apache.org/jira/browse/HBASE-7923
Project: HBase
Issue Type: Improvement
Reporter: rajeshbabu
Assignee: rajeshbabu
Fix For: 0.95.1
Attachments: HBASE-7923_2.patch, HBASE-7923_3.patch, HBASE-7923.patch
Presently in force unassign we are offlining a region from AM and reassigning
it, which may cause double assignments.
{code}
this.assignmentManager.regionOffline(hri);
assignRegion(hri);
{code}
Any way if a region is not served by any RS we are offlining the region from
AM.
{code}
if (t instanceof NotServingRegionException) {
if (transitionInZK) {
deleteClosingOrClosedNode(region);
}
regionOffline(region);
return;
}
{code}
We can change as below just to confirm whether region online on any RS.
{code}
this.assignmentManager.unassign(hri,force);
if(!this.assignmentManager.getRegionStates().isRegionInTransition(hri)
!this.assignmentManager.getRegionStates().isRegionAssigned(hri) ){
assignRegion(hri);
}
{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-8231) delete tests in table_tests.rb(TestShell) always running on empty table.
[
https://issues.apache.org/jira/browse/HBASE-8231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13621854#comment-13621854
]
Hudson commented on HBASE-8231:
---
Integrated in hbase-0.95 #122 (See
[https://builds.apache.org/job/hbase-0.95/122/])
HBASE-8231 delete tests in table_tests.rb(TestShell) always running on
empty table (Revision 1464284)
Result = FAILURE
stack :
Files :
* /hbase/branches/0.95/hbase-server/src/test/ruby/hbase/table_test.rb
delete tests in table_tests.rb(TestShell) always running on empty table.
Key: HBASE-8231
URL: https://issues.apache.org/jira/browse/HBASE-8231
Project: HBase
Issue Type: Bug
Components: scripts
Affects Versions: 0.95.0, 0.94.6
Reporter: rajeshbabu
Assignee: rajeshbabu
Fix For: 0.95.1, 0.94.7
Attachments: HBASE-8231.patch
In ruby,tests within the same test class are invoked in alphabetical order,so
delete test cases are running on a table before adding any entry.
TestShell logs showing Row not found for each delete test everytime.
{code}
ERROR: Row Not Found
Here is some help for this command:
Delete all cells in a given row; pass a table name, row, and optionally
a column and timestamp. Examples:
hbase deleteall 't1', 'r1'
hbase deleteall 't1', 'r1', 'c1'
hbase deleteall 't1', 'r1', 'c1', ts1
The same commands also can be run on a table reference. Suppose you had a
reference
t to table 't1', the corresponding command would be:
hbase t.deleteall 'r1'
hbase t.deleteall 'r1', 'c1'
hbase t.deleteall 'r1', 'c1', ts1
{code}
Before deleting a row we are checking whether the row is present or not.
{code}
def _deleteall_internal(row, column = nil, timestamp =
org.apache.hadoop.hbase.HConstants::LATEST_TIMESTAMP)
raise ArgumentError, Row Not Found if _get_internal(row).nil?
{code}
Need to improve delete tests in table_tests.rb.
--
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-8263) Master LogSplitting metrics update wrong counters
[
https://issues.apache.org/jira/browse/HBASE-8263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13621853#comment-13621853
]
Hudson commented on HBASE-8263:
---
Integrated in hbase-0.95 #122 (See
[https://builds.apache.org/job/hbase-0.95/122/])
HBASE-8263 Master LogSplitting metrics update wrong counters (Revision
1464267)
Result = FAILURE
stack :
Files :
*
/hbase/branches/0.95/hbase-hadoop1-compat/src/main/java/org/apache/hadoop/hbase/master/MetricsMasterSourceImpl.java
*
/hbase/branches/0.95/hbase-hadoop2-compat/src/main/java/org/apache/hadoop/hbase/master/MetricsMasterSourceImpl.java
Master LogSplitting metrics update wrong counters
-
Key: HBASE-8263
URL: https://issues.apache.org/jira/browse/HBASE-8263
Project: HBase
Issue Type: Bug
Components: metrics
Reporter: Jeffrey Zhong
Assignee: Jeffrey Zhong
Priority: Minor
Fix For: 0.95.1
Attachments: hbase-8263.patch
Wrong counters are updated as you can see in
MetricsMasterSourceImpl.java#init()
{code}
splitTimeHisto = metricsRegistry.newHistogram(SPLIT_SIZE_NAME,
SPLIT_SIZE_DESC);
splitSizeHisto = metricsRegistry.newHistogram(SPLIT_TIME_NAME,
SPLIT_TIME_DESC);
{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-5525) Truncate and preserve region boundaries option
[ https://issues.apache.org/jira/browse/HBASE-5525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13621855#comment-13621855 ] Hudson commented on HBASE-5525: --- Integrated in hbase-0.95 #122 (See [https://builds.apache.org/job/hbase-0.95/122/]) HBASE-5525 Truncate and preserve region boundaries option (Revision 1464291) Result = FAILURE stack : Files : * /hbase/branches/0.95/hbase-server/src/main/ruby/hbase/admin.rb * /hbase/branches/0.95/hbase-server/src/main/ruby/shell.rb Truncate and preserve region boundaries option -- Key: HBASE-5525 URL: https://issues.apache.org/jira/browse/HBASE-5525 Project: HBase Issue Type: New Feature Affects Versions: 0.96.0 Reporter: Jean-Daniel Cryans Assignee: Kevin Odell Labels: newbie, noob Fix For: 0.95.1 Attachments: HBASE-5525.patch, HBASE-5525-v1-0.94.patch, HBASE-5525-v1-0.95.patch, HBASE-5525-v1-trunk.patch, HBASE-5525-v1-trunk.patch A tool that would be useful for testing (and maybe in prod too) would be a truncate option to keep the current region boundaries. Right now what you have to do is completely kill the table and recreate it with the correct regions. -- 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-8230) Possible NPE on regionserver abort if replication service has not been started
[
https://issues.apache.org/jira/browse/HBASE-8230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13621856#comment-13621856
]
Hudson commented on HBASE-8230:
---
Integrated in hbase-0.95 #122 (See
[https://builds.apache.org/job/hbase-0.95/122/])
HBASE-8230 Possible NPE on regionserver abort if replication service has
not been started (Revision 1464281)
Result = FAILURE
stack :
Files :
*
/hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/replication/regionserver/Replication.java
Possible NPE on regionserver abort if replication service has not been started
--
Key: HBASE-8230
URL: https://issues.apache.org/jira/browse/HBASE-8230
Project: HBase
Issue Type: Bug
Components: regionserver, Replication
Affects Versions: 0.94.6
Reporter: Jieshan Bean
Assignee: Jieshan Bean
Fix For: 0.95.1, 0.94.7
Attachments: HBASE-8230-94.patch, HBASE-8230-trunk.patch
RegionServer got Exception on calling setupWALAndReplication, so entered
abort flow. Since replicationSink had not been inialized yet, we got below
exception:
{noformat}
Exception in thread regionserver26003 java.lang.NullPointerException
at
org.apache.hadoop.hbase.replication.regionserver.Replication.join(Replication.java:129)
at
org.apache.hadoop.hbase.replication.regionserver.Replication.stopReplicationService(Replication.java:120)
at
org.apache.hadoop.hbase.regionserver.HRegionServer.join(HRegionServer.java:1803)
at
org.apache.hadoop.hbase.regionserver.HRegionServer.run(HRegionServer.java:834)
at java.lang.Thread.run(Thread.java:662)
{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-7568) [replication] Create an interface for replication queues
[ https://issues.apache.org/jira/browse/HBASE-7568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13621857#comment-13621857 ] Hudson commented on HBASE-7568: --- Integrated in hbase-0.95 #122 (See [https://builds.apache.org/job/hbase-0.95/122/]) HBASE-7568 [replication] Create an interface for replication queues (Revision 1464276) Result = FAILURE stack : Files : * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/replication/ReplicationQueues.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/replication/ReplicationQueuesClient.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/replication/ReplicationQueuesClientZKImpl.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/replication/ReplicationQueuesZKImpl.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/replication/ReplicationStateImpl.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/replication/ReplicationStateZKBase.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/replication/ReplicationZookeeper.java * /hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/replication/master/ReplicationLogCleaner.java * /hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/replication/regionserver/Replication.java * /hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/replication/regionserver/ReplicationSourceManager.java * /hbase/branches/0.95/hbase-server/src/test/java/org/apache/hadoop/hbase/client/replication/TestReplicationAdmin.java * /hbase/branches/0.95/hbase-server/src/test/java/org/apache/hadoop/hbase/replication/TestReplicationStateBasic.java * /hbase/branches/0.95/hbase-server/src/test/java/org/apache/hadoop/hbase/replication/TestReplicationStateZKImpl.java * /hbase/branches/0.95/hbase-server/src/test/java/org/apache/hadoop/hbase/replication/regionserver/TestReplicationSourceManager.java [replication] Create an interface for replication queues Key: HBASE-7568 URL: https://issues.apache.org/jira/browse/HBASE-7568 Project: HBase Issue Type: Improvement Components: Replication Reporter: Chris Trezzo Assignee: Chris Trezzo Fix For: 0.95.1 Attachments: HBASE-7568-95-v1.patch, HBASE-7568-trunk-v1.patch, HBASE-7568-trunk-v2.patch, HBASE-7568-trunk-v3.patch, HBASE-7568-trunk-v4.patch -- 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-8188) Avoid unnecessary row compare in StoreScanner
[ https://issues.apache.org/jira/browse/HBASE-8188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13621858#comment-13621858 ] Hudson commented on HBASE-8188: --- Integrated in hbase-0.95 #122 (See [https://builds.apache.org/job/hbase-0.95/122/]) HBASE-8188 Avoid unnecessary row compare in StoreScanner (Revision 1464288) Result = FAILURE larsh : Files : * /hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/StoreScanner.java Avoid unnecessary row compare in StoreScanner - Key: HBASE-8188 URL: https://issues.apache.org/jira/browse/HBASE-8188 Project: HBase Issue Type: Bug Reporter: Lars Hofhansl Assignee: Lars Hofhansl Fix For: 0.95.1, 0.98.0, 0.94.7 Attachments: 8188-0.94-experimental.txt, 8188-0.94.txt, 8188-0.96.txt, 8188-0.96.txt, 8188-0.96.txt, 8188-0.96.txt When scanner batching disable (which is the default) a row compare in StoreScanner avoided, because only entire rows of data are requested. This provides a slight performance gain, especially for tall tables (and when all data is in the cache) -- 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-8229) Replication code logs like crazy if a target table cannot be found.
[ https://issues.apache.org/jira/browse/HBASE-8229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13621859#comment-13621859 ] Hudson commented on HBASE-8229: --- Integrated in hbase-0.95 #122 (See [https://builds.apache.org/job/hbase-0.95/122/]) HBASE-8229 Replication code logs like crazy if a target table cannot be found. (Revision 1464273) Result = FAILURE larsh : Files : * /hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/replication/regionserver/ReplicationSource.java Replication code logs like crazy if a target table cannot be found. --- Key: HBASE-8229 URL: https://issues.apache.org/jira/browse/HBASE-8229 Project: HBase Issue Type: Bug Components: Replication Reporter: Lars Hofhansl Fix For: 0.95.1, 0.98.0, 0.94.7 Attachments: 8229-0.94.txt One of our RS/DN machines ran out of diskspace on the partition to which we write the log files. It turns out we still had a table in our source cluster with REPLICATION_SCOPE=1 that did not have a matching table in the remote cluster. In then logged a long stack trace every 50ms or so, over a few days that filled up our log partition. Since ReplicationSource cannot make any progress in this case anyway, it should probably sleep a bit before retrying (or at least limit the rate at which it spews out these exceptions to the log). -- 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-7836) Create a new replay command so that recovered edits won't mess up normal coprocessing metrics
[
https://issues.apache.org/jira/browse/HBASE-7836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13621885#comment-13621885
]
Hadoop QA commented on HBASE-7836:
--
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12576932/hbase-7836-combined_v2.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 15 new
or modified tests.
{color:green}+1 hadoop2.0{color}. The patch compiles against the hadoop
2.0 profile.
{color:red}-1 javadoc{color}. The javadoc tool appears to have generated 2
warning messages.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 lineLengths{color}. The patch introduces lines longer than
100
{color:green}+1 site{color}. The mvn site goal succeeds with this patch.
{color:red}-1 core tests{color}. The patch failed these unit tests:
org.apache.hadoop.hbase.client.TestShell
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/5130//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5130//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5130//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5130//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5130//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5130//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5130//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5130//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5130//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/5130//console
This message is automatically generated.
Create a new replay command so that recovered edits won't mess up normal
coprocessing metrics
-
Key: HBASE-7836
URL: https://issues.apache.org/jira/browse/HBASE-7836
Project: HBase
Issue Type: Sub-task
Reporter: Jeffrey Zhong
Assignee: Jeffrey Zhong
Fix For: 0.95.1
Attachments: hbase-7836-combined.patch, hbase-7836-combined_v2.patch,
hbase-7836_v1.patch, hbase-7836_v2.patch
--
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-5525) Truncate and preserve region boundaries option
[
https://issues.apache.org/jira/browse/HBASE-5525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13621888#comment-13621888
]
rajeshbabu commented on HBASE-5525:
---
@stack,
truncate_preserve.rb(new file) in the patch is not committed by mistake.
In some QA TestShell is failing
{code}
Tests in error:
testRunShellTests(org.apache.hadoop.hbase.client.TestShell): (LoadError) no
such file to load -- shell/commands/truncate_preserve
{code}
Truncate and preserve region boundaries option
--
Key: HBASE-5525
URL: https://issues.apache.org/jira/browse/HBASE-5525
Project: HBase
Issue Type: New Feature
Affects Versions: 0.96.0
Reporter: Jean-Daniel Cryans
Assignee: Kevin Odell
Labels: newbie, noob
Fix For: 0.95.1
Attachments: HBASE-5525.patch, HBASE-5525-v1-0.94.patch,
HBASE-5525-v1-0.95.patch, HBASE-5525-v1-trunk.patch, HBASE-5525-v1-trunk.patch
A tool that would be useful for testing (and maybe in prod too) would be a
truncate option to keep the current region boundaries. Right now what you
have to do is completely kill the table and recreate it with the correct
regions.
--
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-8235) Adding inmemory CF attribute to LoadTest and PerformanceEvaluation tool
[ https://issues.apache.org/jira/browse/HBASE-8235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan updated HBASE-8235: -- Attachment: HBASE-8235_1.patch Updated patch and tested the both LoadTesttool and PerformanceEvaluation Adding inmemory CF attribute to LoadTest and PerformanceEvaluation tool --- Key: HBASE-8235 URL: https://issues.apache.org/jira/browse/HBASE-8235 Project: HBase Issue Type: Improvement Reporter: ramkrishna.s.vasudevan Assignee: ramkrishna.s.vasudevan Fix For: 0.98.0 Attachments: HBASE-8235_1.patch, HBASE-8235.patch Adding the inmemory CF attribute to the LoadTestTool and PerfEvaluation tool will make it extensible to test such inmemory scenarios also. -- 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-7462) TestDrainingServer is an integration test. It should be a unit test instead
[ https://issues.apache.org/jira/browse/HBASE-7462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13621893#comment-13621893 ] Nicolas Liochon commented on HBASE-7462: Yep, in many cases we do a mock for the master the regionservers, but not for ZooKeeper. As ZooKeeper starts/stops quickly it's not a big issue. TestDrainingServer is an integration test. It should be a unit test instead --- Key: HBASE-7462 URL: https://issues.apache.org/jira/browse/HBASE-7462 Project: HBase Issue Type: Wish Components: test Affects Versions: 0.96.0 Reporter: Nicolas Liochon Priority: Trivial Labels: noob TestDrainingServer tests the function that allows to say that a regionserver should not get new regions. As it is written today, it's an integration test: it starts stops a cluster. The test would be more efficient if it would just check that the AssignmentManager does not use the drained region server; whatever the circumstances (bulk assign or not for example). -- 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-8235) Adding inmemory CF attribute to LoadTest and PerformanceEvaluation tool
[ https://issues.apache.org/jira/browse/HBASE-8235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan updated HBASE-8235: -- Status: Patch Available (was: Open) Adding inmemory CF attribute to LoadTest and PerformanceEvaluation tool --- Key: HBASE-8235 URL: https://issues.apache.org/jira/browse/HBASE-8235 Project: HBase Issue Type: Improvement Reporter: ramkrishna.s.vasudevan Assignee: ramkrishna.s.vasudevan Fix For: 0.98.0 Attachments: HBASE-8235_1.patch, HBASE-8235.patch Adding the inmemory CF attribute to the LoadTestTool and PerfEvaluation tool will make it extensible to test such inmemory scenarios also. -- 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-8266) Master cannot start if TableNotFoundException is thrown while partial table recovery
ramkrishna.s.vasudevan created HBASE-8266:
-
Summary: Master cannot start if TableNotFoundException is thrown
while partial table recovery
Key: HBASE-8266
URL: https://issues.apache.org/jira/browse/HBASE-8266
Project: HBase
Issue Type: Bug
Affects Versions: 0.94.6, 0.95.0
Reporter: ramkrishna.s.vasudevan
Assignee: ramkrishna.s.vasudevan
Priority: Critical
Fix For: 0.95.0, 0.98.0, 0.94.7
I was trying to create a table. The table creation failed
{code}
java.io.IOException: java.util.concurrent.ExecutionException:
java.lang.IllegalStateException: Could not instantiate a region instance.
at
org.apache.hadoop.hbase.util.ModifyRegionUtils.createRegions(ModifyRegionUtils.java:133)
at
org.apache.hadoop.hbase.master.handler.CreateTableHandler.handleCreateHdfsRegions(CreateTableHandler.java:256)
at
org.apache.hadoop.hbase.master.handler.CreateTableHandler.handleCreateTable(CreateTableHandler.java:204)
at
org.apache.hadoop.hbase.master.handler.CreateTableHandler.process(CreateTableHandler.java:153)
at
org.apache.hadoop.hbase.executor.EventHandler.run(EventHandler.java:130)
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:662)
Caused by: java.util.concurrent.ExecutionException:
java.lang.IllegalStateException: Could not instantiate a region instance.
at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:222)
at java.util.concurrent.FutureTask.get(FutureTask.java:83)
at
org.apache.hadoop.hbase.util.ModifyRegionUtils.createRegions(ModifyRegionUtils.java:126)
... 7 more
Caused by: java.lang.IllegalStateException: Could not instantiate a region
instance.
at
org.apache.hadoop.hbase.regionserver.HRegion.newHRegion(HRegion.java:3765)
at
org.apache.hadoop.hbase.regionserver.HRegion.createHRegion(HRegion.java:3870)
at
org.apache.hadoop.hbase.util.ModifyRegionUtils$1.call(ModifyRegionUtils.java:106)
at
org.apache.hadoop.hbase.util.ModifyRegionUtils$1.call(ModifyRegionUtils.java:103)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
... 3 more
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at
org.apache.hadoop.hbase.regionserver.HRegion.newHRegion(HRegion.java:3762)
... 11 more
Caused by: java.lang.NoClassDefFoundError:
org/apache/hadoop/hbase/CompoundConfiguration$1
at
org.apache.hadoop.hbase.CompoundConfiguration.add(CompoundConfiguration.java:82)
at org.apache.hadoop.hbase.regionserver.HRegion.init(HRegion.java:438)
at org.apache.hadoop.hbase.regionserver.HRegion.init(HRegion.java:401)
... 16 more
{code}
Am not sure of the above failure. The same setup is able to create new tables.
Now the table is already in ENABLING state. The master was restarted.
Now as the table was found in ENABLING state but not added to META the
EnableTableHandler
{code}
2013-04-03 18:33:03,850 FATAL org.apache.hadoop.hbase.master.HMaster: Unhandled
exception. Starting shutdown.
org.apache.hadoop.hbase.exceptions.TableNotFoundException: TestTable
at
org.apache.hadoop.hbase.master.handler.EnableTableHandler.prepare(EnableTableHandler.java:89)
at
org.apache.hadoop.hbase.master.AssignmentManager.recoverTableInEnablingState(AssignmentManager.java:2586)
at
org.apache.hadoop.hbase.master.AssignmentManager.joinCluster(AssignmentManager.java:390)
at
org.apache.hadoop.hbase.master.HMaster.finishInitialization(HMaster.java:777)
at org.apache.hadoop.hbase.master.HMaster.run(HMaster.java:522)
at java.lang.Thread.run(Thread.java:662)
2013-04-03 18:33:03,880 INFO org.apache.hadoop.hbase.master.HMaster: Aborting
{code}
This does not allow me to start my master further leading to unoperationable
state of the whole cluster.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA,
[jira] [Updated] (HBASE-7704) migration tool that checks presence of HFile V1 files
[ https://issues.apache.org/jira/browse/HBASE-7704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Himanshu Vashishtha updated HBASE-7704: --- Attachment: HBase-7704-v1.patch A tool that detects any HFile V1 in a given directory. If no argument is given, it takes the hbase.rootdir directory. It prints the help with --h option. java -cp `hbase classpath` org.apache.hadoop.hbase.util.HFileV1Detector --h migration tool that checks presence of HFile V1 files - Key: HBASE-7704 URL: https://issues.apache.org/jira/browse/HBASE-7704 Project: HBase Issue Type: Task Reporter: Ted Yu Assignee: Himanshu Vashishtha Priority: Blocker Fix For: 0.95.1 Attachments: HBase-7704-v1.patch Below was Stack's comment from HBASE-7660: Regards the migration 'tool', or 'tool' to check for presence of v1 files, I imagine it as an addition to the hfile tool http://hbase.apache.org/book.html#hfile_tool2 The hfile tool already takes a bunch of args including printing out meta. We could add an option to print out version only – or return 1 if version 1 or some such – and then do a bit of code to just list all hfiles and run this script against each. Could MR it if too many files. -- 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-8231) delete tests in table_tests.rb(TestShell) always running on empty table.
[
https://issues.apache.org/jira/browse/HBASE-8231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13621916#comment-13621916
]
Hudson commented on HBASE-8231:
---
Integrated in HBase-0.94 #939 (See
[https://builds.apache.org/job/HBase-0.94/939/])
HBASE-8231 delete tests in table_tests.rb(TestShell) always running on
empty table (Revision 1464289)
Result = FAILURE
stack :
Files :
* /hbase/branches/0.94/src/test/ruby/hbase/table_test.rb
delete tests in table_tests.rb(TestShell) always running on empty table.
Key: HBASE-8231
URL: https://issues.apache.org/jira/browse/HBASE-8231
Project: HBase
Issue Type: Bug
Components: scripts
Affects Versions: 0.95.0, 0.94.6
Reporter: rajeshbabu
Assignee: rajeshbabu
Fix For: 0.95.1, 0.94.7
Attachments: HBASE-8231.patch
In ruby,tests within the same test class are invoked in alphabetical order,so
delete test cases are running on a table before adding any entry.
TestShell logs showing Row not found for each delete test everytime.
{code}
ERROR: Row Not Found
Here is some help for this command:
Delete all cells in a given row; pass a table name, row, and optionally
a column and timestamp. Examples:
hbase deleteall 't1', 'r1'
hbase deleteall 't1', 'r1', 'c1'
hbase deleteall 't1', 'r1', 'c1', ts1
The same commands also can be run on a table reference. Suppose you had a
reference
t to table 't1', the corresponding command would be:
hbase t.deleteall 'r1'
hbase t.deleteall 'r1', 'c1'
hbase t.deleteall 'r1', 'c1', ts1
{code}
Before deleting a row we are checking whether the row is present or not.
{code}
def _deleteall_internal(row, column = nil, timestamp =
org.apache.hadoop.hbase.HConstants::LATEST_TIMESTAMP)
raise ArgumentError, Row Not Found if _get_internal(row).nil?
{code}
Need to improve delete tests in table_tests.rb.
--
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-8230) Possible NPE on regionserver abort if replication service has not been started
[
https://issues.apache.org/jira/browse/HBASE-8230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13621917#comment-13621917
]
Hudson commented on HBASE-8230:
---
Integrated in HBase-0.94 #939 (See
[https://builds.apache.org/job/HBase-0.94/939/])
HBASE-8230 Possible NPE on regionserver abort if replication service has
not been started (Revision 1464282)
Result = FAILURE
stack :
Files :
*
/hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/replication/regionserver/Replication.java
Possible NPE on regionserver abort if replication service has not been started
--
Key: HBASE-8230
URL: https://issues.apache.org/jira/browse/HBASE-8230
Project: HBase
Issue Type: Bug
Components: regionserver, Replication
Affects Versions: 0.94.6
Reporter: Jieshan Bean
Assignee: Jieshan Bean
Fix For: 0.95.1, 0.94.7
Attachments: HBASE-8230-94.patch, HBASE-8230-trunk.patch
RegionServer got Exception on calling setupWALAndReplication, so entered
abort flow. Since replicationSink had not been inialized yet, we got below
exception:
{noformat}
Exception in thread regionserver26003 java.lang.NullPointerException
at
org.apache.hadoop.hbase.replication.regionserver.Replication.join(Replication.java:129)
at
org.apache.hadoop.hbase.replication.regionserver.Replication.stopReplicationService(Replication.java:120)
at
org.apache.hadoop.hbase.regionserver.HRegionServer.join(HRegionServer.java:1803)
at
org.apache.hadoop.hbase.regionserver.HRegionServer.run(HRegionServer.java:834)
at java.lang.Thread.run(Thread.java:662)
{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-8188) Avoid unnecessary row compare in StoreScanner
[ https://issues.apache.org/jira/browse/HBASE-8188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13621918#comment-13621918 ] Hudson commented on HBASE-8188: --- Integrated in HBase-0.94 #939 (See [https://builds.apache.org/job/HBase-0.94/939/]) HBASE-8188 Avoid unnecessary row compare in StoreScanner (Revision 1464286) Result = FAILURE larsh : Files : * /hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/regionserver/StoreScanner.java Avoid unnecessary row compare in StoreScanner - Key: HBASE-8188 URL: https://issues.apache.org/jira/browse/HBASE-8188 Project: HBase Issue Type: Bug Reporter: Lars Hofhansl Assignee: Lars Hofhansl Fix For: 0.95.1, 0.98.0, 0.94.7 Attachments: 8188-0.94-experimental.txt, 8188-0.94.txt, 8188-0.96.txt, 8188-0.96.txt, 8188-0.96.txt, 8188-0.96.txt When scanner batching disable (which is the default) a row compare in StoreScanner avoided, because only entire rows of data are requested. This provides a slight performance gain, especially for tall tables (and when all data is in the cache) -- 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-8229) Replication code logs like crazy if a target table cannot be found.
[ https://issues.apache.org/jira/browse/HBASE-8229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13621919#comment-13621919 ] Hudson commented on HBASE-8229: --- Integrated in HBase-0.94 #939 (See [https://builds.apache.org/job/HBase-0.94/939/]) HBASE-8229 Replication code logs like crazy if a target table cannot be found. (Revision 1464275) Result = FAILURE larsh : Files : * /hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/replication/regionserver/ReplicationSource.java Replication code logs like crazy if a target table cannot be found. --- Key: HBASE-8229 URL: https://issues.apache.org/jira/browse/HBASE-8229 Project: HBase Issue Type: Bug Components: Replication Reporter: Lars Hofhansl Fix For: 0.95.1, 0.98.0, 0.94.7 Attachments: 8229-0.94.txt One of our RS/DN machines ran out of diskspace on the partition to which we write the log files. It turns out we still had a table in our source cluster with REPLICATION_SCOPE=1 that did not have a matching table in the remote cluster. In then logged a long stack trace every 50ms or so, over a few days that filled up our log partition. Since ReplicationSource cannot make any progress in this case anyway, it should probably sleep a bit before retrying (or at least limit the rate at which it spews out these exceptions to the log). -- 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-7599) Port HBASE-6066 (low hanging read path improvements) to 0.94
[ https://issues.apache.org/jira/browse/HBASE-7599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13621920#comment-13621920 ] Hudson commented on HBASE-7599: --- Integrated in HBase-0.94 #939 (See [https://builds.apache.org/job/HBase-0.94/939/]) HBASE-7599 Port HBASE-6066 (low hanging read path improvements) to 0.94 - retry (Devaraj Das) (Revision 1464295) Result = FAILURE larsh : Files : * /hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/regionserver/HRegion.java * /hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/regionserver/HRegionServer.java Port HBASE-6066 (low hanging read path improvements) to 0.94 Key: HBASE-7599 URL: https://issues.apache.org/jira/browse/HBASE-7599 Project: HBase Issue Type: Improvement Reporter: Devaraj Das Assignee: Devaraj Das Fix For: 0.94.7 Attachments: 7599-0.94.patch, 7599-0.94.patch, 7599-0.94-v2.patch, 7599-0.94-v2.patch -- 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-6066) some low hanging read path improvement ideas
[
https://issues.apache.org/jira/browse/HBASE-6066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13621921#comment-13621921
]
Hudson commented on HBASE-6066:
---
Integrated in HBase-0.94 #939 (See
[https://builds.apache.org/job/HBase-0.94/939/])
HBASE-7599 Port HBASE-6066 (low hanging read path improvements) to 0.94 -
retry (Devaraj Das) (Revision 1464295)
Result = FAILURE
larsh :
Files :
*
/hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/regionserver/HRegion.java
*
/hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/regionserver/HRegionServer.java
some low hanging read path improvement ideas
-
Key: HBASE-6066
URL: https://issues.apache.org/jira/browse/HBASE-6066
Project: HBase
Issue Type: Sub-task
Components: Performance
Reporter: Kannan Muthukkaruppan
Assignee: Devaraj Das
Priority: Critical
Labels: noob
Fix For: 0.95.0
Attachments:
0001-jira-HBASE-6066-89-fb-Some-read-performance-improvem.patch,
6066-rebased-1.patch, 6066-rebased-1.patch, metric-stringbuilder-fix.patch
I was running some single threaded scan performance tests for a table with
small sized rows that is fully cached. Some observations...
We seem to be doing several wasteful iterations over and/or building of
temporary lists.
1) One such is the following code in HRegionServer.next():
{code}
boolean moreRows = s.next(values, HRegion.METRIC_NEXTSIZE);
if (!values.isEmpty()) {
for (KeyValue kv : values) { -- wasteful in most
cases
currentScanResultSize += kv.heapSize();
}
results.add(new Result(values));
{code}
By default the maxScannerResultSize is Long.MAX_VALUE. In those cases,
we can avoid the unnecessary iteration to compute currentScanResultSize.
2) An example of a wasteful temporary array, is results in
RegionScanner.next().
{code}
results.clear();
boolean returnResult = nextInternal(limit, metric);
outResults.addAll(results);
{code}
results then gets copied over to outResults via an addAll(). Not sure why we
can not directly collect the results in outResults.
3) Another almost similar exmaple of a wasteful array is results in
StoreScanner.next(), which eventually also copies its results into
outResults.
4) Reduce overhead of size metric maintained in StoreScanner.next().
{code}
if (metric != null) {
HRegion.incrNumericMetric(this.metricNamePrefix + metric,
copyKv.getLength());
}
results.add(copyKv);
{code}
A single call to next() might fetch a lot of KVs. We can first add up the
size of those KVs in a local variable and then in a finally clause increment
the metric one shot, rather than updating AtomicLongs for each KV.
5) RegionScanner.next() calls a helper RegionScanner.next() on the same
object. Both are synchronized methods. Synchronized methods calling nested
synchronized methods on the same object are probably adding some small
overhead. The inner next() calls isFilterDone() which is a also a
synchronized method. We should factor the code to avoid these nested
synchronized 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] [Commented] (HBASE-8235) Adding inmemory CF attribute to LoadTest and PerformanceEvaluation tool
[
https://issues.apache.org/jira/browse/HBASE-8235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13621939#comment-13621939
]
Hadoop QA commented on HBASE-8235:
--
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12576939/HBASE-8235_1.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 6 new
or modified tests.
{color:green}+1 hadoop2.0{color}. The patch compiles against the hadoop
2.0 profile.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 lineLengths{color}. The patch introduces lines longer than
100
{color:green}+1 site{color}. The mvn site goal succeeds with this patch.
{color:red}-1 core tests{color}. The patch failed these unit tests:
org.apache.hadoop.hbase.client.TestShell
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/5131//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5131//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5131//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5131//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5131//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5131//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5131//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5131//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5131//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/5131//console
This message is automatically generated.
Adding inmemory CF attribute to LoadTest and PerformanceEvaluation tool
---
Key: HBASE-8235
URL: https://issues.apache.org/jira/browse/HBASE-8235
Project: HBase
Issue Type: Improvement
Reporter: ramkrishna.s.vasudevan
Assignee: ramkrishna.s.vasudevan
Fix For: 0.98.0
Attachments: HBASE-8235_1.patch, HBASE-8235.patch
Adding the inmemory CF attribute to the LoadTestTool and PerfEvaluation tool
will make it extensible to test such inmemory scenarios also.
--
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-5525) Truncate and preserve region boundaries option
[ https://issues.apache.org/jira/browse/HBASE-5525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13621941#comment-13621941 ] Hudson commented on HBASE-5525: --- Integrated in HBase-TRUNK #4011 (See [https://builds.apache.org/job/HBase-TRUNK/4011/]) HBASE-5525 Truncate and preserve region boundaries option (Revision 1464290) Result = FAILURE stack : Files : * /hbase/trunk/hbase-server/src/main/ruby/hbase/admin.rb * /hbase/trunk/hbase-server/src/main/ruby/shell.rb Truncate and preserve region boundaries option -- Key: HBASE-5525 URL: https://issues.apache.org/jira/browse/HBASE-5525 Project: HBase Issue Type: New Feature Affects Versions: 0.96.0 Reporter: Jean-Daniel Cryans Assignee: Kevin Odell Labels: newbie, noob Fix For: 0.95.1 Attachments: HBASE-5525.patch, HBASE-5525-v1-0.94.patch, HBASE-5525-v1-0.95.patch, HBASE-5525-v1-trunk.patch, HBASE-5525-v1-trunk.patch A tool that would be useful for testing (and maybe in prod too) would be a truncate option to keep the current region boundaries. Right now what you have to do is completely kill the table and recreate it with the correct regions. -- 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-7437) Improve CompactSelection
[
https://issues.apache.org/jira/browse/HBASE-7437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiroshi Ikeda updated HBASE-7437:
-
Attachment: HBASE-7437-V3.patch
Patch v3 from review board.
Improve CompactSelection
Key: HBASE-7437
URL: https://issues.apache.org/jira/browse/HBASE-7437
Project: HBase
Issue Type: Improvement
Components: Compaction
Reporter: Hiroshi Ikeda
Assignee: Hiroshi Ikeda
Priority: Minor
Attachments: HBASE-7437.patch, HBASE-7437-V2.patch,
HBASE-7437-V3.patch
1. Using AtomicLong makes CompactSelection simple and improve its performance.
2. There are unused fields and methods.
3. The fields should be private.
4. Assertion in the method finishRequest seems wrong:
{code}
public void finishRequest() {
if (isOffPeakCompaction) {
long newValueToLog = -1;
synchronized(compactionCountLock) {
assert !isOffPeakCompaction : Double-counting off-peak count for
compaction;
{code}
The above assertion seems almost always false.
--
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-8266) Master cannot start if TableNotFoundException is thrown while partial table recovery
[
https://issues.apache.org/jira/browse/HBASE-8266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13622001#comment-13622001
]
Matteo Bertozzi commented on HBASE-8266:
just by looking at the stack trace the problem seems more related to the jars
that you're using
{code}
Caused by: java.lang.NoClassDefFoundError:
org/apache/hadoop/hbase/CompoundConfiguration$1
at
org.apache.hadoop.hbase.CompoundConfiguration.add(CompoundConfiguration.java:82)
at org.apache.hadoop.hbase.regionserver.HRegion.init(HRegion.java:438)
{code}
The CompoundConfiguration is in the hbase-common jar any problem with that?
Master cannot start if TableNotFoundException is thrown while partial table
recovery
Key: HBASE-8266
URL: https://issues.apache.org/jira/browse/HBASE-8266
Project: HBase
Issue Type: Bug
Affects Versions: 0.95.0, 0.94.6
Reporter: ramkrishna.s.vasudevan
Assignee: ramkrishna.s.vasudevan
Priority: Critical
Fix For: 0.95.0, 0.98.0, 0.94.7
I was trying to create a table. The table creation failed
{code}
java.io.IOException: java.util.concurrent.ExecutionException:
java.lang.IllegalStateException: Could not instantiate a region instance.
at
org.apache.hadoop.hbase.util.ModifyRegionUtils.createRegions(ModifyRegionUtils.java:133)
at
org.apache.hadoop.hbase.master.handler.CreateTableHandler.handleCreateHdfsRegions(CreateTableHandler.java:256)
at
org.apache.hadoop.hbase.master.handler.CreateTableHandler.handleCreateTable(CreateTableHandler.java:204)
at
org.apache.hadoop.hbase.master.handler.CreateTableHandler.process(CreateTableHandler.java:153)
at
org.apache.hadoop.hbase.executor.EventHandler.run(EventHandler.java:130)
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:662)
Caused by: java.util.concurrent.ExecutionException:
java.lang.IllegalStateException: Could not instantiate a region instance.
at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:222)
at java.util.concurrent.FutureTask.get(FutureTask.java:83)
at
org.apache.hadoop.hbase.util.ModifyRegionUtils.createRegions(ModifyRegionUtils.java:126)
... 7 more
Caused by: java.lang.IllegalStateException: Could not instantiate a region
instance.
at
org.apache.hadoop.hbase.regionserver.HRegion.newHRegion(HRegion.java:3765)
at
org.apache.hadoop.hbase.regionserver.HRegion.createHRegion(HRegion.java:3870)
at
org.apache.hadoop.hbase.util.ModifyRegionUtils$1.call(ModifyRegionUtils.java:106)
at
org.apache.hadoop.hbase.util.ModifyRegionUtils$1.call(ModifyRegionUtils.java:103)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
... 3 more
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at
org.apache.hadoop.hbase.regionserver.HRegion.newHRegion(HRegion.java:3762)
... 11 more
Caused by: java.lang.NoClassDefFoundError:
org/apache/hadoop/hbase/CompoundConfiguration$1
at
org.apache.hadoop.hbase.CompoundConfiguration.add(CompoundConfiguration.java:82)
at org.apache.hadoop.hbase.regionserver.HRegion.init(HRegion.java:438)
at org.apache.hadoop.hbase.regionserver.HRegion.init(HRegion.java:401)
... 16 more
{code}
Am not sure of the above failure. The same setup is able to create new
tables.
Now the table is already in ENABLING state. The master was restarted.
Now as the table was found in ENABLING state but not added to META the
EnableTableHandler
{code}
2013-04-03 18:33:03,850 FATAL org.apache.hadoop.hbase.master.HMaster:
Unhandled exception. Starting shutdown.
org.apache.hadoop.hbase.exceptions.TableNotFoundException: TestTable
at
org.apache.hadoop.hbase.master.handler.EnableTableHandler.prepare(EnableTableHandler.java:89)
at
[jira] [Commented] (HBASE-7437) Improve CompactSelection
[
https://issues.apache.org/jira/browse/HBASE-7437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13622005#comment-13622005
]
Hadoop QA commented on HBASE-7437:
--
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12576953/HBASE-7437-V3.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 4 new
or modified tests.
{color:green}+1 hadoop2.0{color}. The patch compiles against the hadoop
2.0 profile.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 lineLengths{color}. The patch does not introduce lines
longer than 100
{color:green}+1 site{color}. The mvn site goal succeeds with this patch.
{color:red}-1 core tests{color}. The patch failed these unit tests:
org.apache.hadoop.hbase.client.TestShell
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/5132//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5132//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5132//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5132//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5132//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5132//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5132//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5132//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5132//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/5132//console
This message is automatically generated.
Improve CompactSelection
Key: HBASE-7437
URL: https://issues.apache.org/jira/browse/HBASE-7437
Project: HBase
Issue Type: Improvement
Components: Compaction
Reporter: Hiroshi Ikeda
Assignee: Hiroshi Ikeda
Priority: Minor
Attachments: HBASE-7437.patch, HBASE-7437-V2.patch,
HBASE-7437-V3.patch
1. Using AtomicLong makes CompactSelection simple and improve its performance.
2. There are unused fields and methods.
3. The fields should be private.
4. Assertion in the method finishRequest seems wrong:
{code}
public void finishRequest() {
if (isOffPeakCompaction) {
long newValueToLog = -1;
synchronized(compactionCountLock) {
assert !isOffPeakCompaction : Double-counting off-peak count for
compaction;
{code}
The above assertion seems almost always false.
--
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-5525) Truncate and preserve region boundaries option
[ https://issues.apache.org/jira/browse/HBASE-5525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13622008#comment-13622008 ] Matteo Bertozzi commented on HBASE-5525: The shell is now broken in 95/trunk hbase-server/src/main/ruby/shell/commands/truncate_preserve.rb was not added to the repo. I'll commit that. Truncate and preserve region boundaries option -- Key: HBASE-5525 URL: https://issues.apache.org/jira/browse/HBASE-5525 Project: HBase Issue Type: New Feature Affects Versions: 0.96.0 Reporter: Jean-Daniel Cryans Assignee: Kevin Odell Labels: newbie, noob Fix For: 0.95.1 Attachments: HBASE-5525.patch, HBASE-5525-v1-0.94.patch, HBASE-5525-v1-0.95.patch, HBASE-5525-v1-trunk.patch, HBASE-5525-v1-trunk.patch A tool that would be useful for testing (and maybe in prod too) would be a truncate option to keep the current region boundaries. Right now what you have to do is completely kill the table and recreate it with the correct regions. -- 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-7415) [snapshots] Add task information to snapshot operation
[ https://issues.apache.org/jira/browse/HBASE-7415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13622033#comment-13622033 ] Matteo Bertozzi commented on HBASE-7415: committed to 0.95 and trunk, thanks guys for the review and Jesse for the patch. anyone wants it in 94? [snapshots] Add task information to snapshot operation -- Key: HBASE-7415 URL: https://issues.apache.org/jira/browse/HBASE-7415 Project: HBase Issue Type: New Feature Components: Client, master, regionserver, snapshots, Zookeeper Reporter: Jesse Yates Assignee: Jesse Yates Fix For: 0.95.1 Attachments: HBASE-7415-0.94.patch, HBASE-7415-0.94-v1.patch, hbase-7415-v0.patch, hbase-7415-v1.patch, HBASE-7415-v1-rebase.patch, HBASE-7415-v2.patch, HBASE-7415-v3.patch, HBASE-7415-v4.patch, HBASE-7415-v4.patch, HBase_Snapshot_Task_UI.png Snapshot operations should have some sort of progresss information available via the WebUI so admins can track progress of operations. This should go a long way to enable 'good' admins to not hose their clusters by running concurrent snapshot operations (e.g. rename while a clone is in progress). -- 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-8267) Add some resources checker for tests
Nicolas Liochon created HBASE-8267: -- Summary: Add some resources checker for tests Key: HBASE-8267 URL: https://issues.apache.org/jira/browse/HBASE-8267 Project: HBase Issue Type: Bug Components: build, test Affects Versions: 0.96.0 Reporter: Nicolas Liochon Assignee: Nicolas Liochon Priority: Minor Fix For: 0.96.0 Attachments: 8267.v1.patch This may help to understand why precommit is often ok while trunk is always bad. -- 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-8267) Add some resources checker for tests
[ https://issues.apache.org/jira/browse/HBASE-8267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicolas Liochon updated HBASE-8267: --- Attachment: 8267.v1.patch Add some resources checker for tests Key: HBASE-8267 URL: https://issues.apache.org/jira/browse/HBASE-8267 Project: HBase Issue Type: Bug Components: build, test Affects Versions: 0.96.0 Reporter: Nicolas Liochon Assignee: Nicolas Liochon Priority: Minor Fix For: 0.96.0 Attachments: 8267.v1.patch This may help to understand why precommit is often ok while trunk is always bad. -- 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-8267) Add some resources checker for tests
[ https://issues.apache.org/jira/browse/HBASE-8267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicolas Liochon updated HBASE-8267: --- Status: Patch Available (was: Open) Add some resources checker for tests Key: HBASE-8267 URL: https://issues.apache.org/jira/browse/HBASE-8267 Project: HBase Issue Type: Bug Components: build, test Affects Versions: 0.96.0 Reporter: Nicolas Liochon Assignee: Nicolas Liochon Priority: Minor Fix For: 0.96.0 Attachments: 8267.v1.patch This may help to understand why precommit is often ok while trunk is always bad. -- 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-8256) Add category Flaky for tests which are flaky
[ https://issues.apache.org/jira/browse/HBASE-8256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13622043#comment-13622043 ] Nicolas Liochon commented on HBASE-8256: fwiw, I created HBASE-8267 to see if we can link flakyness to some lack of resources. Add category Flaky for tests which are flaky Key: HBASE-8256 URL: https://issues.apache.org/jira/browse/HBASE-8256 Project: HBase Issue Type: Bug Components: build, test Reporter: Jimmy Xiang Assignee: Jimmy Xiang To make the Jenkin build more useful, it is good to keep it blue/green. We can mark those flaky tests flaky, and don't run them by default. However, people can still run them. We can also set up a Jekin build just for those flaky tests. -- 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-7615) Add metrics for snapshots
[ https://issues.apache.org/jira/browse/HBASE-7615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13622046#comment-13622046 ] Matteo Bertozzi commented on HBASE-7615: committed to 0.95 and trunk, thanks for the reviews guys. Anyone wants it in 94? Add metrics for snapshots - Key: HBASE-7615 URL: https://issues.apache.org/jira/browse/HBASE-7615 Project: HBase Issue Type: Sub-task Reporter: Ted Yu Assignee: Matteo Bertozzi Attachments: HBASE-7615-0.94.patch, HBASE-7615-0.94-v1.patch, HBASE-7615.patch, HBASE-7615.patch, HBASE-7615.patch, HBASE-7615-v0.patch, HBASE-7615-v0-ui-corrupted.png, HBASE-7615-v0-ui.png, HBASE-7615-v1.patch, HBASE-7615-v2.patch, HBASE-7615-v3.patch, HBASE-7615-v4.patch Metrics should be added for snapshot. From Matteo: Output that we have in SnapshotInfo should be covered: %d HFiles (%d in archive), total size %s (%.2f%% %s shared with the source table) Jesse mentioned snaphot counts, average time to completion. I think we should have counts for successful / failed snapshots. -- 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-8266) Master cannot start if TableNotFoundException is thrown while partial table recovery
[
https://issues.apache.org/jira/browse/HBASE-8266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13622049#comment-13622049
]
ramkrishna.s.vasudevan commented on HBASE-8266:
---
[~mbertozzi]
Am wondering if that could be the reason because i did not replace my jar at
all. But yes it is a classpath issue.
Anyway this issue is possible at any case if in the case of IOException.
So the after effect has to be handled.
Master cannot start if TableNotFoundException is thrown while partial table
recovery
Key: HBASE-8266
URL: https://issues.apache.org/jira/browse/HBASE-8266
Project: HBase
Issue Type: Bug
Affects Versions: 0.95.0, 0.94.6
Reporter: ramkrishna.s.vasudevan
Assignee: ramkrishna.s.vasudevan
Priority: Critical
Fix For: 0.95.0, 0.98.0, 0.94.7
I was trying to create a table. The table creation failed
{code}
java.io.IOException: java.util.concurrent.ExecutionException:
java.lang.IllegalStateException: Could not instantiate a region instance.
at
org.apache.hadoop.hbase.util.ModifyRegionUtils.createRegions(ModifyRegionUtils.java:133)
at
org.apache.hadoop.hbase.master.handler.CreateTableHandler.handleCreateHdfsRegions(CreateTableHandler.java:256)
at
org.apache.hadoop.hbase.master.handler.CreateTableHandler.handleCreateTable(CreateTableHandler.java:204)
at
org.apache.hadoop.hbase.master.handler.CreateTableHandler.process(CreateTableHandler.java:153)
at
org.apache.hadoop.hbase.executor.EventHandler.run(EventHandler.java:130)
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:662)
Caused by: java.util.concurrent.ExecutionException:
java.lang.IllegalStateException: Could not instantiate a region instance.
at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:222)
at java.util.concurrent.FutureTask.get(FutureTask.java:83)
at
org.apache.hadoop.hbase.util.ModifyRegionUtils.createRegions(ModifyRegionUtils.java:126)
... 7 more
Caused by: java.lang.IllegalStateException: Could not instantiate a region
instance.
at
org.apache.hadoop.hbase.regionserver.HRegion.newHRegion(HRegion.java:3765)
at
org.apache.hadoop.hbase.regionserver.HRegion.createHRegion(HRegion.java:3870)
at
org.apache.hadoop.hbase.util.ModifyRegionUtils$1.call(ModifyRegionUtils.java:106)
at
org.apache.hadoop.hbase.util.ModifyRegionUtils$1.call(ModifyRegionUtils.java:103)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
... 3 more
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at
org.apache.hadoop.hbase.regionserver.HRegion.newHRegion(HRegion.java:3762)
... 11 more
Caused by: java.lang.NoClassDefFoundError:
org/apache/hadoop/hbase/CompoundConfiguration$1
at
org.apache.hadoop.hbase.CompoundConfiguration.add(CompoundConfiguration.java:82)
at org.apache.hadoop.hbase.regionserver.HRegion.init(HRegion.java:438)
at org.apache.hadoop.hbase.regionserver.HRegion.init(HRegion.java:401)
... 16 more
{code}
Am not sure of the above failure. The same setup is able to create new
tables.
Now the table is already in ENABLING state. The master was restarted.
Now as the table was found in ENABLING state but not added to META the
EnableTableHandler
{code}
2013-04-03 18:33:03,850 FATAL org.apache.hadoop.hbase.master.HMaster:
Unhandled exception. Starting shutdown.
org.apache.hadoop.hbase.exceptions.TableNotFoundException: TestTable
at
org.apache.hadoop.hbase.master.handler.EnableTableHandler.prepare(EnableTableHandler.java:89)
at
org.apache.hadoop.hbase.master.AssignmentManager.recoverTableInEnablingState(AssignmentManager.java:2586)
at
org.apache.hadoop.hbase.master.AssignmentManager.joinCluster(AssignmentManager.java:390)
at
[jira] [Commented] (HBASE-8266) Master cannot start if TableNotFoundException is thrown while partial table recovery
[
https://issues.apache.org/jira/browse/HBASE-8266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13622052#comment-13622052
]
Matteo Bertozzi commented on HBASE-8266:
In the CreateTableHandler.process() I see a big try catch without rethrow, are
you sure that you don't get the error just because this is a runtime error?
(not sure about that I haven't looked at the code yet, so maybe I'm missing
something)
{code}
public void process() {
...
} catch (Throwable e) {
LOG.error(Error trying to create the table + tableName, e);
{code}
Master cannot start if TableNotFoundException is thrown while partial table
recovery
Key: HBASE-8266
URL: https://issues.apache.org/jira/browse/HBASE-8266
Project: HBase
Issue Type: Bug
Affects Versions: 0.95.0, 0.94.6
Reporter: ramkrishna.s.vasudevan
Assignee: ramkrishna.s.vasudevan
Priority: Critical
Fix For: 0.95.0, 0.98.0, 0.94.7
I was trying to create a table. The table creation failed
{code}
java.io.IOException: java.util.concurrent.ExecutionException:
java.lang.IllegalStateException: Could not instantiate a region instance.
at
org.apache.hadoop.hbase.util.ModifyRegionUtils.createRegions(ModifyRegionUtils.java:133)
at
org.apache.hadoop.hbase.master.handler.CreateTableHandler.handleCreateHdfsRegions(CreateTableHandler.java:256)
at
org.apache.hadoop.hbase.master.handler.CreateTableHandler.handleCreateTable(CreateTableHandler.java:204)
at
org.apache.hadoop.hbase.master.handler.CreateTableHandler.process(CreateTableHandler.java:153)
at
org.apache.hadoop.hbase.executor.EventHandler.run(EventHandler.java:130)
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:662)
Caused by: java.util.concurrent.ExecutionException:
java.lang.IllegalStateException: Could not instantiate a region instance.
at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:222)
at java.util.concurrent.FutureTask.get(FutureTask.java:83)
at
org.apache.hadoop.hbase.util.ModifyRegionUtils.createRegions(ModifyRegionUtils.java:126)
... 7 more
Caused by: java.lang.IllegalStateException: Could not instantiate a region
instance.
at
org.apache.hadoop.hbase.regionserver.HRegion.newHRegion(HRegion.java:3765)
at
org.apache.hadoop.hbase.regionserver.HRegion.createHRegion(HRegion.java:3870)
at
org.apache.hadoop.hbase.util.ModifyRegionUtils$1.call(ModifyRegionUtils.java:106)
at
org.apache.hadoop.hbase.util.ModifyRegionUtils$1.call(ModifyRegionUtils.java:103)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
... 3 more
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at
org.apache.hadoop.hbase.regionserver.HRegion.newHRegion(HRegion.java:3762)
... 11 more
Caused by: java.lang.NoClassDefFoundError:
org/apache/hadoop/hbase/CompoundConfiguration$1
at
org.apache.hadoop.hbase.CompoundConfiguration.add(CompoundConfiguration.java:82)
at org.apache.hadoop.hbase.regionserver.HRegion.init(HRegion.java:438)
at org.apache.hadoop.hbase.regionserver.HRegion.init(HRegion.java:401)
... 16 more
{code}
Am not sure of the above failure. The same setup is able to create new
tables.
Now the table is already in ENABLING state. The master was restarted.
Now as the table was found in ENABLING state but not added to META the
EnableTableHandler
{code}
2013-04-03 18:33:03,850 FATAL org.apache.hadoop.hbase.master.HMaster:
Unhandled exception. Starting shutdown.
org.apache.hadoop.hbase.exceptions.TableNotFoundException: TestTable
at
org.apache.hadoop.hbase.master.handler.EnableTableHandler.prepare(EnableTableHandler.java:89)
at
org.apache.hadoop.hbase.master.AssignmentManager.recoverTableInEnablingState(AssignmentManager.java:2586)
at
[jira] [Commented] (HBASE-5525) Truncate and preserve region boundaries option
[ https://issues.apache.org/jira/browse/HBASE-5525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13622053#comment-13622053 ] Jean-Marc Spaggiari commented on HBASE-5525: I tested it on 0.94 and it's working fine. Let me know if you are experiencing any issue with the patch applied. Truncate and preserve region boundaries option -- Key: HBASE-5525 URL: https://issues.apache.org/jira/browse/HBASE-5525 Project: HBase Issue Type: New Feature Affects Versions: 0.96.0 Reporter: Jean-Daniel Cryans Assignee: Kevin Odell Labels: newbie, noob Fix For: 0.95.1 Attachments: HBASE-5525.patch, HBASE-5525-v1-0.94.patch, HBASE-5525-v1-0.95.patch, HBASE-5525-v1-trunk.patch, HBASE-5525-v1-trunk.patch A tool that would be useful for testing (and maybe in prod too) would be a truncate option to keep the current region boundaries. Right now what you have to do is completely kill the table and recreate it with the correct regions. -- 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-8266) Master cannot start if TableNotFoundException is thrown while partial table recovery
[
https://issues.apache.org/jira/browse/HBASE-8266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13622054#comment-13622054
]
ramkrishna.s.vasudevan commented on HBASE-8266:
---
I am getting the error.
{code}
2013-04-03 18:32:31,637 ERROR
org.apache.hadoop.hbase.master.handler.CreateTableHandler: Error trying to
create the table TestTable
{code}
But we do not clear the ENABLING znode. We need that for recreating incase of
master failover. But here the znode is available but the Meta does not have
any entry and hence on master restart we get this error.
Master cannot start if TableNotFoundException is thrown while partial table
recovery
Key: HBASE-8266
URL: https://issues.apache.org/jira/browse/HBASE-8266
Project: HBase
Issue Type: Bug
Affects Versions: 0.95.0, 0.94.6
Reporter: ramkrishna.s.vasudevan
Assignee: ramkrishna.s.vasudevan
Priority: Critical
Fix For: 0.95.0, 0.98.0, 0.94.7
I was trying to create a table. The table creation failed
{code}
java.io.IOException: java.util.concurrent.ExecutionException:
java.lang.IllegalStateException: Could not instantiate a region instance.
at
org.apache.hadoop.hbase.util.ModifyRegionUtils.createRegions(ModifyRegionUtils.java:133)
at
org.apache.hadoop.hbase.master.handler.CreateTableHandler.handleCreateHdfsRegions(CreateTableHandler.java:256)
at
org.apache.hadoop.hbase.master.handler.CreateTableHandler.handleCreateTable(CreateTableHandler.java:204)
at
org.apache.hadoop.hbase.master.handler.CreateTableHandler.process(CreateTableHandler.java:153)
at
org.apache.hadoop.hbase.executor.EventHandler.run(EventHandler.java:130)
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:662)
Caused by: java.util.concurrent.ExecutionException:
java.lang.IllegalStateException: Could not instantiate a region instance.
at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:222)
at java.util.concurrent.FutureTask.get(FutureTask.java:83)
at
org.apache.hadoop.hbase.util.ModifyRegionUtils.createRegions(ModifyRegionUtils.java:126)
... 7 more
Caused by: java.lang.IllegalStateException: Could not instantiate a region
instance.
at
org.apache.hadoop.hbase.regionserver.HRegion.newHRegion(HRegion.java:3765)
at
org.apache.hadoop.hbase.regionserver.HRegion.createHRegion(HRegion.java:3870)
at
org.apache.hadoop.hbase.util.ModifyRegionUtils$1.call(ModifyRegionUtils.java:106)
at
org.apache.hadoop.hbase.util.ModifyRegionUtils$1.call(ModifyRegionUtils.java:103)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
... 3 more
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at
org.apache.hadoop.hbase.regionserver.HRegion.newHRegion(HRegion.java:3762)
... 11 more
Caused by: java.lang.NoClassDefFoundError:
org/apache/hadoop/hbase/CompoundConfiguration$1
at
org.apache.hadoop.hbase.CompoundConfiguration.add(CompoundConfiguration.java:82)
at org.apache.hadoop.hbase.regionserver.HRegion.init(HRegion.java:438)
at org.apache.hadoop.hbase.regionserver.HRegion.init(HRegion.java:401)
... 16 more
{code}
Am not sure of the above failure. The same setup is able to create new
tables.
Now the table is already in ENABLING state. The master was restarted.
Now as the table was found in ENABLING state but not added to META the
EnableTableHandler
{code}
2013-04-03 18:33:03,850 FATAL org.apache.hadoop.hbase.master.HMaster:
Unhandled exception. Starting shutdown.
org.apache.hadoop.hbase.exceptions.TableNotFoundException: TestTable
at
org.apache.hadoop.hbase.master.handler.EnableTableHandler.prepare(EnableTableHandler.java:89)
at
org.apache.hadoop.hbase.master.AssignmentManager.recoverTableInEnablingState(AssignmentManager.java:2586)
[jira] [Commented] (HBASE-5525) Truncate and preserve region boundaries option
[ https://issues.apache.org/jira/browse/HBASE-5525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13622071#comment-13622071 ] Matteo Bertozzi commented on HBASE-5525: I've committed the missing file in trunk and 95, so the shell should work again. [~jmspaggi] I don't see this patch in 94 yet, it should be backported? Truncate and preserve region boundaries option -- Key: HBASE-5525 URL: https://issues.apache.org/jira/browse/HBASE-5525 Project: HBase Issue Type: New Feature Affects Versions: 0.96.0 Reporter: Jean-Daniel Cryans Assignee: Kevin Odell Labels: newbie, noob Fix For: 0.95.1 Attachments: HBASE-5525.patch, HBASE-5525-v1-0.94.patch, HBASE-5525-v1-0.95.patch, HBASE-5525-v1-trunk.patch, HBASE-5525-v1-trunk.patch A tool that would be useful for testing (and maybe in prod too) would be a truncate option to keep the current region boundaries. Right now what you have to do is completely kill the table and recreate it with the correct regions. -- 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-8235) Adding inmemory CF attribute to LoadTest and PerformanceEvaluation tool
[
https://issues.apache.org/jira/browse/HBASE-8235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13622072#comment-13622072
]
Jean-Marc Spaggiari commented on HBASE-8235:
I'm +1 with it.
TestShell failed because of HBASE-5525.
Can you split this:
{code}
+ is served from in_memory. The HFile blocks are tried maximum
to be served from in memory;
{code}
so it's shorter than 100?
Adding inmemory CF attribute to LoadTest and PerformanceEvaluation tool
---
Key: HBASE-8235
URL: https://issues.apache.org/jira/browse/HBASE-8235
Project: HBase
Issue Type: Improvement
Reporter: ramkrishna.s.vasudevan
Assignee: ramkrishna.s.vasudevan
Fix For: 0.98.0
Attachments: HBASE-8235_1.patch, HBASE-8235.patch
Adding the inmemory CF attribute to the LoadTestTool and PerfEvaluation tool
will make it extensible to test such inmemory scenarios also.
--
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-7615) Add metrics for snapshots
[ https://issues.apache.org/jira/browse/HBASE-7615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13622074#comment-13622074 ] Hudson commented on HBASE-7615: --- Integrated in HBase-TRUNK #4012 (See [https://builds.apache.org/job/HBase-TRUNK/4012/]) HBASE-7615 Add metrics for snapshots (Revision 1464441) Result = FAILURE mbertozzi : Files : * /hbase/trunk/hbase-hadoop-compat/src/main/java/org/apache/hadoop/hbase/master/MetricsMasterSource.java * /hbase/trunk/hbase-hadoop1-compat/src/main/java/org/apache/hadoop/hbase/master/MetricsMasterSourceImpl.java * /hbase/trunk/hbase-hadoop2-compat/src/main/java/org/apache/hadoop/hbase/master/MetricsMasterSourceImpl.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/MetricsMaster.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/master/snapshot/CloneSnapshotHandler.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/master/snapshot/DisabledTableSnapshotHandler.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/master/snapshot/EnabledTableSnapshotHandler.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/master/snapshot/RestoreSnapshotHandler.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/master/snapshot/SnapshotManager.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/master/snapshot/TakeSnapshotHandler.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/snapshot/SnapshotInfo.java * /hbase/trunk/hbase-server/src/main/resources/hbase-webapps/master/snapshot.jsp * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/master/snapshot/TestSnapshotManager.java Add metrics for snapshots - Key: HBASE-7615 URL: https://issues.apache.org/jira/browse/HBASE-7615 Project: HBase Issue Type: Sub-task Reporter: Ted Yu Assignee: Matteo Bertozzi Attachments: HBASE-7615-0.94.patch, HBASE-7615-0.94-v1.patch, HBASE-7615.patch, HBASE-7615.patch, HBASE-7615.patch, HBASE-7615-v0.patch, HBASE-7615-v0-ui-corrupted.png, HBASE-7615-v0-ui.png, HBASE-7615-v1.patch, HBASE-7615-v2.patch, HBASE-7615-v3.patch, HBASE-7615-v4.patch Metrics should be added for snapshot. From Matteo: Output that we have in SnapshotInfo should be covered: %d HFiles (%d in archive), total size %s (%.2f%% %s shared with the source table) Jesse mentioned snaphot counts, average time to completion. I think we should have counts for successful / failed snapshots. -- 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-5525) Truncate and preserve region boundaries option
[ https://issues.apache.org/jira/browse/HBASE-5525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13622075#comment-13622075 ] Hudson commented on HBASE-5525: --- Integrated in HBase-TRUNK #4012 (See [https://builds.apache.org/job/HBase-TRUNK/4012/]) HBASE-5525 Truncate and preserve region boundaries option, addendum (Revision 1464425) Result = FAILURE mbertozzi : Files : * /hbase/trunk/hbase-server/src/main/ruby/shell/commands/truncate_preserve.rb Truncate and preserve region boundaries option -- Key: HBASE-5525 URL: https://issues.apache.org/jira/browse/HBASE-5525 Project: HBase Issue Type: New Feature Affects Versions: 0.96.0 Reporter: Jean-Daniel Cryans Assignee: Kevin Odell Labels: newbie, noob Fix For: 0.95.1 Attachments: HBASE-5525.patch, HBASE-5525-v1-0.94.patch, HBASE-5525-v1-0.95.patch, HBASE-5525-v1-trunk.patch, HBASE-5525-v1-trunk.patch A tool that would be useful for testing (and maybe in prod too) would be a truncate option to keep the current region boundaries. Right now what you have to do is completely kill the table and recreate it with the correct regions. -- 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-7415) [snapshots] Add task information to snapshot operation
[ https://issues.apache.org/jira/browse/HBASE-7415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13622076#comment-13622076 ] Hudson commented on HBASE-7415: --- Integrated in HBase-TRUNK #4012 (See [https://builds.apache.org/job/HBase-TRUNK/4012/]) HBASE-7415 Add task information to snapshot operation (Jesse Yates) (Revision 1464427) Result = FAILURE mbertozzi : Files : * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/master/handler/TableEventHandler.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/master/snapshot/CloneSnapshotHandler.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/master/snapshot/DisabledTableSnapshotHandler.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/master/snapshot/RestoreSnapshotHandler.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/master/snapshot/TakeSnapshotHandler.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/snapshot/RestoreSnapshotHelper.java * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/snapshot/TestRestoreSnapshotHelper.java [snapshots] Add task information to snapshot operation -- Key: HBASE-7415 URL: https://issues.apache.org/jira/browse/HBASE-7415 Project: HBase Issue Type: New Feature Components: Client, master, regionserver, snapshots, Zookeeper Reporter: Jesse Yates Assignee: Jesse Yates Fix For: 0.95.1 Attachments: HBASE-7415-0.94.patch, HBASE-7415-0.94-v1.patch, hbase-7415-v0.patch, hbase-7415-v1.patch, HBASE-7415-v1-rebase.patch, HBASE-7415-v2.patch, HBASE-7415-v3.patch, HBASE-7415-v4.patch, HBASE-7415-v4.patch, HBase_Snapshot_Task_UI.png Snapshot operations should have some sort of progresss information available via the WebUI so admins can track progress of operations. This should go a long way to enable 'good' admins to not hose their clusters by running concurrent snapshot operations (e.g. rename while a clone is in progress). -- 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-5525) Truncate and preserve region boundaries option
[ https://issues.apache.org/jira/browse/HBASE-5525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13622077#comment-13622077 ] Jean-Marc Spaggiari commented on HBASE-5525: [~mbertozzi], I applied it locally to test it and it works fine. Patch for 0.94 is already attached. It's a very simple patch and useful for testing. So I think it should be applied to 0.94 too. Truncate and preserve region boundaries option -- Key: HBASE-5525 URL: https://issues.apache.org/jira/browse/HBASE-5525 Project: HBase Issue Type: New Feature Affects Versions: 0.96.0 Reporter: Jean-Daniel Cryans Assignee: Kevin Odell Labels: newbie, noob Fix For: 0.95.1 Attachments: HBASE-5525.patch, HBASE-5525-v1-0.94.patch, HBASE-5525-v1-0.95.patch, HBASE-5525-v1-trunk.patch, HBASE-5525-v1-trunk.patch A tool that would be useful for testing (and maybe in prod too) would be a truncate option to keep the current region boundaries. Right now what you have to do is completely kill the table and recreate it with the correct regions. -- 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-7615) Add metrics for snapshots
[ https://issues.apache.org/jira/browse/HBASE-7615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13622081#comment-13622081 ] Hudson commented on HBASE-7615: --- Integrated in hbase-0.95 #123 (See [https://builds.apache.org/job/hbase-0.95/123/]) HBASE-7615 Add metrics for snapshots (Revision 1464443) Result = FAILURE mbertozzi : Files : * /hbase/branches/0.95/hbase-hadoop-compat/src/main/java/org/apache/hadoop/hbase/master/MetricsMasterSource.java * /hbase/branches/0.95/hbase-hadoop1-compat/src/main/java/org/apache/hadoop/hbase/master/MetricsMasterSourceImpl.java * /hbase/branches/0.95/hbase-hadoop2-compat/src/main/java/org/apache/hadoop/hbase/master/MetricsMasterSourceImpl.java * /hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/master/HMaster.java * /hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/master/MetricsMaster.java * /hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/master/snapshot/CloneSnapshotHandler.java * /hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/master/snapshot/DisabledTableSnapshotHandler.java * /hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/master/snapshot/EnabledTableSnapshotHandler.java * /hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/master/snapshot/RestoreSnapshotHandler.java * /hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/master/snapshot/SnapshotManager.java * /hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/master/snapshot/TakeSnapshotHandler.java * /hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/snapshot/SnapshotInfo.java * /hbase/branches/0.95/hbase-server/src/main/resources/hbase-webapps/master/snapshot.jsp * /hbase/branches/0.95/hbase-server/src/test/java/org/apache/hadoop/hbase/master/snapshot/TestSnapshotManager.java Add metrics for snapshots - Key: HBASE-7615 URL: https://issues.apache.org/jira/browse/HBASE-7615 Project: HBase Issue Type: Sub-task Reporter: Ted Yu Assignee: Matteo Bertozzi Attachments: HBASE-7615-0.94.patch, HBASE-7615-0.94-v1.patch, HBASE-7615.patch, HBASE-7615.patch, HBASE-7615.patch, HBASE-7615-v0.patch, HBASE-7615-v0-ui-corrupted.png, HBASE-7615-v0-ui.png, HBASE-7615-v1.patch, HBASE-7615-v2.patch, HBASE-7615-v3.patch, HBASE-7615-v4.patch Metrics should be added for snapshot. From Matteo: Output that we have in SnapshotInfo should be covered: %d HFiles (%d in archive), total size %s (%.2f%% %s shared with the source table) Jesse mentioned snaphot counts, average time to completion. I think we should have counts for successful / failed snapshots. -- 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-5525) Truncate and preserve region boundaries option
[ https://issues.apache.org/jira/browse/HBASE-5525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13622082#comment-13622082 ] Hudson commented on HBASE-5525: --- Integrated in hbase-0.95 #123 (See [https://builds.apache.org/job/hbase-0.95/123/]) HBASE-5525 Truncate and preserve region boundaries option, addendum (Revision 1464426) Result = FAILURE mbertozzi : Files : * /hbase/branches/0.95/hbase-server/src/main/ruby/shell/commands/truncate_preserve.rb Truncate and preserve region boundaries option -- Key: HBASE-5525 URL: https://issues.apache.org/jira/browse/HBASE-5525 Project: HBase Issue Type: New Feature Affects Versions: 0.96.0 Reporter: Jean-Daniel Cryans Assignee: Kevin Odell Labels: newbie, noob Fix For: 0.95.1 Attachments: HBASE-5525.patch, HBASE-5525-v1-0.94.patch, HBASE-5525-v1-0.95.patch, HBASE-5525-v1-trunk.patch, HBASE-5525-v1-trunk.patch A tool that would be useful for testing (and maybe in prod too) would be a truncate option to keep the current region boundaries. Right now what you have to do is completely kill the table and recreate it with the correct regions. -- 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-7415) [snapshots] Add task information to snapshot operation
[ https://issues.apache.org/jira/browse/HBASE-7415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13622083#comment-13622083 ] Hudson commented on HBASE-7415: --- Integrated in hbase-0.95 #123 (See [https://builds.apache.org/job/hbase-0.95/123/]) HBASE-7415 Add task information to snapshot operation (Jesse Yates) (Revision 1464429) Result = FAILURE mbertozzi : Files : * /hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/master/handler/TableEventHandler.java * /hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/master/snapshot/CloneSnapshotHandler.java * /hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/master/snapshot/DisabledTableSnapshotHandler.java * /hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/master/snapshot/RestoreSnapshotHandler.java * /hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/master/snapshot/TakeSnapshotHandler.java * /hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/snapshot/RestoreSnapshotHelper.java * /hbase/branches/0.95/hbase-server/src/test/java/org/apache/hadoop/hbase/snapshot/TestRestoreSnapshotHelper.java [snapshots] Add task information to snapshot operation -- Key: HBASE-7415 URL: https://issues.apache.org/jira/browse/HBASE-7415 Project: HBase Issue Type: New Feature Components: Client, master, regionserver, snapshots, Zookeeper Reporter: Jesse Yates Assignee: Jesse Yates Fix For: 0.95.1 Attachments: HBASE-7415-0.94.patch, HBASE-7415-0.94-v1.patch, hbase-7415-v0.patch, hbase-7415-v1.patch, HBASE-7415-v1-rebase.patch, HBASE-7415-v2.patch, HBASE-7415-v3.patch, HBASE-7415-v4.patch, HBASE-7415-v4.patch, HBase_Snapshot_Task_UI.png Snapshot operations should have some sort of progresss information available via the WebUI so admins can track progress of operations. This should go a long way to enable 'good' admins to not hose their clusters by running concurrent snapshot operations (e.g. rename while a clone is in progress). -- 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-7959) HBCK skips regions that have been recently modified, which then leads to it to report holes in region chain
[
https://issues.apache.org/jira/browse/HBASE-7959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13622087#comment-13622087
]
Jean-Marc Spaggiari commented on HBASE-7959:
If HBCK is instructed to fix the holes and we detect those temporaty
conditions, can't we just log a warning and skip the fix? The best option will
be to still consider the recently moved regions in the holes detection. [~enis]
are you going to provide a patch to fix that?
HBCK skips regions that have been recently modified, which then leads to it
to report holes in region chain
---
Key: HBASE-7959
URL: https://issues.apache.org/jira/browse/HBASE-7959
Project: HBase
Issue Type: Bug
Components: hbck
Reporter: Enis Soztutar
Fix For: 0.98.0, 0.94.8
While lots of region splits going on, HBCK incorrectly reports
inconsistencies since it skips recently modified, but does not take those
into account for computing the region chain.
{code}
13/02/28 03:33:16 WARN util.HBaseFsck: Region { meta =
cluster_test,,1362021481742.69639761fdf693ab1e2bf33f523cd1ae., hdfs =
NN:8020/apps/hbase-trunk/data/cluster_test/69639761fdf693ab1e2bf33f523cd1ae,
deployed = } was recently modified -- skipping
13/02/28 03:33:16 DEBUG util.HBaseFsck: There are 23 region info entries
ERROR: (region
cluster_test,0ccc,1362021481742.ec3ba583b4ea01393591572bf1f31e07.) First
region should start with an empty key. You need to create a new region and
regioninfo in HDFS to plug the hole.
ERROR: Found inconsistency in table cluster_test
Summary:
-ROOT- is okay.
Number of regions: 1
Deployed on: RSs
.META. is okay.
Number of regions: 1
Deployed on: RSs
Table cluster_test is inconsistent.
Number of regions: 19
Deployed on: RSs
1 inconsistencies detected.
Status: INCONSISTENT
{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-7615) Add metrics for snapshots
[ https://issues.apache.org/jira/browse/HBASE-7615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13622121#comment-13622121 ] Hudson commented on HBASE-7615: --- Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #476 (See [https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/476/]) HBASE-7615 Add metrics for snapshots (Revision 1464441) Result = FAILURE mbertozzi : Files : * /hbase/trunk/hbase-hadoop-compat/src/main/java/org/apache/hadoop/hbase/master/MetricsMasterSource.java * /hbase/trunk/hbase-hadoop1-compat/src/main/java/org/apache/hadoop/hbase/master/MetricsMasterSourceImpl.java * /hbase/trunk/hbase-hadoop2-compat/src/main/java/org/apache/hadoop/hbase/master/MetricsMasterSourceImpl.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/MetricsMaster.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/master/snapshot/CloneSnapshotHandler.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/master/snapshot/DisabledTableSnapshotHandler.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/master/snapshot/EnabledTableSnapshotHandler.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/master/snapshot/RestoreSnapshotHandler.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/master/snapshot/SnapshotManager.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/master/snapshot/TakeSnapshotHandler.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/snapshot/SnapshotInfo.java * /hbase/trunk/hbase-server/src/main/resources/hbase-webapps/master/snapshot.jsp * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/master/snapshot/TestSnapshotManager.java Add metrics for snapshots - Key: HBASE-7615 URL: https://issues.apache.org/jira/browse/HBASE-7615 Project: HBase Issue Type: Sub-task Reporter: Ted Yu Assignee: Matteo Bertozzi Attachments: HBASE-7615-0.94.patch, HBASE-7615-0.94-v1.patch, HBASE-7615.patch, HBASE-7615.patch, HBASE-7615.patch, HBASE-7615-v0.patch, HBASE-7615-v0-ui-corrupted.png, HBASE-7615-v0-ui.png, HBASE-7615-v1.patch, HBASE-7615-v2.patch, HBASE-7615-v3.patch, HBASE-7615-v4.patch Metrics should be added for snapshot. From Matteo: Output that we have in SnapshotInfo should be covered: %d HFiles (%d in archive), total size %s (%.2f%% %s shared with the source table) Jesse mentioned snaphot counts, average time to completion. I think we should have counts for successful / failed snapshots. -- 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-8207) Replication could have data loss when machine name contains hyphen -
[
https://issues.apache.org/jira/browse/HBASE-8207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13622120#comment-13622120
]
Hudson commented on HBASE-8207:
---
Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #476 (See
[https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/476/])
HBASE-8207 Don't use hdfs append during lease recovery (Revision 1463957)
Result = FAILURE
nkeywal :
Files :
*
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/util/FSHDFSUtils.java
*
/hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/wal/TestHLog.java
Replication could have data loss when machine name contains hyphen -
--
Key: HBASE-8207
URL: https://issues.apache.org/jira/browse/HBASE-8207
Project: HBase
Issue Type: Bug
Components: Replication
Affects Versions: 0.95.0, 0.94.6
Reporter: Jeffrey Zhong
Assignee: Jeffrey Zhong
Priority: Critical
Fix For: 0.95.0, 0.98.0, 0.94.7
Attachments: 8207-trunk-addendum.txt, 8207_v3.patch, failed.txt,
hbase-8207-0.94-v1.patch, hbase-8207.patch, hbase-8207_v1.patch,
hbase-8207_v2.patch, hbase-8207_v2.patch, HBASE-8212-94.patch
In the recent test case TestReplication* failures, I'm finally able to find
the cause(or one of causes) for its intermittent failures.
When a machine name contains -, it breaks the function
ReplicationSource.checkIfQueueRecovered. It causes the following issue:
deadRegionServers list is way off so that replication doesn't wait for log
splitting finish for a wal file and move on to the next one(data loss)
You can see that replication use those weird paths constructed from
deadRegionServers to check a file existence
{code}
2013-03-26 21:26:51,385 INFO
[ReplicationExecutor-0.replicationSource,2-ip-10-197-0-156.us-west-1.compute.internal,52170,1364333181125]
regionserver.ReplicationSource(524): Possible location
hdfs://localhost:52882/user/ec2-user/hbase/.logs/1.compute.internal,52170,1364333181125/ip-10-197-0-156.us-west-1.compute.internal%252C52170%252C1364333181125.1364333199540
2013-03-26 21:26:51,386 INFO
[ReplicationExecutor-0.replicationSource,2-ip-10-197-0-156.us-west-1.compute.internal,52170,1364333181125]
regionserver.ReplicationSource(524): Possible location
hdfs://localhost:52882/user/ec2-user/hbase/.logs/1.compute.internal,52170,1364333181125-splitting/ip-10-197-0-156.us-west-1.compute.internal%252C52170%252C1364333181125.1364333199540
2013-03-26 21:26:51,387 INFO
[ReplicationExecutor-0.replicationSource,2-ip-10-197-0-156.us-west-1.compute.internal,52170,1364333181125]
regionserver.ReplicationSource(524): Possible location
hdfs://localhost:52882/user/ec2-user/hbase/.logs/west/ip-10-197-0-156.us-west-1.compute.internal%252C52170%252C1364333181125.1364333199540
2013-03-26 21:26:51,389 INFO
[ReplicationExecutor-0.replicationSource,2-ip-10-197-0-156.us-west-1.compute.internal,52170,1364333181125]
regionserver.ReplicationSource(524): Possible location
hdfs://localhost:52882/user/ec2-user/hbase/.logs/west-splitting/ip-10-197-0-156.us-west-1.compute.internal%252C52170%252C1364333181125.1364333199540
2013-03-26 21:26:51,391 INFO
[ReplicationExecutor-0.replicationSource,2-ip-10-197-0-156.us-west-1.compute.internal,52170,1364333181125]
regionserver.ReplicationSource(524): Possible location
hdfs://localhost:52882/user/ec2-user/hbase/.logs/156.us/ip-10-197-0-156.us-west-1.compute.internal%252C52170%252C1364333181125.1364333199540
2013-03-26 21:26:51,394 INFO
[ReplicationExecutor-0.replicationSource,2-ip-10-197-0-156.us-west-1.compute.internal,52170,1364333181125]
regionserver.ReplicationSource(524): Possible location
hdfs://localhost:52882/user/ec2-user/hbase/.logs/156.us-splitting/ip-10-197-0-156.us-west-1.compute.internal%252C52170%252C1364333181125.1364333199540
2013-03-26 21:26:51,396 INFO
[ReplicationExecutor-0.replicationSource,2-ip-10-197-0-156.us-west-1.compute.internal,52170,1364333181125]
regionserver.ReplicationSource(524): Possible location
hdfs://localhost:52882/user/ec2-user/hbase/.logs/0/ip-10-197-0-156.us-west-1.compute.internal%252C52170%252C1364333181125.1364333199540
2013-03-26 21:26:51,398 INFO
[ReplicationExecutor-0.replicationSource,2-ip-10-197-0-156.us-west-1.compute.internal,52170,1364333181125]
regionserver.ReplicationSource(524): Possible location
hdfs://localhost:52882/user/ec2-user/hbase/.logs/0-splitting/ip-10-197-0-156.us-west-1.compute.internal%252C52170%252C1364333181125.1364333199540
{code}
This happened in the recent test failure in
http://54.241.6.143/job/HBase-0.94/org.apache.hbase$hbase/21/testReport/junit/org.apache.hadoop.hbase.replication/TestReplicationQueueFailover/queueFailover/?auto_refresh=false
[jira] [Commented] (HBASE-8263) Master LogSplitting metrics update wrong counters
[
https://issues.apache.org/jira/browse/HBASE-8263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13622122#comment-13622122
]
Hudson commented on HBASE-8263:
---
Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #476 (See
[https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/476/])
HBASE-8263 Master LogSplitting metrics update wrong counters (Revision
1464268)
Result = FAILURE
stack :
Files :
*
/hbase/trunk/hbase-hadoop1-compat/src/main/java/org/apache/hadoop/hbase/master/MetricsMasterSourceImpl.java
*
/hbase/trunk/hbase-hadoop2-compat/src/main/java/org/apache/hadoop/hbase/master/MetricsMasterSourceImpl.java
Master LogSplitting metrics update wrong counters
-
Key: HBASE-8263
URL: https://issues.apache.org/jira/browse/HBASE-8263
Project: HBase
Issue Type: Bug
Components: metrics
Reporter: Jeffrey Zhong
Assignee: Jeffrey Zhong
Priority: Minor
Fix For: 0.95.1
Attachments: hbase-8263.patch
Wrong counters are updated as you can see in
MetricsMasterSourceImpl.java#init()
{code}
splitTimeHisto = metricsRegistry.newHistogram(SPLIT_SIZE_NAME,
SPLIT_SIZE_DESC);
splitSizeHisto = metricsRegistry.newHistogram(SPLIT_TIME_NAME,
SPLIT_TIME_DESC);
{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-8231) delete tests in table_tests.rb(TestShell) always running on empty table.
[
https://issues.apache.org/jira/browse/HBASE-8231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13622123#comment-13622123
]
Hudson commented on HBASE-8231:
---
Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #476 (See
[https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/476/])
HBASE-8231 delete tests in table_tests.rb(TestShell) always running on
empty table (Revision 1464283)
Result = FAILURE
stack :
Files :
* /hbase/trunk/hbase-server/src/test/ruby/hbase/table_test.rb
delete tests in table_tests.rb(TestShell) always running on empty table.
Key: HBASE-8231
URL: https://issues.apache.org/jira/browse/HBASE-8231
Project: HBase
Issue Type: Bug
Components: scripts
Affects Versions: 0.95.0, 0.94.6
Reporter: rajeshbabu
Assignee: rajeshbabu
Fix For: 0.95.1, 0.94.7
Attachments: HBASE-8231.patch
In ruby,tests within the same test class are invoked in alphabetical order,so
delete test cases are running on a table before adding any entry.
TestShell logs showing Row not found for each delete test everytime.
{code}
ERROR: Row Not Found
Here is some help for this command:
Delete all cells in a given row; pass a table name, row, and optionally
a column and timestamp. Examples:
hbase deleteall 't1', 'r1'
hbase deleteall 't1', 'r1', 'c1'
hbase deleteall 't1', 'r1', 'c1', ts1
The same commands also can be run on a table reference. Suppose you had a
reference
t to table 't1', the corresponding command would be:
hbase t.deleteall 'r1'
hbase t.deleteall 'r1', 'c1'
hbase t.deleteall 'r1', 'c1', ts1
{code}
Before deleting a row we are checking whether the row is present or not.
{code}
def _deleteall_internal(row, column = nil, timestamp =
org.apache.hadoop.hbase.HConstants::LATEST_TIMESTAMP)
raise ArgumentError, Row Not Found if _get_internal(row).nil?
{code}
Need to improve delete tests in table_tests.rb.
--
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-8188) Avoid unnecessary row compare in StoreScanner
[ https://issues.apache.org/jira/browse/HBASE-8188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13622126#comment-13622126 ] Hudson commented on HBASE-8188: --- Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #476 (See [https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/476/]) HBASE-8188 Avoid unnecessary row compare in StoreScanner (Revision 1464287) Result = FAILURE larsh : Files : * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/StoreScanner.java Avoid unnecessary row compare in StoreScanner - Key: HBASE-8188 URL: https://issues.apache.org/jira/browse/HBASE-8188 Project: HBase Issue Type: Bug Reporter: Lars Hofhansl Assignee: Lars Hofhansl Fix For: 0.95.1, 0.98.0, 0.94.7 Attachments: 8188-0.94-experimental.txt, 8188-0.94.txt, 8188-0.96.txt, 8188-0.96.txt, 8188-0.96.txt, 8188-0.96.txt When scanner batching disable (which is the default) a row compare in StoreScanner avoided, because only entire rows of data are requested. This provides a slight performance gain, especially for tall tables (and when all data is in the cache) -- 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-8241) Fix the bad dependency on netty from HDFS
[ https://issues.apache.org/jira/browse/HBASE-8241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13622127#comment-13622127 ] Hudson commented on HBASE-8241: --- Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #476 (See [https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/476/]) HBASE-8241 Fix the bad dependency on netty from HDFS (Revision 1464041) Result = FAILURE nkeywal : Files : * /hbase/trunk/pom.xml Fix the bad dependency on netty from HDFS - Key: HBASE-8241 URL: https://issues.apache.org/jira/browse/HBASE-8241 Project: HBase Issue Type: Bug Components: build, Client, master, regionserver Affects Versions: 0.96.0 Reporter: Nicolas Liochon Assignee: Nicolas Liochon Fix For: 0.95.1, 0.96.0 Attachments: HBASE-8241.v1.patch Even if it's fixed on trunk branch-2, the current version of hdfs still has a previous version of netty, with a different group id. Let's fix this. -- 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-7923) force unassign can confirm region online on any RS to get rid of double assignments.
[
https://issues.apache.org/jira/browse/HBASE-7923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13622129#comment-13622129
]
Hudson commented on HBASE-7923:
---
Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #476 (See
[https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/476/])
HBASE-7923 force unassign can confirm region online on any RS to get rid of
double assignments (Revision 1464232)
Result = FAILURE
stack :
Files :
*
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/master/HMaster.java
force unassign can confirm region online on any RS to get rid of double
assignments.
Key: HBASE-7923
URL: https://issues.apache.org/jira/browse/HBASE-7923
Project: HBase
Issue Type: Improvement
Reporter: rajeshbabu
Assignee: rajeshbabu
Fix For: 0.95.1
Attachments: HBASE-7923_2.patch, HBASE-7923_3.patch, HBASE-7923.patch
Presently in force unassign we are offlining a region from AM and reassigning
it, which may cause double assignments.
{code}
this.assignmentManager.regionOffline(hri);
assignRegion(hri);
{code}
Any way if a region is not served by any RS we are offlining the region from
AM.
{code}
if (t instanceof NotServingRegionException) {
if (transitionInZK) {
deleteClosingOrClosedNode(region);
}
regionOffline(region);
return;
}
{code}
We can change as below just to confirm whether region online on any RS.
{code}
this.assignmentManager.unassign(hri,force);
if(!this.assignmentManager.getRegionStates().isRegionInTransition(hri)
!this.assignmentManager.getRegionStates().isRegionAssigned(hri) ){
assignRegion(hri);
}
{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-5525) Truncate and preserve region boundaries option
[ https://issues.apache.org/jira/browse/HBASE-5525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13622130#comment-13622130 ] Hudson commented on HBASE-5525: --- Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #476 (See [https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/476/]) HBASE-5525 Truncate and preserve region boundaries option, addendum (Revision 1464425) HBASE-5525 Truncate and preserve region boundaries option (Revision 1464290) Result = FAILURE mbertozzi : Files : * /hbase/trunk/hbase-server/src/main/ruby/shell/commands/truncate_preserve.rb stack : Files : * /hbase/trunk/hbase-server/src/main/ruby/hbase/admin.rb * /hbase/trunk/hbase-server/src/main/ruby/shell.rb Truncate and preserve region boundaries option -- Key: HBASE-5525 URL: https://issues.apache.org/jira/browse/HBASE-5525 Project: HBase Issue Type: New Feature Affects Versions: 0.96.0 Reporter: Jean-Daniel Cryans Assignee: Kevin Odell Labels: newbie, noob Fix For: 0.95.1 Attachments: HBASE-5525.patch, HBASE-5525-v1-0.94.patch, HBASE-5525-v1-0.95.patch, HBASE-5525-v1-trunk.patch, HBASE-5525-v1-trunk.patch A tool that would be useful for testing (and maybe in prod too) would be a truncate option to keep the current region boundaries. Right now what you have to do is completely kill the table and recreate it with the correct regions. -- 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-7745) Import uses System.out.println instead of logging
[ https://issues.apache.org/jira/browse/HBASE-7745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13622131#comment-13622131 ] Hudson commented on HBASE-7745: --- Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #476 (See [https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/476/]) HBASE-7745 Import uses System.out.println instead of logging (Revision 1464124) Result = FAILURE stack : Files : * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/mapreduce/Import.java Import uses System.out.println instead of logging - Key: HBASE-7745 URL: https://issues.apache.org/jira/browse/HBASE-7745 Project: HBase Issue Type: Improvement Components: mapreduce Reporter: Nick Dimiduk Assignee: Gustavo Anatoly Priority: Trivial Fix For: 0.95.1, 0.98.0 Attachments: HBASE-7745.patch Per the title. -- 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-7415) [snapshots] Add task information to snapshot operation
[ https://issues.apache.org/jira/browse/HBASE-7415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13622133#comment-13622133 ] Hudson commented on HBASE-7415: --- Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #476 (See [https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/476/]) HBASE-7415 Add task information to snapshot operation (Jesse Yates) (Revision 1464427) Result = FAILURE mbertozzi : Files : * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/master/handler/TableEventHandler.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/master/snapshot/CloneSnapshotHandler.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/master/snapshot/DisabledTableSnapshotHandler.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/master/snapshot/RestoreSnapshotHandler.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/master/snapshot/TakeSnapshotHandler.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/snapshot/RestoreSnapshotHelper.java * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/snapshot/TestRestoreSnapshotHelper.java [snapshots] Add task information to snapshot operation -- Key: HBASE-7415 URL: https://issues.apache.org/jira/browse/HBASE-7415 Project: HBase Issue Type: New Feature Components: Client, master, regionserver, snapshots, Zookeeper Reporter: Jesse Yates Assignee: Jesse Yates Fix For: 0.95.1 Attachments: HBASE-7415-0.94.patch, HBASE-7415-0.94-v1.patch, hbase-7415-v0.patch, hbase-7415-v1.patch, HBASE-7415-v1-rebase.patch, HBASE-7415-v2.patch, HBASE-7415-v3.patch, HBASE-7415-v4.patch, HBASE-7415-v4.patch, HBase_Snapshot_Task_UI.png Snapshot operations should have some sort of progresss information available via the WebUI so admins can track progress of operations. This should go a long way to enable 'good' admins to not hose their clusters by running concurrent snapshot operations (e.g. rename while a clone is in progress). -- 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-8257) [refGuide] adding object design section in Schema Design
[ https://issues.apache.org/jira/browse/HBASE-8257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13622134#comment-13622134 ] Hudson commented on HBASE-8257: --- Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #476 (See [https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/476/]) hbase-8257. refGuide. Adding object design section in Cust/Order Schema Design Case Study. (Revision 1464145) Result = FAILURE [refGuide] adding object design section in Schema Design - Key: HBASE-8257 URL: https://issues.apache.org/jira/browse/HBASE-8257 Project: HBase Issue Type: New Feature Reporter: Doug Meil Assignee: Doug Meil Attachments: schema_design_hbase_8257.xml.patch Added an object design sub-section in the Customer/Order Case Study in the Schema Design chapter. Renamed the Customer / Sales Case Study to Customer/Order because I found I was using both sales and order interchangeably and I think that was confusing, so now I'm only referring to Order Minor cleanup: fixed some of the section-ids in the Case Study section (from yesterday) -- 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-7401) Remove warning message about running 'hbase migrate'
[
https://issues.apache.org/jira/browse/HBASE-7401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13622135#comment-13622135
]
Hudson commented on HBASE-7401:
---
Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #476 (See
[https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/476/])
HBASE-7401 Remove warning message about running 'hbase migrate' (Revision
1464129)
Result = FAILURE
jmhsieh :
Files :
*
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/util/FSUtils.java
Remove warning message about running 'hbase migrate'
Key: HBASE-7401
URL: https://issues.apache.org/jira/browse/HBASE-7401
Project: HBase
Issue Type: Bug
Components: Usability
Affects Versions: 0.94.3, 0.96.0
Reporter: Jonathan Hsieh
Assignee: Jonathan Hsieh
Fix For: 0.95.1, 0.96.0, 0.98.0, 0.94.7
Attachments: hbase-7401.patch
I was switching version to 0.94 (from 0.95-SNAPSHOT) and got this message
which refers to a program that does not exist.
{code}
org.apache.hadoop.hbase.util.FileSystemVersionException: File system needs to
be upgraded. You have version null and I want version 7. Run the
'${HBASE_HOME}/bin/hbase migrate' script.
at org.apache.hadoop.hbase.util.FSUtils.checkVersion(FSUtils.java:324)
at
org.apache.hadoop.hbase.master.MasterFileSystem.checkRootDir(MasterFileSystem.java:352)
at
org.apache.hadoop.hbase.master.MasterFileSystem.createInitialFileSystemLayout(MasterFileSystem.java:128)
at
org.apache.hadoop.hbase.master.MasterFileSystem.init(MasterFileSystem.java:113)
at
org.apache.hadoop.hbase.master.HMaster.finishInitialization(HMaster.java:505)
at org.apache.hadoop.hbase.master.HMaster.run(HMaster.java:362)
at
org.apache.hadoop.hbase.master.HMasterCommandLine$LocalHMaster.run(HMasterCommandLine.java:226)
at java.lang.Thread.run(Thread.java:662)
{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-8247) inconsistent date format in different logs makes it painful to manipulate them
[ https://issues.apache.org/jira/browse/HBASE-8247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13622136#comment-13622136 ] Hudson commented on HBASE-8247: --- Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #476 (See [https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/476/]) HBASE-8247 inconsistent date format in different logs makes it painful to manipulate them (Revision 1464184) Result = FAILURE sershe : Files : * /hbase/trunk/conf/log4j.properties * /hbase/trunk/hbase-server/src/test/resources/log4j.properties inconsistent date format in different logs makes it painful to manipulate them -- Key: HBASE-8247 URL: https://issues.apache.org/jira/browse/HBASE-8247 Project: HBase Issue Type: Bug Reporter: Sergey Shelukhin Assignee: Sergey Shelukhin Priority: Minor Attachments: HBASE-8247-v0.patch, HBASE-8247-v1.patch -- 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-8230) Possible NPE on regionserver abort if replication service has not been started
[
https://issues.apache.org/jira/browse/HBASE-8230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13622124#comment-13622124
]
Hudson commented on HBASE-8230:
---
Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #476 (See
[https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/476/])
HBASE-8230 Possible NPE on regionserver abort if replication service has
not been started (Revision 1464280)
Result = FAILURE
stack :
Files :
*
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/replication/regionserver/Replication.java
Possible NPE on regionserver abort if replication service has not been started
--
Key: HBASE-8230
URL: https://issues.apache.org/jira/browse/HBASE-8230
Project: HBase
Issue Type: Bug
Components: regionserver, Replication
Affects Versions: 0.94.6
Reporter: Jieshan Bean
Assignee: Jieshan Bean
Fix For: 0.95.1, 0.94.7
Attachments: HBASE-8230-94.patch, HBASE-8230-trunk.patch
RegionServer got Exception on calling setupWALAndReplication, so entered
abort flow. Since replicationSink had not been inialized yet, we got below
exception:
{noformat}
Exception in thread regionserver26003 java.lang.NullPointerException
at
org.apache.hadoop.hbase.replication.regionserver.Replication.join(Replication.java:129)
at
org.apache.hadoop.hbase.replication.regionserver.Replication.stopReplicationService(Replication.java:120)
at
org.apache.hadoop.hbase.regionserver.HRegionServer.join(HRegionServer.java:1803)
at
org.apache.hadoop.hbase.regionserver.HRegionServer.run(HRegionServer.java:834)
at java.lang.Thread.run(Thread.java:662)
{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-7568) [replication] Create an interface for replication queues
[ https://issues.apache.org/jira/browse/HBASE-7568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13622132#comment-13622132 ] Hudson commented on HBASE-7568: --- Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #476 (See [https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/476/]) HBASE-7568 [replication] Create an interface for replication queues (Revision 1464279) Result = FAILURE stack : Files : * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/replication/ReplicationQueues.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/replication/ReplicationQueuesClient.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/replication/ReplicationQueuesClientZKImpl.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/replication/ReplicationQueuesZKImpl.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/replication/ReplicationStateImpl.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/replication/ReplicationStateZKBase.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/replication/ReplicationZookeeper.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/replication/master/ReplicationLogCleaner.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/replication/regionserver/Replication.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/replication/regionserver/ReplicationSourceManager.java * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/client/replication/TestReplicationAdmin.java * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/replication/TestReplicationStateBasic.java * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/replication/TestReplicationStateZKImpl.java * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/replication/regionserver/TestReplicationSourceManager.java [replication] Create an interface for replication queues Key: HBASE-7568 URL: https://issues.apache.org/jira/browse/HBASE-7568 Project: HBase Issue Type: Improvement Components: Replication Reporter: Chris Trezzo Assignee: Chris Trezzo Fix For: 0.95.1 Attachments: HBASE-7568-95-v1.patch, HBASE-7568-trunk-v1.patch, HBASE-7568-trunk-v2.patch, HBASE-7568-trunk-v3.patch, HBASE-7568-trunk-v4.patch -- 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-7415) [snapshots] Add task information to snapshot operation
[ https://issues.apache.org/jira/browse/HBASE-7415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13622181#comment-13622181 ] Hudson commented on HBASE-7415: --- Integrated in hbase-0.95-on-hadoop2 #54 (See [https://builds.apache.org/job/hbase-0.95-on-hadoop2/54/]) HBASE-7415 Add task information to snapshot operation (Jesse Yates) (Revision 1464429) Result = FAILURE mbertozzi : Files : * /hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/master/handler/TableEventHandler.java * /hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/master/snapshot/CloneSnapshotHandler.java * /hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/master/snapshot/DisabledTableSnapshotHandler.java * /hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/master/snapshot/RestoreSnapshotHandler.java * /hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/master/snapshot/TakeSnapshotHandler.java * /hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/snapshot/RestoreSnapshotHelper.java * /hbase/branches/0.95/hbase-server/src/test/java/org/apache/hadoop/hbase/snapshot/TestRestoreSnapshotHelper.java [snapshots] Add task information to snapshot operation -- Key: HBASE-7415 URL: https://issues.apache.org/jira/browse/HBASE-7415 Project: HBase Issue Type: New Feature Components: Client, master, regionserver, snapshots, Zookeeper Reporter: Jesse Yates Assignee: Jesse Yates Fix For: 0.95.1 Attachments: HBASE-7415-0.94.patch, HBASE-7415-0.94-v1.patch, hbase-7415-v0.patch, hbase-7415-v1.patch, HBASE-7415-v1-rebase.patch, HBASE-7415-v2.patch, HBASE-7415-v3.patch, HBASE-7415-v4.patch, HBASE-7415-v4.patch, HBase_Snapshot_Task_UI.png Snapshot operations should have some sort of progresss information available via the WebUI so admins can track progress of operations. This should go a long way to enable 'good' admins to not hose their clusters by running concurrent snapshot operations (e.g. rename while a clone is in progress). -- 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-8229) Replication code logs like crazy if a target table cannot be found.
[ https://issues.apache.org/jira/browse/HBASE-8229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13622180#comment-13622180 ] Hudson commented on HBASE-8229: --- Integrated in hbase-0.95-on-hadoop2 #54 (See [https://builds.apache.org/job/hbase-0.95-on-hadoop2/54/]) HBASE-8229 Replication code logs like crazy if a target table cannot be found. (Revision 1464273) Result = FAILURE larsh : Files : * /hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/replication/regionserver/ReplicationSource.java Replication code logs like crazy if a target table cannot be found. --- Key: HBASE-8229 URL: https://issues.apache.org/jira/browse/HBASE-8229 Project: HBase Issue Type: Bug Components: Replication Reporter: Lars Hofhansl Fix For: 0.95.1, 0.98.0, 0.94.7 Attachments: 8229-0.94.txt One of our RS/DN machines ran out of diskspace on the partition to which we write the log files. It turns out we still had a table in our source cluster with REPLICATION_SCOPE=1 that did not have a matching table in the remote cluster. In then logged a long stack trace every 50ms or so, over a few days that filled up our log partition. Since ReplicationSource cannot make any progress in this case anyway, it should probably sleep a bit before retrying (or at least limit the rate at which it spews out these exceptions to the log). -- 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-7568) [replication] Create an interface for replication queues
[ https://issues.apache.org/jira/browse/HBASE-7568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13622178#comment-13622178 ] Hudson commented on HBASE-7568: --- Integrated in hbase-0.95-on-hadoop2 #54 (See [https://builds.apache.org/job/hbase-0.95-on-hadoop2/54/]) HBASE-7568 [replication] Create an interface for replication queues (Revision 1464276) Result = FAILURE stack : Files : * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/replication/ReplicationQueues.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/replication/ReplicationQueuesClient.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/replication/ReplicationQueuesClientZKImpl.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/replication/ReplicationQueuesZKImpl.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/replication/ReplicationStateImpl.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/replication/ReplicationStateZKBase.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/replication/ReplicationZookeeper.java * /hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/replication/master/ReplicationLogCleaner.java * /hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/replication/regionserver/Replication.java * /hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/replication/regionserver/ReplicationSourceManager.java * /hbase/branches/0.95/hbase-server/src/test/java/org/apache/hadoop/hbase/client/replication/TestReplicationAdmin.java * /hbase/branches/0.95/hbase-server/src/test/java/org/apache/hadoop/hbase/replication/TestReplicationStateBasic.java * /hbase/branches/0.95/hbase-server/src/test/java/org/apache/hadoop/hbase/replication/TestReplicationStateZKImpl.java * /hbase/branches/0.95/hbase-server/src/test/java/org/apache/hadoop/hbase/replication/regionserver/TestReplicationSourceManager.java [replication] Create an interface for replication queues Key: HBASE-7568 URL: https://issues.apache.org/jira/browse/HBASE-7568 Project: HBase Issue Type: Improvement Components: Replication Reporter: Chris Trezzo Assignee: Chris Trezzo Fix For: 0.95.1 Attachments: HBASE-7568-95-v1.patch, HBASE-7568-trunk-v1.patch, HBASE-7568-trunk-v2.patch, HBASE-7568-trunk-v3.patch, HBASE-7568-trunk-v4.patch -- 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-8231) delete tests in table_tests.rb(TestShell) always running on empty table.
[
https://issues.apache.org/jira/browse/HBASE-8231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13622175#comment-13622175
]
Hudson commented on HBASE-8231:
---
Integrated in hbase-0.95-on-hadoop2 #54 (See
[https://builds.apache.org/job/hbase-0.95-on-hadoop2/54/])
HBASE-8231 delete tests in table_tests.rb(TestShell) always running on
empty table (Revision 1464284)
Result = FAILURE
stack :
Files :
* /hbase/branches/0.95/hbase-server/src/test/ruby/hbase/table_test.rb
delete tests in table_tests.rb(TestShell) always running on empty table.
Key: HBASE-8231
URL: https://issues.apache.org/jira/browse/HBASE-8231
Project: HBase
Issue Type: Bug
Components: scripts
Affects Versions: 0.95.0, 0.94.6
Reporter: rajeshbabu
Assignee: rajeshbabu
Fix For: 0.95.1, 0.94.7
Attachments: HBASE-8231.patch
In ruby,tests within the same test class are invoked in alphabetical order,so
delete test cases are running on a table before adding any entry.
TestShell logs showing Row not found for each delete test everytime.
{code}
ERROR: Row Not Found
Here is some help for this command:
Delete all cells in a given row; pass a table name, row, and optionally
a column and timestamp. Examples:
hbase deleteall 't1', 'r1'
hbase deleteall 't1', 'r1', 'c1'
hbase deleteall 't1', 'r1', 'c1', ts1
The same commands also can be run on a table reference. Suppose you had a
reference
t to table 't1', the corresponding command would be:
hbase t.deleteall 'r1'
hbase t.deleteall 'r1', 'c1'
hbase t.deleteall 'r1', 'c1', ts1
{code}
Before deleting a row we are checking whether the row is present or not.
{code}
def _deleteall_internal(row, column = nil, timestamp =
org.apache.hadoop.hbase.HConstants::LATEST_TIMESTAMP)
raise ArgumentError, Row Not Found if _get_internal(row).nil?
{code}
Need to improve delete tests in table_tests.rb.
--
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-5525) Truncate and preserve region boundaries option
[ https://issues.apache.org/jira/browse/HBASE-5525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13622176#comment-13622176 ] Hudson commented on HBASE-5525: --- Integrated in hbase-0.95-on-hadoop2 #54 (See [https://builds.apache.org/job/hbase-0.95-on-hadoop2/54/]) HBASE-5525 Truncate and preserve region boundaries option, addendum (Revision 1464426) HBASE-5525 Truncate and preserve region boundaries option (Revision 1464291) Result = FAILURE mbertozzi : Files : * /hbase/branches/0.95/hbase-server/src/main/ruby/shell/commands/truncate_preserve.rb stack : Files : * /hbase/branches/0.95/hbase-server/src/main/ruby/hbase/admin.rb * /hbase/branches/0.95/hbase-server/src/main/ruby/shell.rb Truncate and preserve region boundaries option -- Key: HBASE-5525 URL: https://issues.apache.org/jira/browse/HBASE-5525 Project: HBase Issue Type: New Feature Affects Versions: 0.96.0 Reporter: Jean-Daniel Cryans Assignee: Kevin Odell Labels: newbie, noob Fix For: 0.95.1 Attachments: HBASE-5525.patch, HBASE-5525-v1-0.94.patch, HBASE-5525-v1-0.95.patch, HBASE-5525-v1-trunk.patch, HBASE-5525-v1-trunk.patch A tool that would be useful for testing (and maybe in prod too) would be a truncate option to keep the current region boundaries. Right now what you have to do is completely kill the table and recreate it with the correct regions. -- 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-7686) TestSplitTransactionOnCluster fails occasionally in trunk builds
[
https://issues.apache.org/jira/browse/HBASE-7686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13622198#comment-13622198
]
Ted Yu commented on HBASE-7686:
---
Latest failure was in 0.95 build #123:
{code}
testShouldFailSplitIfZNodeDoesNotExistDueToPrevRollBack(org.apache.hadoop.hbase.regionserver.TestSplitTransactionOnCluster):
test timed out after 2 milliseconds
testMasterRestartWhenSplittingIsPartial(org.apache.hadoop.hbase.regionserver.TestSplitTransactionOnCluster):
test timed out after 30 milliseconds
testExistingZnodeBlocksSplitAndWeRollback(org.apache.hadoop.hbase.regionserver.TestSplitTransactionOnCluster):
test timed out after 30 milliseconds
{code}
TestSplitTransactionOnCluster fails occasionally in trunk builds
Key: HBASE-7686
URL: https://issues.apache.org/jira/browse/HBASE-7686
Project: HBase
Issue Type: Bug
Reporter: Ted Yu
Priority: Critical
Fix For: 0.95.1
Attachments: HBASE-7686-v0.patch, HBASE-7686-v1.patch
From trunk build #3808:
{code}
testShouldFailSplitIfZNodeDoesNotExistDueToPrevRollBack(org.apache.hadoop.hbase.regionserver.TestSplitTransactionOnCluster):
test timed out after 2 milliseconds
testMasterRestartWhenSplittingIsPartial(org.apache.hadoop.hbase.regionserver.TestSplitTransactionOnCluster):
test timed out after 30 milliseconds
testExistingZnodeBlocksSplitAndWeRollback(org.apache.hadoop.hbase.regionserver.TestSplitTransactionOnCluster):
test timed out after 30 milliseconds
{code}
From HBase-TRUNK-on-Hadoop-2.0.0 #378 :
{code}
testShutdownSimpleFixup(org.apache.hadoop.hbase.regionserver.TestSplitTransactionOnCluster):
Region not moved off .META. server
testShouldFailSplitIfZNodeDoesNotExistDueToPrevRollBack(org.apache.hadoop.hbase.regionserver.TestSplitTransactionOnCluster):
test timed out after 2 milliseconds
{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-8188) Avoid unnecessary row compare in StoreScanner
[ https://issues.apache.org/jira/browse/HBASE-8188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13622179#comment-13622179 ] Hudson commented on HBASE-8188: --- Integrated in hbase-0.95-on-hadoop2 #54 (See [https://builds.apache.org/job/hbase-0.95-on-hadoop2/54/]) HBASE-8188 Avoid unnecessary row compare in StoreScanner (Revision 1464288) Result = FAILURE larsh : Files : * /hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/StoreScanner.java Avoid unnecessary row compare in StoreScanner - Key: HBASE-8188 URL: https://issues.apache.org/jira/browse/HBASE-8188 Project: HBase Issue Type: Bug Reporter: Lars Hofhansl Assignee: Lars Hofhansl Fix For: 0.95.1, 0.98.0, 0.94.7 Attachments: 8188-0.94-experimental.txt, 8188-0.94.txt, 8188-0.96.txt, 8188-0.96.txt, 8188-0.96.txt, 8188-0.96.txt When scanner batching disable (which is the default) a row compare in StoreScanner avoided, because only entire rows of data are requested. This provides a slight performance gain, especially for tall tables (and when all data is in the cache) -- 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-7615) Add metrics for snapshots
[ https://issues.apache.org/jira/browse/HBASE-7615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13622174#comment-13622174 ] Hudson commented on HBASE-7615: --- Integrated in hbase-0.95-on-hadoop2 #54 (See [https://builds.apache.org/job/hbase-0.95-on-hadoop2/54/]) HBASE-7615 Add metrics for snapshots (Revision 1464443) Result = FAILURE mbertozzi : Files : * /hbase/branches/0.95/hbase-hadoop-compat/src/main/java/org/apache/hadoop/hbase/master/MetricsMasterSource.java * /hbase/branches/0.95/hbase-hadoop1-compat/src/main/java/org/apache/hadoop/hbase/master/MetricsMasterSourceImpl.java * /hbase/branches/0.95/hbase-hadoop2-compat/src/main/java/org/apache/hadoop/hbase/master/MetricsMasterSourceImpl.java * /hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/master/HMaster.java * /hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/master/MetricsMaster.java * /hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/master/snapshot/CloneSnapshotHandler.java * /hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/master/snapshot/DisabledTableSnapshotHandler.java * /hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/master/snapshot/EnabledTableSnapshotHandler.java * /hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/master/snapshot/RestoreSnapshotHandler.java * /hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/master/snapshot/SnapshotManager.java * /hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/master/snapshot/TakeSnapshotHandler.java * /hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/snapshot/SnapshotInfo.java * /hbase/branches/0.95/hbase-server/src/main/resources/hbase-webapps/master/snapshot.jsp * /hbase/branches/0.95/hbase-server/src/test/java/org/apache/hadoop/hbase/master/snapshot/TestSnapshotManager.java Add metrics for snapshots - Key: HBASE-7615 URL: https://issues.apache.org/jira/browse/HBASE-7615 Project: HBase Issue Type: Sub-task Reporter: Ted Yu Assignee: Matteo Bertozzi Attachments: HBASE-7615-0.94.patch, HBASE-7615-0.94-v1.patch, HBASE-7615.patch, HBASE-7615.patch, HBASE-7615.patch, HBASE-7615-v0.patch, HBASE-7615-v0-ui-corrupted.png, HBASE-7615-v0-ui.png, HBASE-7615-v1.patch, HBASE-7615-v2.patch, HBASE-7615-v3.patch, HBASE-7615-v4.patch Metrics should be added for snapshot. From Matteo: Output that we have in SnapshotInfo should be covered: %d HFiles (%d in archive), total size %s (%.2f%% %s shared with the source table) Jesse mentioned snaphot counts, average time to completion. I think we should have counts for successful / failed snapshots. -- 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-8230) Possible NPE on regionserver abort if replication service has not been started
[
https://issues.apache.org/jira/browse/HBASE-8230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13622177#comment-13622177
]
Hudson commented on HBASE-8230:
---
Integrated in hbase-0.95-on-hadoop2 #54 (See
[https://builds.apache.org/job/hbase-0.95-on-hadoop2/54/])
HBASE-8230 Possible NPE on regionserver abort if replication service has
not been started (Revision 1464281)
Result = FAILURE
stack :
Files :
*
/hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/replication/regionserver/Replication.java
Possible NPE on regionserver abort if replication service has not been started
--
Key: HBASE-8230
URL: https://issues.apache.org/jira/browse/HBASE-8230
Project: HBase
Issue Type: Bug
Components: regionserver, Replication
Affects Versions: 0.94.6
Reporter: Jieshan Bean
Assignee: Jieshan Bean
Fix For: 0.95.1, 0.94.7
Attachments: HBASE-8230-94.patch, HBASE-8230-trunk.patch
RegionServer got Exception on calling setupWALAndReplication, so entered
abort flow. Since replicationSink had not been inialized yet, we got below
exception:
{noformat}
Exception in thread regionserver26003 java.lang.NullPointerException
at
org.apache.hadoop.hbase.replication.regionserver.Replication.join(Replication.java:129)
at
org.apache.hadoop.hbase.replication.regionserver.Replication.stopReplicationService(Replication.java:120)
at
org.apache.hadoop.hbase.regionserver.HRegionServer.join(HRegionServer.java:1803)
at
org.apache.hadoop.hbase.regionserver.HRegionServer.run(HRegionServer.java:834)
at java.lang.Thread.run(Thread.java:662)
{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-8240) CompoundConfiguration should implement Iterable
[
https://issues.apache.org/jira/browse/HBASE-8240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13622211#comment-13622211
]
Ted Yu commented on HBASE-8240:
---
bq. I suppose it is ok because base Configuration does this.
That's right. Query to ImmutableConfigMap always uses String parameter:
{code}
public String get(String key) {
{code}
bq. Do we have to save up all of the Configuation into a HashMap
This is done so that the returned iterator doesn't give user duplicate keys.
See my comment above:
bq. I tried CompositeIterator approach but its semantics is not correct:
iterator would return multiple values for the same key.
bq. Where do we need this functionatlity?
This is needed in FileSystem.get(Configuration) call. hadoop 2.0 expects a
mutable Configuration. We would get the following if CompoundConfiguration is
passed:
{code}
java.lang.UnsupportedOperationException: Immutable Configuration
at
org.apache.hadoop.hbase.CompoundConfiguration.setClass(CompoundConfiguration.java:474)
at org.apache.hadoop.ipc.RPC.setProtocolEngine(RPC.java:193)
at
org.apache.hadoop.hdfs.NameNodeProxies.createNNProxyWithClientProtocol(NameNodeProxies.java:249)
at
org.apache.hadoop.hdfs.NameNodeProxies.createNonHAProxy(NameNodeProxies.java:168)
at
org.apache.hadoop.hdfs.NameNodeProxies.createProxy(NameNodeProxies.java:129)
at org.apache.hadoop.hdfs.DFSClient.init(DFSClient.java:421)
at org.apache.hadoop.hdfs.DFSClient.init(DFSClient.java:388)
at
org.apache.hadoop.hdfs.DistributedFileSystem.initialize(DistributedFileSystem.java:125)
at org.apache.hadoop.fs.FileSystem.createFileSystem(FileSystem.java:2277)
at org.apache.hadoop.fs.FileSystem.access$200(FileSystem.java:86)
at org.apache.hadoop.fs.FileSystem$Cache.getInternal(FileSystem.java:2311)
at org.apache.hadoop.fs.FileSystem$Cache.get(FileSystem.java:2293)
at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:317)
at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:163)
{code}
So this JIRA should go into 0.95 as well.
CompoundConfiguration should implement Iterable
---
Key: HBASE-8240
URL: https://issues.apache.org/jira/browse/HBASE-8240
Project: HBase
Issue Type: Improvement
Reporter: Ted Yu
Assignee: Ted Yu
Fix For: 0.98.0
Attachments: 8240-v1.txt, 8240-v2.txt, 8240-v3.txt, 8240-v4.txt,
8240-v6.txt
Here is from hadoop Configuration class:
{code}
public class Configuration implements IterableMap.EntryString,String,
{code}
There're 3 addXX() methods for CompoundConfiguration:
{code}
public CompoundConfiguration add(final Configuration conf) {
public CompoundConfiguration addWritableMap(
final MapImmutableBytesWritable, ImmutableBytesWritable map) {
public CompoundConfiguration addStringMap(final MapString, String map) {
{code}
Parameters to these methods all support iteration.
We can enhance ImmutableConfigMap with the following new method:
{code}
public abstract java.util.Iterator iterator();
{code}
Then the following method of CompoundConfiguration can be implemented:
{code}
public IteratorMap.EntryString, String iterator() {
{code}
This enhancement would be useful in scenario where a mutable Configuration is
required.
--
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-8071) TestRestoreFlushSnapshotFromClient fails intermittently in trunk builds
[
https://issues.apache.org/jira/browse/HBASE-8071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13622218#comment-13622218
]
Ted Yu commented on HBASE-8071:
---
This test failed in HBase-TRUNK #4010:
testTakeFlushSnapshot(org.apache.hadoop.hbase.snapshot.TestRestoreFlushSnapshotFromClient):
org.apache.hadoop.hbase.exceptions.SnapshotDoesNotExistException: Snapshot
'snaptb0-1365052897105' doesn't exist on the filesystem
TestRestoreFlushSnapshotFromClient fails intermittently in trunk builds
---
Key: HBASE-8071
URL: https://issues.apache.org/jira/browse/HBASE-8071
Project: HBase
Issue Type: Test
Reporter: Ted Yu
Assignee: Ted Yu
Fix For: 0.95.1
Attachments: 8071.txt
From
https://builds.apache.org/job/HBase-TRUNK/3945/testReport/org.apache.hadoop.hbase.snapshot/TestRestoreFlushSnapshotFromClient/testRestoreSnapshot/:
{code}
2013-03-11 19:35:54,162 DEBUG [IPC Server handler 1 on 51923]
master.HMaster(2410): Submitting snapshot request for:{
ss=snaptb1-1363030509407 table=testtb-1363030509407 type=FLUSH }
2013-03-11 19:35:54,162 DEBUG [IPC Server handler 1 on 51923]
snapshot.SnapshotDescriptionUtils(235): Creation time not specified, setting
to:1363030554162 (current time:1363030554162).
2013-03-11 19:35:54,163 DEBUG [IPC Server handler 1 on 51923]
snapshot.SnapshotManager(465): No existing snapshot, attempting snapshot...
...
2013-03-11 19:36:52,139 DEBUG [pool-1-thread-1] client.HBaseAdmin(2234):
Getting current status of snapshot from master...
2013-03-11 19:36:52,140 DEBUG [IPC Server handler 1 on 51923]
master.HMaster(2481): Checking to see if snapshot from request:{
ss=snaptb1-1363030509407 table=testtb-1363030509407 type=FLUSH } is done
2013-03-11 19:36:52,140 DEBUG [IPC Server handler 1 on 51923]
snapshot.SnapshotManager(344): Snapshoting '{ ss=snaptb1-1363030509407
table=testtb-1363030509407 type=FLUSH }' is still in progress!
2013-03-11 19:36:52,140 DEBUG [pool-1-thread-1] client.HBaseAdmin(2226):
(#16) Sleeping: 8000ms while waiting for snapshot completion.
2013-03-11 19:36:55,740 DEBUG [Timer-28]
errorhandling.ForeignExceptionDispatcher(68): accepting received exception
org.apache.hadoop.hbase.errorhandling.TimeoutException via
timer-java.util.Timer@1ed8384b:org.apache.hadoop.hbase.errorhandling.TimeoutException:
Timeout elapsed! Source:Timeout caused Foreign Exception
Start:1363030555739, End:1363030615740, diff:60001, max:6 ms
at
org.apache.hadoop.hbase.errorhandling.TimeoutExceptionInjector$1.run(TimeoutExceptionInjector.java:71)
at java.util.TimerThread.mainLoop(Timer.java:555)
at java.util.TimerThread.run(Timer.java:505)
Caused by: org.apache.hadoop.hbase.errorhandling.TimeoutException: Timeout
elapsed! Source:Timeout caused Foreign Exception Start:1363030555739,
End:1363030615740, diff:60001, max:6 ms
at
org.apache.hadoop.hbase.errorhandling.TimeoutExceptionInjector$1.run(TimeoutExceptionInjector.java:68)
... 2 more
2013-03-11 19:36:55,759 DEBUG
[MASTER_TABLE_OPERATIONS-janus.apache.org,51923,1363030251194-0]
client.HConnectionManager$HConnectionImplementation(944): Looking up meta
region location in ZK, connection=hconnection 0x25c6f10
2013-03-11 19:36:55,760 DEBUG
[MASTER_TABLE_OPERATIONS-janus.apache.org,51923,1363030251194-0]
zookeeper.ZKUtil(1682): hconnection 0x25c6f10-0x13d5aef12b70004 Retrieved 35
byte(s) of data from znode /hbase/meta-region-server;
data=janus.apache.org,42570,1363030252791
2013-03-11 19:36:55,760 DEBUG
[MASTER_TABLE_OPERATIONS-janus.apache.org,51923,1363030251194-0]
client.HConnectionManager$HConnectionImplementation(949): Looked up meta
region location, connection=hconnection 0x25c6f10;
serverName=janus.apache.org,42570,1363030252791
2013-03-11 19:36:55,760 DEBUG
[MASTER_TABLE_OPERATIONS-janus.apache.org,51923,1363030251194-0]
client.ClientScanner(96): Creating scanner over .META. starting at key
'testtb-1363030509407,,'
2013-03-11 19:36:55,760 DEBUG
[MASTER_TABLE_OPERATIONS-janus.apache.org,51923,1363030251194-0]
client.ClientScanner(209): Advancing internal scanner to startKey at
'testtb-1363030509407,,'
2013-03-11 19:36:55,760 DEBUG
[MASTER_TABLE_OPERATIONS-janus.apache.org,51923,1363030251194-0]
client.HConnectionManager$HConnectionImplementation(944): Looking up meta
region location in ZK, connection=hconnection 0x25c6f10
2013-03-11 19:36:55,761 DEBUG
[MASTER_TABLE_OPERATIONS-janus.apache.org,51923,1363030251194-0]
zookeeper.ZKUtil(1682): hconnection 0x25c6f10-0x13d5aef12b70004 Retrieved 35
byte(s) of data from znode /hbase/meta-region-server;
data=janus.apache.org,42570,1363030252791
2013-03-11 19:36:55,761 DEBUG
[jira] [Commented] (HBASE-7871) HBase can be stuck when closing regions concurrently
[
https://issues.apache.org/jira/browse/HBASE-7871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13622125#comment-13622125
]
Hudson commented on HBASE-7871:
---
Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #476 (See
[https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/476/])
HBASE-7871 HBase can be stuck when closing regions concurrently (Ted Yu)
(Revision 1464012)
Result = FAILURE
tedyu :
Files :
*
/hbase/trunk/hbase-hadoop1-compat/src/main/java/org/apache/hadoop/hbase/regionserver/MetricsRegionAggregateSourceImpl.java
*
/hbase/trunk/hbase-hadoop2-compat/src/main/java/org/apache/hadoop/hbase/regionserver/MetricsRegionAggregateSourceImpl.java
HBase can be stuck when closing regions concurrently
-
Key: HBASE-7871
URL: https://issues.apache.org/jira/browse/HBASE-7871
Project: HBase
Issue Type: Bug
Components: master
Affects Versions: 0.96.0
Reporter: Nicolas Liochon
Assignee: Ted Yu
Priority: Critical
Fix For: 0.95.1, 0.98.0
Attachments: 7871.patch, 7871-v2.patch, 7871-v3.txt, 7871-v4.txt,
s1.txt, TestStartStop.java
The attached test fails ~1% of the the time on 0.96. It seems it does not
fail on 0.94.5. It's simple: a table creation and some puts.
I attach the stack. Logs says nothing it seems.
The suspicious part is:
{noformat}
RS_CLOSE_REGION-localhost,57575,1361197489166-2 prio=10
tid=0x7fb0c8775800 nid=0x61ac runnable [0x7fb09f272000]
java.lang.Thread.State: RUNNABLE
at java.util.TreeMap.fixAfterDeletion(TreeMap.java:2193)
at java.util.TreeMap.deleteEntry(TreeMap.java:2151)
at java.util.TreeMap.remove(TreeMap.java:585)
at java.util.TreeSet.remove(TreeSet.java:259)
at
org.apache.hadoop.hbase.regionserver.MetricsRegionAggregateSourceImpl.deregister(MetricsRegionAggregateSourceImpl.java:55)
at
org.apache.hadoop.hbase.regionserver.MetricsRegionSourceImpl.close(MetricsRegionSourceImpl.java:86)
at
org.apache.hadoop.hbase.regionserver.MetricsRegion.close(MetricsRegion.java:40)
at
org.apache.hadoop.hbase.regionserver.HRegion.doClose(HRegion.java:1063)
at
org.apache.hadoop.hbase.regionserver.HRegion.close(HRegion.java:969)
- locked 0x0006944e2558 (a java.lang.Object)
at
org.apache.hadoop.hbase.regionserver.handler.CloseRegionHandler.process(CloseRegionHandler.java:146)
at
org.apache.hadoop.hbase.executor.EventHandler.run(EventHandler.java:203)
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:662)
{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-8229) Replication code logs like crazy if a target table cannot be found.
[ https://issues.apache.org/jira/browse/HBASE-8229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13622128#comment-13622128 ] Hudson commented on HBASE-8229: --- Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #476 (See [https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/476/]) HBASE-8229 Replication code logs like crazy if a target table cannot be found. (Revision 1464278) Result = FAILURE larsh : Files : * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/replication/regionserver/ReplicationSource.java Replication code logs like crazy if a target table cannot be found. --- Key: HBASE-8229 URL: https://issues.apache.org/jira/browse/HBASE-8229 Project: HBase Issue Type: Bug Components: Replication Reporter: Lars Hofhansl Fix For: 0.95.1, 0.98.0, 0.94.7 Attachments: 8229-0.94.txt One of our RS/DN machines ran out of diskspace on the partition to which we write the log files. It turns out we still had a table in our source cluster with REPLICATION_SCOPE=1 that did not have a matching table in the remote cluster. In then logged a long stack trace every 50ms or so, over a few days that filled up our log partition. Since ReplicationSource cannot make any progress in this case anyway, it should probably sleep a bit before retrying (or at least limit the rate at which it spews out these exceptions to the log). -- 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-8164) TestTableLockManager fails intermittently in trunk builds
[ https://issues.apache.org/jira/browse/HBASE-8164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13622365#comment-13622365 ] Ted Yu commented on HBASE-8164: --- In trunk build #4011: testTableReadLock(org.apache.hadoop.hbase.master.TestTableLockManager): test timed out after 60 milliseconds TestTableLockManager fails intermittently in trunk builds - Key: HBASE-8164 URL: https://issues.apache.org/jira/browse/HBASE-8164 Project: HBase Issue Type: Bug Reporter: Ted Yu Assignee: Ted Yu Fix For: 0.95.0, 0.98.0 Attachments: 8164-addendum-2.txt, 8164-addendum.txt, 8164-v2.txt, 8164-v3.txt, 8164-v4.txt, HBASE-8164_addendum_3.patch, HBASE-8164_addendum_4.patch, HBASE-8164_addendum_5.patch In build #3979: testTableReadLock(org.apache.hadoop.hbase.master.TestTableLockManager): test timed out after 60 milliseconds -- 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] [Comment Edited] (HBASE-8258) Make mapreduce tests pass on hadoop2
[
https://issues.apache.org/jira/browse/HBASE-8258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13622371#comment-13622371
]
Jonathan Hsieh edited comment on HBASE-8258 at 4/4/13 2:30 PM:
---
The old theory I mentioned above is not relevant. Here's the new idea I'm
working on.
* We are getting an UndeclaredThrowableException when waiting for the MR job to
complete, because
* we get a ConnectException from the mr client trying to talk to 0.0.0.0:8032
(the resource manager port), because
* ... there is a gap here between the local runs and the jenkins runs ...
* the Yarn MRAppMaster for the job is getting killed the Yarn nodemanager[1],
(separate processes) because
* virtual memory is being over provisioned in the MRAppMaster
[1]
{code}
2013-04-04 04:46:18,895 WARN [AsyncDispatcher event handler]
resourcemanager.RMAuditLogger(255): USER=jenkins OPERATION=Application
Finished - Failed TARGET=RMAppManager RESULT=FAILURE DESCRIPTION=App
failed with state: FAILED PERMISSIONS=Application
application_1365075961471_0001 failed 1 times due to AM Container for
appattempt_1365075961471_0001_01 exited with exitCode: 143 due to:
Container [pid=31600,containerID=container_1365075961471_0001_01_01] is
running beyond virtual memory limits. Current usage: 259.7mb of 2.0gb physical
memory used; 5.6gb of 4.2gb virtual memory used. Killing container.
{code}
was (Author: jmhsieh):
The old theory I mentioned above is not relevant. Here's the new idea I'm
working on.
* We are getting an UndeclaredThrowableException when waiting for the MR job to
complete, because
* we get a ConnectException from the mr client trying to talk to 0.0.0.0:8032
(the resource manager port), because
* ... there is a gap here between the local runs and the jenkins runs ...
* the Yarn MRAppMaster for the is getting killed the Yarn nodemanager[1],
(separate processes) because
* virtual memory is being over provisioned in the MRAppMaster
[1]
{code}
2013-04-04 04:46:18,895 WARN [AsyncDispatcher event handler]
resourcemanager.RMAuditLogger(255): USER=jenkins OPERATION=Application
Finished - Failed TARGET=RMAppManager RESULT=FAILURE DESCRIPTION=App
failed with state: FAILED PERMISSIONS=Application
application_1365075961471_0001 failed 1 times due to AM Container for
appattempt_1365075961471_0001_01 exited with exitCode: 143 due to:
Container [pid=31600,containerID=container_1365075961471_0001_01_01] is
running beyond virtual memory limits. Current usage: 259.7mb of 2.0gb physical
memory used; 5.6gb of 4.2gb virtual memory used. Killing container.
{code}
Make mapreduce tests pass on hadoop2
Key: HBASE-8258
URL: https://issues.apache.org/jira/browse/HBASE-8258
Project: HBase
Issue Type: Bug
Components: mapreduce
Reporter: stack
Priority: Blocker
Fix For: 0.95.1
Attachments: 8258-plain.txt
HBASE-7904 was a first attempt at making this work but it got lost in the
weeds.
This is a new attempt at making hbase mapreduce jobs run on hadoop2 (w/o
breaking mapreduce on hadoop1)
--
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-8258) Make mapreduce tests pass on hadoop2
[
https://issues.apache.org/jira/browse/HBASE-8258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13622371#comment-13622371
]
Jonathan Hsieh commented on HBASE-8258:
---
The old theory I mentioned above is not relevant. Here's the new idea I'm
working on.
* We are getting an UndeclaredThrowableException when waiting for the MR job to
complete, because
* we get a ConnectException from the mr client trying to talk to 0.0.0.0:8032
(the resource manager port), because
* ... there is a gap here between the local runs and the jenkins runs ...
* the Yarn MRAppMaster for the is getting killed the Yarn nodemanager[1],
(separate processes) because
* virtual memory is being over provisioned in the MRAppMaster
[1]
{code}
2013-04-04 04:46:18,895 WARN [AsyncDispatcher event handler]
resourcemanager.RMAuditLogger(255): USER=jenkins OPERATION=Application
Finished - Failed TARGET=RMAppManager RESULT=FAILURE DESCRIPTION=App
failed with state: FAILED PERMISSIONS=Application
application_1365075961471_0001 failed 1 times due to AM Container for
appattempt_1365075961471_0001_01 exited with exitCode: 143 due to:
Container [pid=31600,containerID=container_1365075961471_0001_01_01] is
running beyond virtual memory limits. Current usage: 259.7mb of 2.0gb physical
memory used; 5.6gb of 4.2gb virtual memory used. Killing container.
{code}
Make mapreduce tests pass on hadoop2
Key: HBASE-8258
URL: https://issues.apache.org/jira/browse/HBASE-8258
Project: HBase
Issue Type: Bug
Components: mapreduce
Reporter: stack
Priority: Blocker
Fix For: 0.95.1
Attachments: 8258-plain.txt
HBASE-7904 was a first attempt at making this work but it got lost in the
weeds.
This is a new attempt at making hbase mapreduce jobs run on hadoop2 (w/o
breaking mapreduce on hadoop1)
--
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] [Comment Edited] (HBASE-8258) Make mapreduce tests pass on hadoop2
[
https://issues.apache.org/jira/browse/HBASE-8258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13622371#comment-13622371
]
Jonathan Hsieh edited comment on HBASE-8258 at 4/4/13 2:33 PM:
---
The old theory I mentioned above is not relevant. Here's the new idea I'm
working on.
* Certain mapreduce on hadoop2 minicluster jobs are failing, because
* we are getting an UndeclaredThrowableException when waiting for the MR job to
complete, because
* we get a ConnectException from the mr client trying to talk to 0.0.0.0:8032
(the resource manager port), because
* ... there is a gap here between the local runs and the jenkins runs ...
* the Yarn MRAppMaster for the job is getting killed the Yarn nodemanager[1],
(separate processes) because
* virtual memory is being over provisioned in the MRAppMaster
[1]
{code}
2013-04-04 04:46:18,895 WARN [AsyncDispatcher event handler]
resourcemanager.RMAuditLogger(255): USER=jenkins OPERATION=Application
Finished - Failed TARGET=RMAppManager RESULT=FAILURE DESCRIPTION=App
failed with state: FAILED PERMISSIONS=Application
application_1365075961471_0001 failed 1 times due to AM Container for
appattempt_1365075961471_0001_01 exited with exitCode: 143 due to:
Container [pid=31600,containerID=container_1365075961471_0001_01_01] is
running beyond virtual memory limits. Current usage: 259.7mb of 2.0gb physical
memory used; 5.6gb of 4.2gb virtual memory used. Killing container.
{code}
was (Author: jmhsieh):
The old theory I mentioned above is not relevant. Here's the new idea I'm
working on.
* We are getting an UndeclaredThrowableException when waiting for the MR job to
complete, because
* we get a ConnectException from the mr client trying to talk to 0.0.0.0:8032
(the resource manager port), because
* ... there is a gap here between the local runs and the jenkins runs ...
* the Yarn MRAppMaster for the job is getting killed the Yarn nodemanager[1],
(separate processes) because
* virtual memory is being over provisioned in the MRAppMaster
[1]
{code}
2013-04-04 04:46:18,895 WARN [AsyncDispatcher event handler]
resourcemanager.RMAuditLogger(255): USER=jenkins OPERATION=Application
Finished - Failed TARGET=RMAppManager RESULT=FAILURE DESCRIPTION=App
failed with state: FAILED PERMISSIONS=Application
application_1365075961471_0001 failed 1 times due to AM Container for
appattempt_1365075961471_0001_01 exited with exitCode: 143 due to:
Container [pid=31600,containerID=container_1365075961471_0001_01_01] is
running beyond virtual memory limits. Current usage: 259.7mb of 2.0gb physical
memory used; 5.6gb of 4.2gb virtual memory used. Killing container.
{code}
Make mapreduce tests pass on hadoop2
Key: HBASE-8258
URL: https://issues.apache.org/jira/browse/HBASE-8258
Project: HBase
Issue Type: Bug
Components: mapreduce
Reporter: stack
Priority: Blocker
Fix For: 0.95.1
Attachments: 8258-plain.txt
HBASE-7904 was a first attempt at making this work but it got lost in the
weeds.
This is a new attempt at making hbase mapreduce jobs run on hadoop2 (w/o
breaking mapreduce on hadoop1)
--
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] [Comment Edited] (HBASE-8258) Make mapreduce tests pass on hadoop2
[ https://issues.apache.org/jira/browse/HBASE-8258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13622388#comment-13622388 ] Jonathan Hsieh edited comment on HBASE-8258 at 4/4/13 2:53 PM: --- [~devaraj] I'm not getting the same error you are getting. Are you working ontop of the current hadoop2 in the pom 2.0.2-alpha or a different version? (I have build problems with ted's 8258-plain.txt patch applied). was (Author: jmhsieh): [~devaraj] I'm not getting the same error you are getting. Are you working ontop of the current hadoop2 in the pom 2.0.2-alpha or a different version? (I hvae build with ted's 8258-plain.txt patch applied). Make mapreduce tests pass on hadoop2 Key: HBASE-8258 URL: https://issues.apache.org/jira/browse/HBASE-8258 Project: HBase Issue Type: Bug Components: mapreduce Reporter: stack Priority: Blocker Fix For: 0.95.1 Attachments: 8258-plain.txt HBASE-7904 was a first attempt at making this work but it got lost in the weeds. This is a new attempt at making hbase mapreduce jobs run on hadoop2 (w/o breaking mapreduce on hadoop1) -- 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-8258) Make mapreduce tests pass on hadoop2
[ https://issues.apache.org/jira/browse/HBASE-8258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13622388#comment-13622388 ] Jonathan Hsieh commented on HBASE-8258: --- [~devaraj] I'm not getting the same error you are getting. Are you working ontop of the current hadoop2 in the pom 2.0.2-alpha or a different version? (I hvae build with ted's 8258-plain.txt patch applied). Make mapreduce tests pass on hadoop2 Key: HBASE-8258 URL: https://issues.apache.org/jira/browse/HBASE-8258 Project: HBase Issue Type: Bug Components: mapreduce Reporter: stack Priority: Blocker Fix For: 0.95.1 Attachments: 8258-plain.txt HBASE-7904 was a first attempt at making this work but it got lost in the weeds. This is a new attempt at making hbase mapreduce jobs run on hadoop2 (w/o breaking mapreduce on hadoop1) -- 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-7686) TestSplitTransactionOnCluster fails occasionally in trunk builds
[
https://issues.apache.org/jira/browse/HBASE-7686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13622399#comment-13622399
]
Matteo Bertozzi commented on HBASE-7686:
all the failures, in this last case, seems to be timeouts 30sec to create a
table.
TestSplitTransactionOnCluster fails occasionally in trunk builds
Key: HBASE-7686
URL: https://issues.apache.org/jira/browse/HBASE-7686
Project: HBase
Issue Type: Bug
Reporter: Ted Yu
Priority: Critical
Fix For: 0.95.1
Attachments: HBASE-7686-v0.patch, HBASE-7686-v1.patch
From trunk build #3808:
{code}
testShouldFailSplitIfZNodeDoesNotExistDueToPrevRollBack(org.apache.hadoop.hbase.regionserver.TestSplitTransactionOnCluster):
test timed out after 2 milliseconds
testMasterRestartWhenSplittingIsPartial(org.apache.hadoop.hbase.regionserver.TestSplitTransactionOnCluster):
test timed out after 30 milliseconds
testExistingZnodeBlocksSplitAndWeRollback(org.apache.hadoop.hbase.regionserver.TestSplitTransactionOnCluster):
test timed out after 30 milliseconds
{code}
From HBase-TRUNK-on-Hadoop-2.0.0 #378 :
{code}
testShutdownSimpleFixup(org.apache.hadoop.hbase.regionserver.TestSplitTransactionOnCluster):
Region not moved off .META. server
testShouldFailSplitIfZNodeDoesNotExistDueToPrevRollBack(org.apache.hadoop.hbase.regionserver.TestSplitTransactionOnCluster):
test timed out after 2 milliseconds
{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-8258) Make mapreduce tests pass on hadoop2
[ https://issues.apache.org/jira/browse/HBASE-8258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13622406#comment-13622406 ] stack commented on HBASE-8258: -- [~jmhsieh] You saw the discussion over in hbase-7904 about YARN doing process kill because of vmem excess? Ted added this addendum over in hbase-7904: https://issues.apache.org/jira/secure/attachment/12576220/7904-addendum.txt Make mapreduce tests pass on hadoop2 Key: HBASE-8258 URL: https://issues.apache.org/jira/browse/HBASE-8258 Project: HBase Issue Type: Bug Components: mapreduce Reporter: stack Priority: Blocker Fix For: 0.95.1 Attachments: 8258-plain.txt HBASE-7904 was a first attempt at making this work but it got lost in the weeds. This is a new attempt at making hbase mapreduce jobs run on hadoop2 (w/o breaking mapreduce on hadoop1) -- 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-8259) Snapshot backport in 0.94.6 breaks rolling restarts
[
https://issues.apache.org/jira/browse/HBASE-8259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13622408#comment-13622408
]
Hudson commented on HBASE-8259:
---
Integrated in HBase-0.94 #940 (See
[https://builds.apache.org/job/HBase-0.94/940/])
HBASE-8259 Snapshot backport in 0.94.6 breaks rolling restarts (Revision
1464562)
Result = FAILURE
mbertozzi :
Files :
*
/hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/executor/EventHandler.java
Snapshot backport in 0.94.6 breaks rolling restarts
---
Key: HBASE-8259
URL: https://issues.apache.org/jira/browse/HBASE-8259
Project: HBase
Issue Type: Bug
Affects Versions: 0.94.6
Reporter: Jean-Daniel Cryans
Assignee: Matteo Bertozzi
Priority: Blocker
Fix For: 0.94.7
Attachments: HBASE-8259-v0.patch
[~aleksshulman] found with his nifty QA tools that 0.94.6 has an incompatible
change due to HBASE-7360 (Snapshot 0.94 Backport) that breaks rolling
restarts.
RegionTransitionData.write() uses eventType.ordinal() that is the index in
the enum and not the value specified in the enum definition. It means we
can't add new states in the middle of the list. This can be fixed by moving
C_M_SNAPSHOT_TABLE and C_M_RESTORE_SNAPSHOT at the end of the list. Trunk
does the right thing already.
Right now, RIT znodes created with 0.94.6 (or top of the branch) will use the
wrong value for the event type. You will see things like:
{noformat}
2013-04-03 14:57:25,197 DEBUG org.apache.hadoop.hbase.zookeeper.ZKAssign:
regionserver:60020-0x13dd1e10dbd0004 Attempting to transition node
70236052/-ROOT- from M_ZK_REGION_OFFLINE to RS_ZK_REGION_OPENING
2013-04-03 14:57:25,201 WARN org.apache.hadoop.hbase.zookeeper.ZKAssign:
regionserver:60020-0x13dd1e10dbd0004 Attempt to transition the unassigned
node for 70236052 from M_ZK_REGION_OFFLINE to RS_ZK_REGION_OPENING failed,
the node existed but was in the state M_SERVER_SHUTDOWN set by the server
192.168.1.112,60020,1365026237977
2013-04-03 14:57:25,201 WARN
org.apache.hadoop.hbase.regionserver.handler.OpenRegionHandler: Failed
transition from OFFLINE to OPENING for region=70236052
2013-04-03 14:57:25,201 WARN
org.apache.hadoop.hbase.regionserver.handler.OpenRegionHandler: Region was
hijacked? It no longer exists, encodedName=70236052
{noformat}
We should roll a 0.94.6.1 or 0.94.7 as soon this is fixed IMO.
--
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-7244) Provide a command or argument to startup, that formats znodes if provided
[
https://issues.apache.org/jira/browse/HBASE-7244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13622411#comment-13622411
]
rajeshbabu commented on HBASE-7244:
---
[~stack]
bq. Can you provide evidence this script actually works?
Started hbase cluster and stopped all hbase related processes then ran the
clean up script.
Here are the logs I can provide for evidence. One of my colleague using in
cluster testing when ever needed cleanup.
It checks any hbase processes master,regionservers and backup masters are alive
or not. If no process is alive only it will delete zk data and then hdfs data
on user acceptance.
{code}
All ZNode(s) of regionservers are expired.
All ZNode(s) of backupmasters are expired.
Node does not exist: /hbase/master
Active Master ZNode also expired.
Do you want to clean zookeeper data.[y/n]y
13/04/04 20:23:34 DEBUG zookeeper.ZKConfig: Skipped reading ZK properties file
'zoo.cfg' since 'hbase.config.read.zookeeper.config' was not set to true
Connecting to 10.18.91.14:2181
13/04/04 20:23:35 INFO zookeeper.ZooKeeper: Client
environment:zookeeper.version=3.4.5-1392090, built on 09/30/2012 17:52 GMT
13/04/04 20:23:35 INFO zookeeper.ZooKeeper: Client
environment:host.name=linux-129
13/04/04 20:23:35 INFO zookeeper.ZooKeeper: Client
environment:java.version=1.6.0_31
13/04/04 20:23:35 INFO zookeeper.ZooKeeper: Client environment:java.vendor=Sun
Microsystems Inc.
13/04/04 20:23:35 INFO zookeeper.ZooKeeper: Client
environment:java.home=/opt/jdk1.6.0_31/jre
13/04/04 20:23:35 INFO zookeeper.ZooKeeper: Client
environment:java.class.path=/home/rajeshbabu/hbase-0.97-SNAPSHOT/bin/../conf:
13/04/04 20:23:35 INFO zookeeper.ZooKeeper: Client
environment:java.library.path=/opt/jdk1.6.0_31/jre/lib/amd64/server:/opt/jdk1.6.0_31/jre/lib/amd64:/opt/jdk1.6.0_31/jre/../lib/amd64:/usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib
13/04/04 20:23:35 INFO zookeeper.ZooKeeper: Client
environment:java.io.tmpdir=/tmp
13/04/04 20:23:35 INFO zookeeper.ZooKeeper: Client
environment:java.compiler=NA
13/04/04 20:23:35 INFO zookeeper.ZooKeeper: Client environment:os.name=Linux
13/04/04 20:23:35 INFO zookeeper.ZooKeeper: Client environment:os.arch=amd64
13/04/04 20:23:35 INFO zookeeper.ZooKeeper: Client
environment:os.version=2.6.27.19-5-default
13/04/04 20:23:35 INFO zookeeper.ZooKeeper: Client environment:user.name=root
13/04/04 20:23:35 INFO zookeeper.ZooKeeper: Client environment:user.home=/root
13/04/04 20:23:35 INFO zookeeper.ZooKeeper: Client
environment:user.dir=/home/rajeshbabu/hbase-0.97-SNAPSHOT/dev-support
13/04/04 20:23:35 INFO zookeeper.ZooKeeper: Initiating client connection,
connectString=10.18.91.14:2181 sessionTimeout=3
watcher=org.apache.zookeeper.ZooKeeperMain$MyWatcher@670655dd
13/04/04 20:23:35 INFO zookeeper.ClientCnxn: Opening socket connection to
server linux-129/10.18.91.14:2181. Will not attempt to authenticate using SASL
(Unable to locate a login configuration)
13/04/04 20:23:35 INFO zookeeper.ClientCnxn: Socket connection established to
linux-129/10.18.91.14:2181, initiating session
13/04/04 20:23:35 INFO zookeeper.ClientCnxn: Session establishment complete on
server linux-129/10.18.91.14:2181, sessionid = 0x13d821d941f00d5, negotiated
timeout = 3
WATCHER::
WatchedEvent state:SyncConnected type:None path:null
Do you want to clean hdfs data.[y/n]y
Deleted hdfs://10.18.91.14:9000/hbase
{code}
Provide a command or argument to startup, that formats znodes if provided
-
Key: HBASE-7244
URL: https://issues.apache.org/jira/browse/HBASE-7244
Project: HBase
Issue Type: New Feature
Components: Zookeeper
Affects Versions: 0.94.0
Reporter: Harsh J
Assignee: rajeshbabu
Priority: Minor
Fix For: 0.95.1, 0.98.0, 0.94.7
Attachments: HBASE-7244_2.patch, HBASE-7244_3.patch, HBASE-7244.patch
Many a times I've had to, and have seen instructions being thrown, to stop
cluster, clear out ZK and restart.
While this is only a quick (and painful to master) fix, it is certainly nifty
to some smaller cluster users but the process is far too long, roughly:
1. Stop HBase
2. Start zkCli.sh and connect to the right quorum
3. Find and ensure the HBase parent znode from the configs (/hbase only by
default)
4. Run an rmr /hbase in the zkCli.sh shell, or manually delete each znode
if on a lower version of ZK.
5. Quit zkCli.sh and start HBase again
Perhaps it may be useful, if the start-hbase.sh itself accepted a formatZK
parameter. Such that, when you do a {{start-hbase.sh -formatZK}}, it does
steps 2-4 automatically for you.
For safety, we could make the formatter code ensure that no HBase instance is
actually active, and skip the format process if it is.
[jira] [Commented] (HBASE-8258) Make mapreduce tests pass on hadoop2
[ https://issues.apache.org/jira/browse/HBASE-8258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13622415#comment-13622415 ] Jonathan Hsieh commented on HBASE-8258: --- [~stack] yeah, saw that -- I think instead of depending on the new flag in 2.0.4, we should be able to just bump those numbers to bypass the failures. Currently trying this. Make mapreduce tests pass on hadoop2 Key: HBASE-8258 URL: https://issues.apache.org/jira/browse/HBASE-8258 Project: HBase Issue Type: Bug Components: mapreduce Reporter: stack Priority: Blocker Fix For: 0.95.1 Attachments: 8258-plain.txt HBASE-7904 was a first attempt at making this work but it got lost in the weeds. This is a new attempt at making hbase mapreduce jobs run on hadoop2 (w/o breaking mapreduce on hadoop1) -- 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-8262) Add testcase to verify HBASE-7678's empty region split semantics change
[ https://issues.apache.org/jira/browse/HBASE-8262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Hsieh updated HBASE-8262: -- Resolution: Fixed Fix Version/s: 0.98.0 Hadoop Flags: Reviewed Status: Resolved (was: Patch Available) Commited to trunk, doesn't apply cleanly to 0.95 due to HBASE-8008. Add testcase to verify HBASE-7678's empty region split semantics change --- Key: HBASE-8262 URL: https://issues.apache.org/jira/browse/HBASE-8262 Project: HBase Issue Type: Bug Affects Versions: 0.95.0, 0.96.0, 0.98.0, 0.94.6 Reporter: Jonathan Hsieh Assignee: Jonathan Hsieh Fix For: 0.98.0 Attachments: hbase-8262.patch HBASE-7678 change the semantics of splits and removed a test case but didn't not add one to verify behavior. We'll add one here. -- 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-8008) Fix DirFilter usage to be consistent
[ https://issues.apache.org/jira/browse/HBASE-8008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Hsieh updated HBASE-8008: -- Fix Version/s: (was: 0.96.0) 0.98.0 Fix DirFilter usage to be consistent Key: HBASE-8008 URL: https://issues.apache.org/jira/browse/HBASE-8008 Project: HBase Issue Type: Sub-task Reporter: Jesse Yates Assignee: Jesse Yates Fix For: 0.98.0 Attachments: hbase-8008-r0.patch, hbase-8008-r1.patch Currently the DirFilter automatically filters out HConstants.HBASE_NON_USER_TABLE_DIRS, which is not needed in most cases. We should switch the usage so people actually using a directory filter and then have a special filter when looking for tables specifically. -- 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-8008) Fix DirFilter usage to be consistent
[ https://issues.apache.org/jira/browse/HBASE-8008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13622419#comment-13622419 ] Jonathan Hsieh commented on HBASE-8008: --- Changed version to 0.98 -- 0.96 will be off of 0.95 and this patch isn't in there. Fix DirFilter usage to be consistent Key: HBASE-8008 URL: https://issues.apache.org/jira/browse/HBASE-8008 Project: HBase Issue Type: Sub-task Reporter: Jesse Yates Assignee: Jesse Yates Fix For: 0.98.0 Attachments: hbase-8008-r0.patch, hbase-8008-r1.patch Currently the DirFilter automatically filters out HConstants.HBASE_NON_USER_TABLE_DIRS, which is not needed in most cases. We should switch the usage so people actually using a directory filter and then have a special filter when looking for tables specifically. -- 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
