[jira] [Commented] (HBASE-7337) SingleColumnValueFilter seems to get unavailble data
[
https://issues.apache.org/jira/browse/HBASE-7337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13532066#comment-13532066
]
Zhou wenjian commented on HBASE-7337:
-
[~anoopsamjohn]
actually i did get all the versions.
when using SCVF, it is not allowed to set version in the scan for it will get
data againset SCVF,do you mean it?
> SingleColumnValueFilter seems to get unavailble data
>
>
> Key: HBASE-7337
> URL: https://issues.apache.org/jira/browse/HBASE-7337
> Project: HBase
> Issue Type: Bug
> Components: Filters
>Affects Versions: 0.94.3, 0.96.0
> Environment: 0.94
>Reporter: Zhou wenjian
>Assignee: Zhou wenjian
> Fix For: 0.96.0, 0.94.4
>
>
> put multi versions of a row.
> r1 cf:q version:1 value:1
> r1 cf:q version:2 value:3
> r1 cf:q version:3 value:2
> the filter in scan is set as below:
> SingleColumnValueFilter valueF = new SingleColumnValueFilter(
> family,qualifier,CompareOp.EQUAL,new BinaryComparator(Bytes
> .toBytes("2")));
> then i found all of the three versions will be emmitted, then i set
> latestVersionOnly to false, the result does no change.
> public ReturnCode filterKeyValue(KeyValue keyValue) {
> // System.out.println("REMOVE KEY=" + keyValue.toString() + ", value=" +
> Bytes.toString(keyValue.getValue()));
> if (this.matchedColumn) {
> // We already found and matched the single column, all keys now pass
> return ReturnCode.INCLUDE;
> } else if (this.latestVersionOnly && this.foundColumn) {
> // We found but did not match the single column, skip to next row
> return ReturnCode.NEXT_ROW;
> }
> if (!keyValue.matchingColumn(this.columnFamily, this.columnQualifier)) {
> return ReturnCode.INCLUDE;
> }
> foundColumn = true;
> if (filterColumnValue(keyValue.getBuffer(),
> keyValue.getValueOffset(), keyValue.getValueLength())) {
> return this.latestVersionOnly? ReturnCode.NEXT_ROW: ReturnCode.INCLUDE;
> }
> this.matchedColumn = true;
> return ReturnCode.INCLUDE;
> }
> From the code above, it seeems that version 3 will be first emmited, and set
> matchedColumn to true, which leads the following version 2 and 1 emmited too.
--
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-7337) SingleColumnValueFilter seems to get unavailble data
[
https://issues.apache.org/jira/browse/HBASE-7337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13529773#comment-13529773
]
Zhou wenjian commented on HBASE-7337:
-
they are both String
> SingleColumnValueFilter seems to get unavailble data
>
>
> Key: HBASE-7337
> URL: https://issues.apache.org/jira/browse/HBASE-7337
> Project: HBase
> Issue Type: Bug
> Components: Filters
>Affects Versions: 0.94.3, 0.96.0
> Environment: 0.94
>Reporter: Zhou wenjian
>Assignee: Zhou wenjian
> Fix For: 0.96.0, 0.94.4
>
>
> put multi versions of a row.
> r1 cf:q version:1 value:1
> r1 cf:q version:2 value:3
> r1 cf:q version:3 value:2
> the filter in scan is set as below:
> SingleColumnValueFilter valueF = new SingleColumnValueFilter(
> family,qualifier,CompareOp.EQUAL,new BinaryComparator(Bytes
> .toBytes("2")));
> then i found all of the three versions will be emmitted, then i set
> latestVersionOnly to false, the result does no change.
> public ReturnCode filterKeyValue(KeyValue keyValue) {
> // System.out.println("REMOVE KEY=" + keyValue.toString() + ", value=" +
> Bytes.toString(keyValue.getValue()));
> if (this.matchedColumn) {
> // We already found and matched the single column, all keys now pass
> return ReturnCode.INCLUDE;
> } else if (this.latestVersionOnly && this.foundColumn) {
> // We found but did not match the single column, skip to next row
> return ReturnCode.NEXT_ROW;
> }
> if (!keyValue.matchingColumn(this.columnFamily, this.columnQualifier)) {
> return ReturnCode.INCLUDE;
> }
> foundColumn = true;
> if (filterColumnValue(keyValue.getBuffer(),
> keyValue.getValueOffset(), keyValue.getValueLength())) {
> return this.latestVersionOnly? ReturnCode.NEXT_ROW: ReturnCode.INCLUDE;
> }
> this.matchedColumn = true;
> return ReturnCode.INCLUDE;
> }
> From the code above, it seeems that version 3 will be first emmited, and set
> matchedColumn to true, which leads the following version 2 and 1 emmited too.
--
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-7337) SingleColumnValueFilter seems to get unavailble data
[
https://issues.apache.org/jira/browse/HBASE-7337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhou wenjian updated HBASE-7337:
Description:
put multi versions of a row.
r1 cf:q version:1 value:1
r1 cf:q version:2 value:3
r1 cf:q version:3 value:2
the filter in scan is set as below:
SingleColumnValueFilter valueF = new SingleColumnValueFilter(
family,qualifier,CompareOp.EQUAL,new BinaryComparator(Bytes
.toBytes("2")));
then i found all of the three versions will be emmitted, then i set
latestVersionOnly to false, the result does no change.
public ReturnCode filterKeyValue(KeyValue keyValue) {
// System.out.println("REMOVE KEY=" + keyValue.toString() + ", value=" +
Bytes.toString(keyValue.getValue()));
if (this.matchedColumn) {
// We already found and matched the single column, all keys now pass
return ReturnCode.INCLUDE;
} else if (this.latestVersionOnly && this.foundColumn) {
// We found but did not match the single column, skip to next row
return ReturnCode.NEXT_ROW;
}
if (!keyValue.matchingColumn(this.columnFamily, this.columnQualifier)) {
return ReturnCode.INCLUDE;
}
foundColumn = true;
if (filterColumnValue(keyValue.getBuffer(),
keyValue.getValueOffset(), keyValue.getValueLength())) {
return this.latestVersionOnly? ReturnCode.NEXT_ROW: ReturnCode.INCLUDE;
}
this.matchedColumn = true;
return ReturnCode.INCLUDE;
}
>From the code above, it seeems that version 3 will be first emmited, and set
>matchedColumn to true, which leads the following version 2 and 1 emmited too.
was:
put multi versions of a row.
r1 cf:q version:1 value:1
r1 cf:q version:2 value:3
r1 cf:q version:3 value:2
the filter in scan is set as below:
SingleColumnValueFilter valueF = new SingleColumnValueFilter(
family,qualifier,CompareOp.EQUAL,new BinaryComparator(Bytes
.toBytes("2")));
then i found all of the three versions will be emmitted, then i set
latestVersionOnly to false, the result does no change.
public ReturnCode filterKeyValue(KeyValue keyValue) {
// System.out.println("REMOVE KEY=" + keyValue.toString() + ", value=" +
Bytes.toString(keyValue.getValue()));
if (this.matchedColumn) {
// We already found and matched the single column, all keys now pass
return ReturnCode.INCLUDE;
} else if (this.latestVersionOnly && this.foundColumn) {
// We found but did not match the single column, skip to next row
return ReturnCode.NEXT_ROW;
}
if (!keyValue.matchingColumn(this.columnFamily, this.columnQualifier)) {
return ReturnCode.INCLUDE;
}
foundColumn = true;
if (filterColumnValue(keyValue.getBuffer(),
keyValue.getValueOffset(), keyValue.getValueLength())) {
return this.latestVersionOnly? ReturnCode.NEXT_ROW: ReturnCode.INCLUDE;
}
this.matchedColumn = true;
return ReturnCode.INCLUDE;
}
>From the code above, it seeems that version 3 will be first emmited, and set
>matchedColumn to false, which leads the following version 2 and 1 emmited too.
> SingleColumnValueFilter seems to get unavailble data
>
>
> Key: HBASE-7337
> URL: https://issues.apache.org/jira/browse/HBASE-7337
> Project: HBase
> Issue Type: Bug
> Components: Filters
>Affects Versions: 0.94.3, 0.96.0
> Environment: 0.94
>Reporter: Zhou wenjian
>Assignee: Zhou wenjian
> Fix For: 0.96.0, 0.94.4
>
>
> put multi versions of a row.
> r1 cf:q version:1 value:1
> r1 cf:q version:2 value:3
> r1 cf:q version:3 value:2
> the filter in scan is set as below:
> SingleColumnValueFilter valueF = new SingleColumnValueFilter(
> family,qualifier,CompareOp.EQUAL,new BinaryComparator(Bytes
> .toBytes("2")));
> then i found all of the three versions will be emmitted, then i set
> latestVersionOnly to false, the result does no change.
> public ReturnCode filterKeyValue(KeyValue keyValue) {
> // System.out.println("REMOVE KEY=" + keyValue.toString() + ", value=" +
> Bytes.toString(keyValue.getValue()));
> if (this.matchedColumn) {
> // We already found and matched the single column, all keys now pass
> return ReturnCode.INCLUDE;
> } else if (this.latestVersionOnly && this.foundColumn) {
> // We found but did not match the single column, skip to next row
> return ReturnCode.NEXT_ROW;
> }
> if (!keyValue.matchingColumn(this.columnFamily, this.columnQualifier)) {
> return ReturnCode.INCLUDE;
> }
> foundColumn = true;
> if (filterColumnValue(keyValue.getBuffer(),
> keyValue.getValueOffset(), keyValue.getValueLength())) {
> return this.latestVersionOnly? ReturnCode.NEXT_ROW: ReturnCode.INCLUDE;
> }
> this.matchedColumn = true;
> return ReturnCode.IN
[jira] [Created] (HBASE-7337) SingleColumnValueFilter seems to get unavailble data
Zhou wenjian created HBASE-7337:
---
Summary: SingleColumnValueFilter seems to get unavailble data
Key: HBASE-7337
URL: https://issues.apache.org/jira/browse/HBASE-7337
Project: HBase
Issue Type: Bug
Components: Filters
Affects Versions: 0.94.3, 0.96.0
Environment: 0.94
Reporter: Zhou wenjian
Assignee: Zhou wenjian
Fix For: 0.96.0, 0.94.4
put multi versions of a row.
r1 cf:q version:1 value:1
r1 cf:q version:2 value:3
r1 cf:q version:3 value:2
the filter in scan is set as below:
SingleColumnValueFilter valueF = new SingleColumnValueFilter(
family,qualifier,CompareOp.EQUAL,new BinaryComparator(Bytes
.toBytes("2")));
then i found all of the three versions will be emmitted, then i set
latestVersionOnly to false, the result does no change.
public ReturnCode filterKeyValue(KeyValue keyValue) {
// System.out.println("REMOVE KEY=" + keyValue.toString() + ", value=" +
Bytes.toString(keyValue.getValue()));
if (this.matchedColumn) {
// We already found and matched the single column, all keys now pass
return ReturnCode.INCLUDE;
} else if (this.latestVersionOnly && this.foundColumn) {
// We found but did not match the single column, skip to next row
return ReturnCode.NEXT_ROW;
}
if (!keyValue.matchingColumn(this.columnFamily, this.columnQualifier)) {
return ReturnCode.INCLUDE;
}
foundColumn = true;
if (filterColumnValue(keyValue.getBuffer(),
keyValue.getValueOffset(), keyValue.getValueLength())) {
return this.latestVersionOnly? ReturnCode.NEXT_ROW: ReturnCode.INCLUDE;
}
this.matchedColumn = true;
return ReturnCode.INCLUDE;
}
>From the code above, it seeems that version 3 will be first emmited, and set
>matchedColumn to false, which leads the following version 2 and 1 emmited too.
--
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-6563) s.isMajorCompaction() throws npe will cause current major Compaction checking abort
[
https://issues.apache.org/jira/browse/HBASE-6563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13493060#comment-13493060
]
Zhou wenjian commented on HBASE-6563:
-
[~lhofhansl]
not quite follow you, the npe will be throwed in trunk too, i think.
private boolean isMajorCompaction(final List filesToCompact) throws
IOException {
boolean result = false;
long mcTime = getNextMajorCompactTime();
if (filesToCompact == null || filesToCompact.isEmpty() || mcTime == 0) {
return result;
} long lowTimestamp = getLowestTimestamp(filesToCompact);
long now = System.currentTimeMillis();
if (lowTimestamp > 0l && lowTimestamp < (now - mcTime)) {
// Major compaction time has elapsed.
if (filesToCompact.size() == 1) {
// Single file
StoreFile sf = filesToCompact.get(0);
long oldest =
(sf.getReader().timeRangeTracker == null) ?
Long.MIN_VALUE :
now - sf.getReader().timeRangeTracker.minimumTimestamp;
if the file to compact is closed after the check, npe will be throwed too,
which is same to 94 and 90.
the bad side is that current major compaction check for region is interrupted
IMO, need to catch and just Ingore it.
> s.isMajorCompaction() throws npe will cause current major Compaction checking
> abort
> ---
>
> Key: HBASE-6563
> URL: https://issues.apache.org/jira/browse/HBASE-6563
> Project: HBase
> Issue Type: Bug
> Components: regionserver
>Reporter: Zhou wenjian
>Assignee: Zhou wenjian
> Attachments: HBASE-6563-trunk.patch, HBASE-6563-trunk-v2.patch,
> HBASE-6563-trunk-v3.patch
>
>
> 2012-05-05 00:49:43,265 ERROR
> org.apache.hadoop.hbase.regionserver.HRegionServer$MajorCompactionChecker:
> Caught exception
> java.lang.NullPointerException
> at
> org.apache.hadoop.hbase.regionserver.Store.isMajorCompaction(Store.java:938)
> at
> org.apache.hadoop.hbase.regionserver.Store.isMajorCompaction(Store.java:917)
> at
> org.apache.hadoop.hbase.regionserver.HRegion.isMajorCompaction(HRegion.java:3250)
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer$MajorCompactionChecker.chore(HRegionServer.java:1222)
> at org.apache.hadoop.hbase.Chore.run(Chore.java:66)
--
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-7111) hbase zkcli will not start if the zookeeper server choosen to connectted to is not available
[
https://issues.apache.org/jira/browse/HBASE-7111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13493030#comment-13493030
]
Zhou wenjian commented on HBASE-7111:
-
The testcase modified could assert my change.
And i have tested it in my local test cluster, if one of the zookeeper server
in conf works, the script will connect to zookeeper
> hbase zkcli will not start if the zookeeper server choosen to connectted to
> is not available
> -
>
> Key: HBASE-7111
> URL: https://issues.apache.org/jira/browse/HBASE-7111
> Project: HBase
> Issue Type: Bug
> Components: Zookeeper
>Affects Versions: 0.94.2
>Reporter: Zhou wenjian
>Assignee: Zhou wenjian
> Fix For: 0.94.4
>
> Attachments: HBASE-7111-trunk.patch, HBASE-7111-trunk-v2.patch
>
>
> there are 3 zookeeper servers in my cluster.
> s1
> s2
> s3
> after killing s3, i found the hbase zkcli will not start again.
> it will try to connect to s3 continuely.
> /11/07 11:01:01 INFO zookeeper.ClientCnxn: Opening socket connection to
> server s3
> 12/11/07 11:01:01 WARN zookeeper.ClientCnxn: Session 0x0 for server null,
> unexpected error, closing socket connection and attempting reconnect
> java.net.ConnectException: Connection refused
> from the code
> public String parse(final Configuration c) {
> // Note that we do not simply grab the property
> // HConstants.ZOOKEEPER_QUORUM from the HBaseConfiguration because the
> // user may be using a zoo.cfg file.
> Properties zkProps = ZKConfig.makeZKProps(c);
> String host = null;
> String clientPort = null;
> for (Entry entry: zkProps.entrySet()) {
> String key = entry.getKey().toString().trim();
> String value = entry.getValue().toString().trim();
> if (key.startsWith("server.") && host == null) {
> String[] parts = value.split(":");
> host = parts[0];
> } else if (key.endsWith("clientPort")) {
> clientPort = value;
> }
> if (host != null && clientPort != null) break;
> }
> return host != null && clientPort != null? host + ":" + clientPort: null;
> }
> the code will choose the fixed zookeeper server (here is the unavailable s3),
> which leads to the script fails
--
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-7111) hbase zkcli will not start if the zookeeper server choosen to connectted to is not available
[
https://issues.apache.org/jira/browse/HBASE-7111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhou wenjian updated HBASE-7111:
Attachment: HBASE-7111-trunk-v2.patch
> hbase zkcli will not start if the zookeeper server choosen to connectted to
> is not available
> -
>
> Key: HBASE-7111
> URL: https://issues.apache.org/jira/browse/HBASE-7111
> Project: HBase
> Issue Type: Bug
> Components: Zookeeper
>Affects Versions: 0.94.2
>Reporter: Zhou wenjian
>Assignee: Zhou wenjian
> Fix For: 0.94.4
>
> Attachments: HBASE-7111-trunk.patch, HBASE-7111-trunk-v2.patch
>
>
> there are 3 zookeeper servers in my cluster.
> s1
> s2
> s3
> after killing s3, i found the hbase zkcli will not start again.
> it will try to connect to s3 continuely.
> /11/07 11:01:01 INFO zookeeper.ClientCnxn: Opening socket connection to
> server s3
> 12/11/07 11:01:01 WARN zookeeper.ClientCnxn: Session 0x0 for server null,
> unexpected error, closing socket connection and attempting reconnect
> java.net.ConnectException: Connection refused
> from the code
> public String parse(final Configuration c) {
> // Note that we do not simply grab the property
> // HConstants.ZOOKEEPER_QUORUM from the HBaseConfiguration because the
> // user may be using a zoo.cfg file.
> Properties zkProps = ZKConfig.makeZKProps(c);
> String host = null;
> String clientPort = null;
> for (Entry entry: zkProps.entrySet()) {
> String key = entry.getKey().toString().trim();
> String value = entry.getValue().toString().trim();
> if (key.startsWith("server.") && host == null) {
> String[] parts = value.split(":");
> host = parts[0];
> } else if (key.endsWith("clientPort")) {
> clientPort = value;
> }
> if (host != null && clientPort != null) break;
> }
> return host != null && clientPort != null? host + ":" + clientPort: null;
> }
> the code will choose the fixed zookeeper server (here is the unavailable s3),
> which leads to the script fails
--
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-7111) hbase zkcli will not start if the zookeeper server choosen to connectted to is not available
[
https://issues.apache.org/jira/browse/HBASE-7111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13492917#comment-13492917
]
Zhou wenjian commented on HBASE-7111:
-
patch for trunk
> hbase zkcli will not start if the zookeeper server choosen to connectted to
> is not available
> -
>
> Key: HBASE-7111
> URL: https://issues.apache.org/jira/browse/HBASE-7111
> Project: HBase
> Issue Type: Bug
> Components: Zookeeper
>Affects Versions: 0.94.2
>Reporter: Zhou wenjian
>Assignee: Zhou wenjian
> Fix For: 0.94.4
>
> Attachments: HBASE-7111-trunk.patch
>
>
> there are 3 zookeeper servers in my cluster.
> s1
> s2
> s3
> after killing s3, i found the hbase zkcli will not start again.
> it will try to connect to s3 continuely.
> /11/07 11:01:01 INFO zookeeper.ClientCnxn: Opening socket connection to
> server s3
> 12/11/07 11:01:01 WARN zookeeper.ClientCnxn: Session 0x0 for server null,
> unexpected error, closing socket connection and attempting reconnect
> java.net.ConnectException: Connection refused
> from the code
> public String parse(final Configuration c) {
> // Note that we do not simply grab the property
> // HConstants.ZOOKEEPER_QUORUM from the HBaseConfiguration because the
> // user may be using a zoo.cfg file.
> Properties zkProps = ZKConfig.makeZKProps(c);
> String host = null;
> String clientPort = null;
> for (Entry entry: zkProps.entrySet()) {
> String key = entry.getKey().toString().trim();
> String value = entry.getValue().toString().trim();
> if (key.startsWith("server.") && host == null) {
> String[] parts = value.split(":");
> host = parts[0];
> } else if (key.endsWith("clientPort")) {
> clientPort = value;
> }
> if (host != null && clientPort != null) break;
> }
> return host != null && clientPort != null? host + ":" + clientPort: null;
> }
> the code will choose the fixed zookeeper server (here is the unavailable s3),
> which leads to the script fails
--
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-7111) hbase zkcli will not start if the zookeeper server choosen to connectted to is not available
[
https://issues.apache.org/jira/browse/HBASE-7111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhou wenjian updated HBASE-7111:
Attachment: HBASE-7111-trunk.patch
> hbase zkcli will not start if the zookeeper server choosen to connectted to
> is not available
> -
>
> Key: HBASE-7111
> URL: https://issues.apache.org/jira/browse/HBASE-7111
> Project: HBase
> Issue Type: Bug
> Components: Zookeeper
>Affects Versions: 0.94.2
>Reporter: Zhou wenjian
>Assignee: Zhou wenjian
> Fix For: 0.94.4
>
> Attachments: HBASE-7111-trunk.patch
>
>
> there are 3 zookeeper servers in my cluster.
> s1
> s2
> s3
> after killing s3, i found the hbase zkcli will not start again.
> it will try to connect to s3 continuely.
> /11/07 11:01:01 INFO zookeeper.ClientCnxn: Opening socket connection to
> server s3
> 12/11/07 11:01:01 WARN zookeeper.ClientCnxn: Session 0x0 for server null,
> unexpected error, closing socket connection and attempting reconnect
> java.net.ConnectException: Connection refused
> from the code
> public String parse(final Configuration c) {
> // Note that we do not simply grab the property
> // HConstants.ZOOKEEPER_QUORUM from the HBaseConfiguration because the
> // user may be using a zoo.cfg file.
> Properties zkProps = ZKConfig.makeZKProps(c);
> String host = null;
> String clientPort = null;
> for (Entry entry: zkProps.entrySet()) {
> String key = entry.getKey().toString().trim();
> String value = entry.getValue().toString().trim();
> if (key.startsWith("server.") && host == null) {
> String[] parts = value.split(":");
> host = parts[0];
> } else if (key.endsWith("clientPort")) {
> clientPort = value;
> }
> if (host != null && clientPort != null) break;
> }
> return host != null && clientPort != null? host + ":" + clientPort: null;
> }
> the code will choose the fixed zookeeper server (here is the unavailable s3),
> which leads to the script fails
--
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-7111) hbase zkcli will not start if the zookeeper server choosen to connectted to is not available
[
https://issues.apache.org/jira/browse/HBASE-7111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13492898#comment-13492898
]
Zhou wenjian commented on HBASE-7111:
-
will give a patch later
> hbase zkcli will not start if the zookeeper server choosen to connectted to
> is not available
> -
>
> Key: HBASE-7111
> URL: https://issues.apache.org/jira/browse/HBASE-7111
> Project: HBase
> Issue Type: Bug
> Components: Zookeeper
>Affects Versions: 0.94.2
>Reporter: Zhou wenjian
>Assignee: Zhou wenjian
> Fix For: 0.94.4
>
>
> there are 3 zookeeper servers in my cluster.
> s1
> s2
> s3
> after killing s3, i found the hbase zkcli will not start again.
> it will try to connect to s3 continuely.
> /11/07 11:01:01 INFO zookeeper.ClientCnxn: Opening socket connection to
> server s3
> 12/11/07 11:01:01 WARN zookeeper.ClientCnxn: Session 0x0 for server null,
> unexpected error, closing socket connection and attempting reconnect
> java.net.ConnectException: Connection refused
> from the code
> public String parse(final Configuration c) {
> // Note that we do not simply grab the property
> // HConstants.ZOOKEEPER_QUORUM from the HBaseConfiguration because the
> // user may be using a zoo.cfg file.
> Properties zkProps = ZKConfig.makeZKProps(c);
> String host = null;
> String clientPort = null;
> for (Entry entry: zkProps.entrySet()) {
> String key = entry.getKey().toString().trim();
> String value = entry.getValue().toString().trim();
> if (key.startsWith("server.") && host == null) {
> String[] parts = value.split(":");
> host = parts[0];
> } else if (key.endsWith("clientPort")) {
> clientPort = value;
> }
> if (host != null && clientPort != null) break;
> }
> return host != null && clientPort != null? host + ":" + clientPort: null;
> }
> the code will choose the fixed zookeeper server (here is the unavailable s3),
> which leads to the script fails
--
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-7111) hbase zkcli will not start if the zookeeper server choosen to connectted to is not available
[
https://issues.apache.org/jira/browse/HBASE-7111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13492882#comment-13492882
]
Zhou wenjian commented on HBASE-7111:
-
[~saint@gmail.com]
i have s1,s2,s3 in my configuration
but the script will always choose s3 which is unavailable
> hbase zkcli will not start if the zookeeper server choosen to connectted to
> is not available
> -
>
> Key: HBASE-7111
> URL: https://issues.apache.org/jira/browse/HBASE-7111
> Project: HBase
> Issue Type: Bug
> Components: Zookeeper
>Affects Versions: 0.94.2
>Reporter: Zhou wenjian
>Assignee: Zhou wenjian
> Fix For: 0.94.4
>
>
> there are 3 zookeeper servers in my cluster.
> s1
> s2
> s3
> after killing s3, i found the hbase zkcli will not start again.
> it will try to connect to s3 continuely.
> /11/07 11:01:01 INFO zookeeper.ClientCnxn: Opening socket connection to
> server s3
> 12/11/07 11:01:01 WARN zookeeper.ClientCnxn: Session 0x0 for server null,
> unexpected error, closing socket connection and attempting reconnect
> java.net.ConnectException: Connection refused
> from the code
> public String parse(final Configuration c) {
> // Note that we do not simply grab the property
> // HConstants.ZOOKEEPER_QUORUM from the HBaseConfiguration because the
> // user may be using a zoo.cfg file.
> Properties zkProps = ZKConfig.makeZKProps(c);
> String host = null;
> String clientPort = null;
> for (Entry entry: zkProps.entrySet()) {
> String key = entry.getKey().toString().trim();
> String value = entry.getValue().toString().trim();
> if (key.startsWith("server.") && host == null) {
> String[] parts = value.split(":");
> host = parts[0];
> } else if (key.endsWith("clientPort")) {
> clientPort = value;
> }
> if (host != null && clientPort != null) break;
> }
> return host != null && clientPort != null? host + ":" + clientPort: null;
> }
> the code will choose the fixed zookeeper server (here is the unavailable s3),
> which leads to the script fails
--
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-7112) ZK_CLIENT_PORT_KEY maybe is not correct
[ https://issues.apache.org/jira/browse/HBASE-7112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13492163#comment-13492163 ] Zhou wenjian commented on HBASE-7112: - 94 has correct it， just for 90. > ZK_CLIENT_PORT_KEY maybe is not correct > --- > > Key: HBASE-7112 > URL: https://issues.apache.org/jira/browse/HBASE-7112 > Project: HBase > Issue Type: Bug > Components: Zookeeper >Affects Versions: 0.90.6 >Reporter: Zhou wenjian > Fix For: 0.90.7 > > > the ZK_CLIENT_PORT_KEY is declared as followed: > private static final String ZK_CFG_PROPERTY = "hbase.zookeeper.property."; > private static final String ZK_CLIENT_PORT_KEY = ZK_CFG_PROPERTY > + "clientPort"; > i think it is not correct exactly, it should not contain the prefix > ZK_CFG_PROPERTY. > IMO, need to change it to private static final String ZK_CLIENT_PORT_KEY = > "clientPort"; -- 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-7112) ZK_CLIENT_PORT_KEY maybe is not correct
[ https://issues.apache.org/jira/browse/HBASE-7112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhou wenjian updated HBASE-7112: Affects Version/s: (was: 0.94.2) 0.90.6 Fix Version/s: (was: 0.94.4) 0.90.7 > ZK_CLIENT_PORT_KEY maybe is not correct > --- > > Key: HBASE-7112 > URL: https://issues.apache.org/jira/browse/HBASE-7112 > Project: HBase > Issue Type: Bug > Components: Zookeeper >Affects Versions: 0.90.6 >Reporter: Zhou wenjian > Fix For: 0.90.7 > > > the ZK_CLIENT_PORT_KEY is declared as followed: > private static final String ZK_CFG_PROPERTY = "hbase.zookeeper.property."; > private static final String ZK_CLIENT_PORT_KEY = ZK_CFG_PROPERTY > + "clientPort"; > i think it is not correct exactly, it should not contain the prefix > ZK_CFG_PROPERTY. > IMO, need to change it to private static final String ZK_CLIENT_PORT_KEY = > "clientPort"; -- 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-7112) ZK_CLIENT_PORT_KEY maybe is not correct
Zhou wenjian created HBASE-7112: --- Summary: ZK_CLIENT_PORT_KEY maybe is not correct Key: HBASE-7112 URL: https://issues.apache.org/jira/browse/HBASE-7112 Project: HBase Issue Type: Bug Components: Zookeeper Affects Versions: 0.94.2 Reporter: Zhou wenjian Fix For: 0.94.4 the ZK_CLIENT_PORT_KEY is declared as followed: private static final String ZK_CFG_PROPERTY = "hbase.zookeeper.property."; private static final String ZK_CLIENT_PORT_KEY = ZK_CFG_PROPERTY + "clientPort"; i think it is not correct exactly, it should not contain the prefix ZK_CFG_PROPERTY. IMO, need to change it to private static final String ZK_CLIENT_PORT_KEY = "clientPort"; -- 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-7111) hbase zkcli will not start if the zookeeper server choosen to connectted to is not available
[
https://issues.apache.org/jira/browse/HBASE-7111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13492089#comment-13492089
]
Zhou wenjian commented on HBASE-7111:
-
IMO, need to choose a random server to connect, rather than the fixed one which
is depended on the properties reading from conf
> hbase zkcli will not start if the zookeeper server choosen to connectted to
> is not available
> -
>
> Key: HBASE-7111
> URL: https://issues.apache.org/jira/browse/HBASE-7111
> Project: HBase
> Issue Type: Bug
> Components: Zookeeper
>Affects Versions: 0.94.2
>Reporter: Zhou wenjian
>Assignee: Zhou wenjian
> Fix For: 0.94.4
>
>
> there are 3 zookeeper servers in my cluster.
> s1
> s2
> s3
> after killing s3, i found the hbase zkcli will not start again.
> it will try to connect to s3 continuely.
> /11/07 11:01:01 INFO zookeeper.ClientCnxn: Opening socket connection to
> server s3
> 12/11/07 11:01:01 WARN zookeeper.ClientCnxn: Session 0x0 for server null,
> unexpected error, closing socket connection and attempting reconnect
> java.net.ConnectException: Connection refused
> from the code
> public String parse(final Configuration c) {
> // Note that we do not simply grab the property
> // HConstants.ZOOKEEPER_QUORUM from the HBaseConfiguration because the
> // user may be using a zoo.cfg file.
> Properties zkProps = ZKConfig.makeZKProps(c);
> String host = null;
> String clientPort = null;
> for (Entry entry: zkProps.entrySet()) {
> String key = entry.getKey().toString().trim();
> String value = entry.getValue().toString().trim();
> if (key.startsWith("server.") && host == null) {
> String[] parts = value.split(":");
> host = parts[0];
> } else if (key.endsWith("clientPort")) {
> clientPort = value;
> }
> if (host != null && clientPort != null) break;
> }
> return host != null && clientPort != null? host + ":" + clientPort: null;
> }
> the code will choose the fixed zookeeper server (here is the unavailable s3),
> which leads to the script fails
--
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-7111) hbase zkcli will not start if the zookeeper server choosen to connectted to is not available
Zhou wenjian created HBASE-7111:
---
Summary: hbase zkcli will not start if the zookeeper server
choosen to connectted to is not available
Key: HBASE-7111
URL: https://issues.apache.org/jira/browse/HBASE-7111
Project: HBase
Issue Type: Bug
Components: Zookeeper
Affects Versions: 0.94.2
Reporter: Zhou wenjian
Assignee: Zhou wenjian
Fix For: 0.94.4
there are 3 zookeeper servers in my cluster.
s1
s2
s3
after killing s3, i found the hbase zkcli will not start again.
it will try to connect to s3 continuely.
/11/07 11:01:01 INFO zookeeper.ClientCnxn: Opening socket connection to server
s3
12/11/07 11:01:01 WARN zookeeper.ClientCnxn: Session 0x0 for server null,
unexpected error, closing socket connection and attempting reconnect
java.net.ConnectException: Connection refused
from the code
public String parse(final Configuration c) {
// Note that we do not simply grab the property
// HConstants.ZOOKEEPER_QUORUM from the HBaseConfiguration because the
// user may be using a zoo.cfg file.
Properties zkProps = ZKConfig.makeZKProps(c);
String host = null;
String clientPort = null;
for (Entry entry: zkProps.entrySet()) {
String key = entry.getKey().toString().trim();
String value = entry.getValue().toString().trim();
if (key.startsWith("server.") && host == null) {
String[] parts = value.split(":");
host = parts[0];
} else if (key.endsWith("clientPort")) {
clientPort = value;
}
if (host != null && clientPort != null) break;
}
return host != null && clientPort != null? host + ":" + clientPort: null;
}
the code will choose the fixed zookeeper server (here is the unavailable s3),
which leads to the script fails
--
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-7079) testCloseRegionWhenEncodedRegionNameIsNotGiven occainlly fails
[ https://issues.apache.org/jira/browse/HBASE-7079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13487566#comment-13487566 ] Zhou wenjian commented on HBASE-7079: - patch for trunk > testCloseRegionWhenEncodedRegionNameIsNotGiven occainlly fails > -- > > Key: HBASE-7079 > URL: https://issues.apache.org/jira/browse/HBASE-7079 > Project: HBase > Issue Type: Bug > Components: test >Affects Versions: 0.94.2 >Reporter: Zhou wenjian >Assignee: Zhou wenjian > Attachments: HBASE-7079-trunk.patch, HBASE-7079-trunk-v2.patch > > > Regression > org.apache.hadoop.hbase.client.TestAdmin.testCloseRegionWhenEncodedRegionNameIsNotGiven > Failing for the past 1 build (Since #147 ) > Took 2 ms. > Error Message > -1 > Stacktrace > java.lang.ArrayIndexOutOfBoundsException: -1 > at > java.util.concurrent.CopyOnWriteArrayList.get(CopyOnWriteArrayList.java:343) > at java.util.Collections$UnmodifiableList.get(Collections.java:1154) > at > org.apache.hadoop.hbase.HBaseTestingUtility.getRSForFirstRegionInTable(HBaseTestingUtility.java:1300) > at > org.apache.hadoop.hbase.client.TestAdmin.testCloseRegionWhenEncodedRegionNameIsNotGiven(TestAdmin.java:1454) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at > org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45) > at > org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) > at > org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42) > at > org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20) > at > org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28) > at > org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:30) > at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:47) > at org.junit.rules.RunRules.evaluate(RunRules.java:18) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:263) > at > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:68) > at > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:47) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:60) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:229) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:50) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:222) > at > org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28) > at > org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:30) > at org.junit.runners.ParentRunner.run(ParentRunner.java:300) > at org.junit.runners.Suite.runChild(Suite.java:128) > at org.junit.runners.Suite.runChild(Suite.java:24) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231) > 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) > 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) -- 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-7079) testCloseRegionWhenEncodedRegionNameIsNotGiven occainlly fails
[ https://issues.apache.org/jira/browse/HBASE-7079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhou wenjian updated HBASE-7079: Attachment: HBASE-7079-trunk-v2.patch > testCloseRegionWhenEncodedRegionNameIsNotGiven occainlly fails > -- > > Key: HBASE-7079 > URL: https://issues.apache.org/jira/browse/HBASE-7079 > Project: HBase > Issue Type: Bug > Components: test >Affects Versions: 0.94.2 >Reporter: Zhou wenjian >Assignee: Zhou wenjian > Attachments: HBASE-7079-trunk.patch, HBASE-7079-trunk-v2.patch > > > Regression > org.apache.hadoop.hbase.client.TestAdmin.testCloseRegionWhenEncodedRegionNameIsNotGiven > Failing for the past 1 build (Since #147 ) > Took 2 ms. > Error Message > -1 > Stacktrace > java.lang.ArrayIndexOutOfBoundsException: -1 > at > java.util.concurrent.CopyOnWriteArrayList.get(CopyOnWriteArrayList.java:343) > at java.util.Collections$UnmodifiableList.get(Collections.java:1154) > at > org.apache.hadoop.hbase.HBaseTestingUtility.getRSForFirstRegionInTable(HBaseTestingUtility.java:1300) > at > org.apache.hadoop.hbase.client.TestAdmin.testCloseRegionWhenEncodedRegionNameIsNotGiven(TestAdmin.java:1454) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at > org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45) > at > org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) > at > org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42) > at > org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20) > at > org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28) > at > org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:30) > at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:47) > at org.junit.rules.RunRules.evaluate(RunRules.java:18) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:263) > at > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:68) > at > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:47) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:60) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:229) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:50) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:222) > at > org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28) > at > org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:30) > at org.junit.runners.ParentRunner.run(ParentRunner.java:300) > at org.junit.runners.Suite.runChild(Suite.java:128) > at org.junit.runners.Suite.runChild(Suite.java:24) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231) > 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) > 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) -- 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-7079) testCloseRegionWhenEncodedRegionNameIsNotGiven occainlly fails
[ https://issues.apache.org/jira/browse/HBASE-7079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhou wenjian updated HBASE-7079: Attachment: HBASE-7079-trunk.patch > testCloseRegionWhenEncodedRegionNameIsNotGiven occainlly fails > -- > > Key: HBASE-7079 > URL: https://issues.apache.org/jira/browse/HBASE-7079 > Project: HBase > Issue Type: Bug > Components: test >Affects Versions: 0.94.2 >Reporter: Zhou wenjian >Assignee: Zhou wenjian > Attachments: HBASE-7079-trunk.patch > > > Regression > org.apache.hadoop.hbase.client.TestAdmin.testCloseRegionWhenEncodedRegionNameIsNotGiven > Failing for the past 1 build (Since #147 ) > Took 2 ms. > Error Message > -1 > Stacktrace > java.lang.ArrayIndexOutOfBoundsException: -1 > at > java.util.concurrent.CopyOnWriteArrayList.get(CopyOnWriteArrayList.java:343) > at java.util.Collections$UnmodifiableList.get(Collections.java:1154) > at > org.apache.hadoop.hbase.HBaseTestingUtility.getRSForFirstRegionInTable(HBaseTestingUtility.java:1300) > at > org.apache.hadoop.hbase.client.TestAdmin.testCloseRegionWhenEncodedRegionNameIsNotGiven(TestAdmin.java:1454) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at > org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45) > at > org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) > at > org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42) > at > org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20) > at > org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28) > at > org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:30) > at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:47) > at org.junit.rules.RunRules.evaluate(RunRules.java:18) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:263) > at > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:68) > at > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:47) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:60) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:229) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:50) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:222) > at > org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28) > at > org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:30) > at org.junit.runners.ParentRunner.run(ParentRunner.java:300) > at org.junit.runners.Suite.runChild(Suite.java:128) > at org.junit.runners.Suite.runChild(Suite.java:24) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231) > 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) > 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) -- 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-7079) testCloseRegionWhenEncodedRegionNameIsNotGiven occainlly fails
[ https://issues.apache.org/jira/browse/HBASE-7079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13487556#comment-13487556 ] Zhou wenjian commented on HBASE-7079: - testCloseRegionWhenEncodedRegionNameIsNotGiven occainlly fails. there is a window between the region adding to meta and online the region in regionserver. during that, the testcase try to get the online region provided, it will return -1, which lead to the case failture. > testCloseRegionWhenEncodedRegionNameIsNotGiven occainlly fails > -- > > Key: HBASE-7079 > URL: https://issues.apache.org/jira/browse/HBASE-7079 > Project: HBase > Issue Type: Bug > Components: test >Affects Versions: 0.94.2 >Reporter: Zhou wenjian >Assignee: Zhou wenjian > > Regression > org.apache.hadoop.hbase.client.TestAdmin.testCloseRegionWhenEncodedRegionNameIsNotGiven > Failing for the past 1 build (Since #147 ) > Took 2 ms. > Error Message > -1 > Stacktrace > java.lang.ArrayIndexOutOfBoundsException: -1 > at > java.util.concurrent.CopyOnWriteArrayList.get(CopyOnWriteArrayList.java:343) > at java.util.Collections$UnmodifiableList.get(Collections.java:1154) > at > org.apache.hadoop.hbase.HBaseTestingUtility.getRSForFirstRegionInTable(HBaseTestingUtility.java:1300) > at > org.apache.hadoop.hbase.client.TestAdmin.testCloseRegionWhenEncodedRegionNameIsNotGiven(TestAdmin.java:1454) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at > org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45) > at > org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) > at > org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42) > at > org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20) > at > org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28) > at > org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:30) > at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:47) > at org.junit.rules.RunRules.evaluate(RunRules.java:18) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:263) > at > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:68) > at > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:47) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:60) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:229) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:50) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:222) > at > org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28) > at > org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:30) > at org.junit.runners.ParentRunner.run(ParentRunner.java:300) > at org.junit.runners.Suite.runChild(Suite.java:128) > at org.junit.runners.Suite.runChild(Suite.java:24) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231) > 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) > 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) -- 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-7079) testCloseRegionWhenEncodedRegionNameIsNotGiven occainlly fails
[ https://issues.apache.org/jira/browse/HBASE-7079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhou wenjian updated HBASE-7079: Description: Regression org.apache.hadoop.hbase.client.TestAdmin.testCloseRegionWhenEncodedRegionNameIsNotGiven Failing for the past 1 build (Since #147 ) Took 2 ms. Error Message -1 Stacktrace java.lang.ArrayIndexOutOfBoundsException: -1 at java.util.concurrent.CopyOnWriteArrayList.get(CopyOnWriteArrayList.java:343) at java.util.Collections$UnmodifiableList.get(Collections.java:1154) at org.apache.hadoop.hbase.HBaseTestingUtility.getRSForFirstRegionInTable(HBaseTestingUtility.java:1300) at org.apache.hadoop.hbase.client.TestAdmin.testCloseRegionWhenEncodedRegionNameIsNotGiven(TestAdmin.java:1454) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42) at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20) at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28) at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:30) at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:47) at org.junit.rules.RunRules.evaluate(RunRules.java:18) at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:263) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:68) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:47) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:60) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:229) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:50) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:222) at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28) at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:30) at org.junit.runners.ParentRunner.run(ParentRunner.java:300) at org.junit.runners.Suite.runChild(Suite.java:128) at org.junit.runners.Suite.runChild(Suite.java:24) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231) 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) 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) was: Regression org.apache.hadoop.hbase.client.TestAdmin.testCloseRegionWhenEncodedRegionNameIsNotGiven Failing for the past 1 build (Since #147 ) Took 2 毫秒. Error Message -1 Stacktrace java.lang.ArrayIndexOutOfBoundsException: -1 at java.util.concurrent.CopyOnWriteArrayList.get(CopyOnWriteArrayList.java:343) at java.util.Collections$UnmodifiableList.get(Collections.java:1154) at org.apache.hadoop.hbase.HBaseTestingUtility.getRSForFirstRegionInTable(HBaseTestingUtility.java:1300) at org.apache.hadoop.hbase.client.TestAdmin.testCloseRegionWhenEncodedRegionNameIsNotGiven(TestAdmin.java:1454) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42) at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20) at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28) at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:30) at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:47) at or
[jira] [Created] (HBASE-7079) testCloseRegionWhenEncodedRegionNameIsNotGiven occainlly fails
Zhou wenjian created HBASE-7079: --- Summary: testCloseRegionWhenEncodedRegionNameIsNotGiven occainlly fails Key: HBASE-7079 URL: https://issues.apache.org/jira/browse/HBASE-7079 Project: HBase Issue Type: Bug Components: test Affects Versions: 0.94.2 Reporter: Zhou wenjian Assignee: Zhou wenjian Regression org.apache.hadoop.hbase.client.TestAdmin.testCloseRegionWhenEncodedRegionNameIsNotGiven Failing for the past 1 build (Since #147 ) Took 2 毫秒. Error Message -1 Stacktrace java.lang.ArrayIndexOutOfBoundsException: -1 at java.util.concurrent.CopyOnWriteArrayList.get(CopyOnWriteArrayList.java:343) at java.util.Collections$UnmodifiableList.get(Collections.java:1154) at org.apache.hadoop.hbase.HBaseTestingUtility.getRSForFirstRegionInTable(HBaseTestingUtility.java:1300) at org.apache.hadoop.hbase.client.TestAdmin.testCloseRegionWhenEncodedRegionNameIsNotGiven(TestAdmin.java:1454) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42) at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20) at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28) at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:30) at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:47) at org.junit.rules.RunRules.evaluate(RunRules.java:18) at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:263) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:68) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:47) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:60) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:229) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:50) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:222) at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28) at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:30) at org.junit.runners.ParentRunner.run(ParentRunner.java:300) at org.junit.runners.Suite.runChild(Suite.java:128) at org.junit.runners.Suite.runChild(Suite.java:24) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231) 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) 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) -- 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-6843) loading lzo error when using coprocessor
[ https://issues.apache.org/jira/browse/HBASE-6843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13459339#comment-13459339 ] Zhou wenjian commented on HBASE-6843: - [~saint@gmail.com] IMO, native-lzo is loaded Repeatedly in different regions opening with cp imported in, that is because of the PREFIX of lzo( com.hadoop.compression.lzo ) is not included in CoprocessorClassLoader.CLASS_PREFIX_EXEMPTIONS > loading lzo error when using coprocessor > > > Key: HBASE-6843 > URL: https://issues.apache.org/jira/browse/HBASE-6843 > Project: HBase > Issue Type: Bug > Components: coprocessors >Affects Versions: 0.94.1 >Reporter: Zhou wenjian >Assignee: Zhou wenjian >Priority: Critical > Fix For: 0.96.0, 0.94.3 > > Attachments: HBASE-6843-trunk.patch > > > After applying HBASE-6308,we found error followed > 2012-09-06 00:44:38,341 DEBUG > org.apache.hadoop.hbase.coprocessor.CoprocessorClassLoader: Finding class: > com.hadoop.compression.lzo.LzoCodec > 2012-09-06 00:44:38,351 ERROR com.hadoop.compression.lzo.GPLNativeCodeLoader: > Could not load native gpl library > java.lang.UnsatisfiedLinkError: Native Library > /home/zhuzhuang/hbase/0.94.0-ali-1.0/lib/native/Linux-amd64-64/libgplcompression.so > already loaded in another classloade > r > at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1772) > at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1732) > at java.lang.Runtime.loadLibrary0(Runtime.java:823) > at java.lang.System.loadLibrary(System.java:1028) > at > com.hadoop.compression.lzo.GPLNativeCodeLoader.(GPLNativeCodeLoader.java:32) > at com.hadoop.compression.lzo.LzoCodec.(LzoCodec.java:67) > 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.util.ReflectionUtils.newInstance(ReflectionUtils.java:113) > at > org.apache.hadoop.hbase.io.hfile.Compression$Algorithm$1.getCodec(Compression.java:107) > at > org.apache.hadoop.hbase.io.hfile.Compression$Algorithm.getCompressor(Compression.java:243) > at > org.apache.hadoop.hbase.util.CompressionTest.testCompression(CompressionTest.java:85) > at > org.apache.hadoop.hbase.regionserver.HRegion.checkCompressionCodecs(HRegion.java:3793) > at org.apache.hadoop.hbase.regionserver.HRegion.openHRegion(HRegion.java:3782) > at org.apache.hadoop.hbase.regionserver.HRegion.openHRegion(HRegion.java:3732) > at > org.apache.hadoop.hbase.regionserver.handler.OpenRegionHandler.openRegion(OpenRegionHandler.java:332) > at > org.apache.hadoop.hbase.regionserver.handler.OpenRegionHandler.process(OpenRegionHandler.java:108) > at org.apache.hadoop.hbase.executor.EventHandler.run(EventHandler.java:169) > at > java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) > at java.lang.Thread.run(Thread.java:662) > 2012-09-06 00:44:38,355 DEBUG > org.apache.hadoop.hbase.coprocessor.CoprocessorClassLoader: Skipping exempt > class java.io.PrintWriter - delegating directly to parent > 2012-09-06 00:44:38,355 ERROR com.hadoop.compression.lzo.LzoCodec: Cannot > load native-lzo without native-hadoop -- 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-6842) the jar used in coprocessor is not deleted in local which will exhaust the space of /tmp
[
https://issues.apache.org/jira/browse/HBASE-6842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13459338#comment-13459338
]
Zhou wenjian commented on HBASE-6842:
-
@stack
in our cluster,it does work. the jar in /tmp will be deleted when the jvm exits.
IMO, fs.deleteOnExit means to delete the file in hdfs rather than delete it in
local fs.
> the jar used in coprocessor is not deleted in local which will exhaust the
> space of /tmp
> ---
>
> Key: HBASE-6842
> URL: https://issues.apache.org/jira/browse/HBASE-6842
> Project: HBase
> Issue Type: Bug
> Components: coprocessors
>Affects Versions: 0.94.1
>Reporter: Zhou wenjian
>Assignee: Zhou wenjian
>Priority: Critical
> Fix For: 0.96.0, 0.94.3
>
> Attachments: HBASE-6842-trunk.patch
>
>
> FileSystem fs = path.getFileSystem(HBaseConfiguration.create());
> Path dst = new Path(System.getProperty("java.io.tmpdir") +
> java.io.File.separator +"." + pathPrefix +
> "." + className + "." + System.currentTimeMillis() + ".jar");
> fs.copyToLocalFile(path, dst);
> fs.deleteOnExit(dst);
> change to
> File tmpLocal = new File(dst.toString());
> tmpLocal.deleteOnExit();
>
--
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-6843) loading lzo error when using coprocessor
[ https://issues.apache.org/jira/browse/HBASE-6843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhou wenjian updated HBASE-6843: Attachment: HBASE-6843-trunk.patch > loading lzo error when using coprocessor > > > Key: HBASE-6843 > URL: https://issues.apache.org/jira/browse/HBASE-6843 > Project: HBase > Issue Type: Bug > Components: coprocessors >Affects Versions: 0.94.1 >Reporter: Zhou wenjian >Assignee: Zhou wenjian >Priority: Critical > Fix For: 0.96.0, 0.94.3 > > Attachments: HBASE-6843-trunk.patch > > > After applying HBASE-6308,we found error followed > 2012-09-06 00:44:38,341 DEBUG > org.apache.hadoop.hbase.coprocessor.CoprocessorClassLoader: Finding class: > com.hadoop.compression.lzo.LzoCodec > 2012-09-06 00:44:38,351 ERROR com.hadoop.compression.lzo.GPLNativeCodeLoader: > Could not load native gpl library > java.lang.UnsatisfiedLinkError: Native Library > /home/zhuzhuang/hbase/0.94.0-ali-1.0/lib/native/Linux-amd64-64/libgplcompression.so > already loaded in another classloade > r > at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1772) > at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1732) > at java.lang.Runtime.loadLibrary0(Runtime.java:823) > at java.lang.System.loadLibrary(System.java:1028) > at > com.hadoop.compression.lzo.GPLNativeCodeLoader.(GPLNativeCodeLoader.java:32) > at com.hadoop.compression.lzo.LzoCodec.(LzoCodec.java:67) > 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.util.ReflectionUtils.newInstance(ReflectionUtils.java:113) > at > org.apache.hadoop.hbase.io.hfile.Compression$Algorithm$1.getCodec(Compression.java:107) > at > org.apache.hadoop.hbase.io.hfile.Compression$Algorithm.getCompressor(Compression.java:243) > at > org.apache.hadoop.hbase.util.CompressionTest.testCompression(CompressionTest.java:85) > at > org.apache.hadoop.hbase.regionserver.HRegion.checkCompressionCodecs(HRegion.java:3793) > at org.apache.hadoop.hbase.regionserver.HRegion.openHRegion(HRegion.java:3782) > at org.apache.hadoop.hbase.regionserver.HRegion.openHRegion(HRegion.java:3732) > at > org.apache.hadoop.hbase.regionserver.handler.OpenRegionHandler.openRegion(OpenRegionHandler.java:332) > at > org.apache.hadoop.hbase.regionserver.handler.OpenRegionHandler.process(OpenRegionHandler.java:108) > at org.apache.hadoop.hbase.executor.EventHandler.run(EventHandler.java:169) > at > java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) > at java.lang.Thread.run(Thread.java:662) > 2012-09-06 00:44:38,355 DEBUG > org.apache.hadoop.hbase.coprocessor.CoprocessorClassLoader: Skipping exempt > class java.io.PrintWriter - delegating directly to parent > 2012-09-06 00:44:38,355 ERROR com.hadoop.compression.lzo.LzoCodec: Cannot > load native-lzo without native-hadoop -- 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-6842) the jar used in coprocessor is not deleted in local which will exhaust the space of /tmp
[
https://issues.apache.org/jira/browse/HBASE-6842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhou wenjian updated HBASE-6842:
Attachment: HBASE-6842-trunk.patch
> the jar used in coprocessor is not deleted in local which will exhaust the
> space of /tmp
> ---
>
> Key: HBASE-6842
> URL: https://issues.apache.org/jira/browse/HBASE-6842
> Project: HBase
> Issue Type: Bug
> Components: coprocessors
>Affects Versions: 0.94.1
>Reporter: Zhou wenjian
>Assignee: Zhou wenjian
>Priority: Critical
> Fix For: 0.96.0, 0.94.3
>
> Attachments: HBASE-6842-trunk.patch
>
>
> FileSystem fs = path.getFileSystem(HBaseConfiguration.create());
> Path dst = new Path(System.getProperty("java.io.tmpdir") +
> java.io.File.separator +"." + pathPrefix +
> "." + className + "." + System.currentTimeMillis() + ".jar");
> fs.copyToLocalFile(path, dst);
> fs.deleteOnExit(dst);
> change to
> File tmpLocal = new File(dst.toString());
> tmpLocal.deleteOnExit();
>
--
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-6842) the jar used in coprocessor is not deleted in local which will exhaust the space of /tmp
[
https://issues.apache.org/jira/browse/HBASE-6842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhou wenjian updated HBASE-6842:
Attachment: (was: HBASE-6842-trunk.patch)
> the jar used in coprocessor is not deleted in local which will exhaust the
> space of /tmp
> ---
>
> Key: HBASE-6842
> URL: https://issues.apache.org/jira/browse/HBASE-6842
> Project: HBase
> Issue Type: Bug
> Components: coprocessors
>Affects Versions: 0.94.1
>Reporter: Zhou wenjian
>Assignee: Zhou wenjian
>Priority: Critical
> Fix For: 0.96.0, 0.94.3
>
>
> FileSystem fs = path.getFileSystem(HBaseConfiguration.create());
> Path dst = new Path(System.getProperty("java.io.tmpdir") +
> java.io.File.separator +"." + pathPrefix +
> "." + className + "." + System.currentTimeMillis() + ".jar");
> fs.copyToLocalFile(path, dst);
> fs.deleteOnExit(dst);
> change to
> File tmpLocal = new File(dst.toString());
> tmpLocal.deleteOnExit();
>
--
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-6842) the jar used in coprocessor is not deleted in local which will exhaust the space of /tmp
[
https://issues.apache.org/jira/browse/HBASE-6842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhou wenjian updated HBASE-6842:
Attachment: HBASE-6842-trunk.patch
> the jar used in coprocessor is not deleted in local which will exhaust the
> space of /tmp
> ---
>
> Key: HBASE-6842
> URL: https://issues.apache.org/jira/browse/HBASE-6842
> Project: HBase
> Issue Type: Bug
> Components: coprocessors
>Affects Versions: 0.94.1
>Reporter: Zhou wenjian
>Assignee: Zhou wenjian
>Priority: Critical
> Fix For: 0.96.0, 0.94.3
>
>
> FileSystem fs = path.getFileSystem(HBaseConfiguration.create());
> Path dst = new Path(System.getProperty("java.io.tmpdir") +
> java.io.File.separator +"." + pathPrefix +
> "." + className + "." + System.currentTimeMillis() + ".jar");
> fs.copyToLocalFile(path, dst);
> fs.deleteOnExit(dst);
> change to
> File tmpLocal = new File(dst.toString());
> tmpLocal.deleteOnExit();
>
--
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-6843) loading lzo error when using coprocessor
[ https://issues.apache.org/jira/browse/HBASE-6843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13459315#comment-13459315 ] Zhou wenjian commented on HBASE-6843: - i think we should include the com.hadoop in CoprocessorClassLoader.CLASS_PREFIX_EXEMPTIONS ,to avoid the lzo loaed twice. > loading lzo error when using coprocessor > > > Key: HBASE-6843 > URL: https://issues.apache.org/jira/browse/HBASE-6843 > Project: HBase > Issue Type: Bug > Components: coprocessors >Affects Versions: 0.94.1 >Reporter: Zhou wenjian >Assignee: Zhou wenjian >Priority: Critical > Fix For: 0.96.0, 0.94.3 > > > After applying HBASE-6308,we found error followed > 2012-09-06 00:44:38,341 DEBUG > org.apache.hadoop.hbase.coprocessor.CoprocessorClassLoader: Finding class: > com.hadoop.compression.lzo.LzoCodec > 2012-09-06 00:44:38,351 ERROR com.hadoop.compression.lzo.GPLNativeCodeLoader: > Could not load native gpl library > java.lang.UnsatisfiedLinkError: Native Library > /home/zhuzhuang/hbase/0.94.0-ali-1.0/lib/native/Linux-amd64-64/libgplcompression.so > already loaded in another classloade > r > at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1772) > at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1732) > at java.lang.Runtime.loadLibrary0(Runtime.java:823) > at java.lang.System.loadLibrary(System.java:1028) > at > com.hadoop.compression.lzo.GPLNativeCodeLoader.(GPLNativeCodeLoader.java:32) > at com.hadoop.compression.lzo.LzoCodec.(LzoCodec.java:67) > 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.util.ReflectionUtils.newInstance(ReflectionUtils.java:113) > at > org.apache.hadoop.hbase.io.hfile.Compression$Algorithm$1.getCodec(Compression.java:107) > at > org.apache.hadoop.hbase.io.hfile.Compression$Algorithm.getCompressor(Compression.java:243) > at > org.apache.hadoop.hbase.util.CompressionTest.testCompression(CompressionTest.java:85) > at > org.apache.hadoop.hbase.regionserver.HRegion.checkCompressionCodecs(HRegion.java:3793) > at org.apache.hadoop.hbase.regionserver.HRegion.openHRegion(HRegion.java:3782) > at org.apache.hadoop.hbase.regionserver.HRegion.openHRegion(HRegion.java:3732) > at > org.apache.hadoop.hbase.regionserver.handler.OpenRegionHandler.openRegion(OpenRegionHandler.java:332) > at > org.apache.hadoop.hbase.regionserver.handler.OpenRegionHandler.process(OpenRegionHandler.java:108) > at org.apache.hadoop.hbase.executor.EventHandler.run(EventHandler.java:169) > at > java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) > at java.lang.Thread.run(Thread.java:662) > 2012-09-06 00:44:38,355 DEBUG > org.apache.hadoop.hbase.coprocessor.CoprocessorClassLoader: Skipping exempt > class java.io.PrintWriter - delegating directly to parent > 2012-09-06 00:44:38,355 ERROR com.hadoop.compression.lzo.LzoCodec: Cannot > load native-lzo without native-hadoop -- 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-6843) loading lzo error when using coprocessor
Zhou wenjian created HBASE-6843: --- Summary: loading lzo error when using coprocessor Key: HBASE-6843 URL: https://issues.apache.org/jira/browse/HBASE-6843 Project: HBase Issue Type: Bug Components: coprocessors Affects Versions: 0.94.1 Reporter: Zhou wenjian Assignee: Zhou wenjian Priority: Critical Fix For: 0.96.0, 0.94.3 After applying HBASE-6308,we found error followed 2012-09-06 00:44:38,341 DEBUG org.apache.hadoop.hbase.coprocessor.CoprocessorClassLoader: Finding class: com.hadoop.compression.lzo.LzoCodec 2012-09-06 00:44:38,351 ERROR com.hadoop.compression.lzo.GPLNativeCodeLoader: Could not load native gpl library java.lang.UnsatisfiedLinkError: Native Library /home/zhuzhuang/hbase/0.94.0-ali-1.0/lib/native/Linux-amd64-64/libgplcompression.so already loaded in another classloade r at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1772) at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1732) at java.lang.Runtime.loadLibrary0(Runtime.java:823) at java.lang.System.loadLibrary(System.java:1028) at com.hadoop.compression.lzo.GPLNativeCodeLoader.(GPLNativeCodeLoader.java:32) at com.hadoop.compression.lzo.LzoCodec.(LzoCodec.java:67) 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.util.ReflectionUtils.newInstance(ReflectionUtils.java:113) at org.apache.hadoop.hbase.io.hfile.Compression$Algorithm$1.getCodec(Compression.java:107) at org.apache.hadoop.hbase.io.hfile.Compression$Algorithm.getCompressor(Compression.java:243) at org.apache.hadoop.hbase.util.CompressionTest.testCompression(CompressionTest.java:85) at org.apache.hadoop.hbase.regionserver.HRegion.checkCompressionCodecs(HRegion.java:3793) at org.apache.hadoop.hbase.regionserver.HRegion.openHRegion(HRegion.java:3782) at org.apache.hadoop.hbase.regionserver.HRegion.openHRegion(HRegion.java:3732) at org.apache.hadoop.hbase.regionserver.handler.OpenRegionHandler.openRegion(OpenRegionHandler.java:332) at org.apache.hadoop.hbase.regionserver.handler.OpenRegionHandler.process(OpenRegionHandler.java:108) at org.apache.hadoop.hbase.executor.EventHandler.run(EventHandler.java:169) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) 2012-09-06 00:44:38,355 DEBUG org.apache.hadoop.hbase.coprocessor.CoprocessorClassLoader: Skipping exempt class java.io.PrintWriter - delegating directly to parent 2012-09-06 00:44:38,355 ERROR com.hadoop.compression.lzo.LzoCodec: Cannot load native-lzo without native-hadoop -- 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-6842) the jar used in coprocessor is not deleted in local which will exhaust the space of /tmp
Zhou wenjian created HBASE-6842:
---
Summary: the jar used in coprocessor is not deleted in local
which will exhaust the space of /tmp
Key: HBASE-6842
URL: https://issues.apache.org/jira/browse/HBASE-6842
Project: HBase
Issue Type: Bug
Components: coprocessors
Affects Versions: 0.94.1
Reporter: Zhou wenjian
Assignee: Zhou wenjian
Priority: Critical
Fix For: 0.96.0, 0.94.3
FileSystem fs = path.getFileSystem(HBaseConfiguration.create());
Path dst = new Path(System.getProperty("java.io.tmpdir") +
java.io.File.separator +"." + pathPrefix +
"." + className + "." + System.currentTimeMillis() + ".jar");
fs.copyToLocalFile(path, dst);
fs.deleteOnExit(dst);
change to
File tmpLocal = new File(dst.toString());
tmpLocal.deleteOnExit();
--
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-6473) deleted table is not deleted completely, some region may be still online
[
https://issues.apache.org/jira/browse/HBASE-6473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13445673#comment-13445673
]
zhou wenjian commented on HBASE-6473:
-
@Lars,could you help me to pick out what happened in trunk.
through https://builds.apache.org/job/PreCommit-HBASE-Build/2601//testReport/
the error in TestAssignmentManager is Address already in use, so i suppose
there is nothing with my patch, what caused you fails in trunk. thanks.
> deleted table is not deleted completely, some region may be still online
>
>
> Key: HBASE-6473
> URL: https://issues.apache.org/jira/browse/HBASE-6473
> Project: HBase
> Issue Type: Bug
>Affects Versions: 0.94.0
>Reporter: zhou wenjian
>Assignee: Zhou wenjian
> Fix For: 0.96.0, 0.94.2
>
> Attachments: HBASE-6473-trunk.patch, HBASE-6473-trunk-v2.patch,
> HBASE-6473-trunk-v3.patch, HBASE-6473-trunk-v4.patch
>
>
> consider such Scenario:
> we have a table called T1, which has 1 regions: A
> 1. move A from rs1 to rs2,and A is now closed
> 2. disable T1,
> 3. delete T1.
> when we disable T1, disable handler will just set the zk to disabled and A
> will still be assigned. when Ais opened, A in transition will be clean out.
> At that time, Deletetable found it is safe to delete all regions and table in
> meta and fs , it will also delete the zk node of T1.
> {code}
> while (System.currentTimeMillis() < done) {
> AssignmentManager.RegionState rs = am.isRegionInTransition(region);
> if (rs == null) break;
> Threads.sleep(waitingTimeForEvents);
> LOG.debug("Waiting on region to clear regions in transition; " + rs);
> }
> if (am.isRegionInTransition(region) != null) {
> throw new IOException("Waited hbase.master.wait.on.region (" +
> waitTime + "ms) for region to leave region " +
> region.getRegionNameAsString() + " in transitions");
> }
> {code}
> however A is still being unassigned, when it finished closed the A,it finds
> that the disabled state in zk is deleted, and then A will be assigned again.
--
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-6473) deleted table is not deleted completely, some region may be still online
[
https://issues.apache.org/jira/browse/HBASE-6473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13445621#comment-13445621
]
zhou wenjian commented on HBASE-6473:
-
i have tried the patch in 94, there is no problem.
> deleted table is not deleted completely, some region may be still online
>
>
> Key: HBASE-6473
> URL: https://issues.apache.org/jira/browse/HBASE-6473
> Project: HBase
> Issue Type: Bug
>Affects Versions: 0.94.0
>Reporter: zhou wenjian
>Assignee: Zhou wenjian
> Fix For: 0.96.0, 0.94.2
>
> Attachments: HBASE-6473-trunk.patch, HBASE-6473-trunk-v2.patch,
> HBASE-6473-trunk-v3.patch, HBASE-6473-trunk-v4.patch
>
>
> consider such Scenario:
> we have a table called T1, which has 1 regions: A
> 1. move A from rs1 to rs2,and A is now closed
> 2. disable T1,
> 3. delete T1.
> when we disable T1, disable handler will just set the zk to disabled and A
> will still be assigned. when Ais opened, A in transition will be clean out.
> At that time, Deletetable found it is safe to delete all regions and table in
> meta and fs , it will also delete the zk node of T1.
> {code}
> while (System.currentTimeMillis() < done) {
> AssignmentManager.RegionState rs = am.isRegionInTransition(region);
> if (rs == null) break;
> Threads.sleep(waitingTimeForEvents);
> LOG.debug("Waiting on region to clear regions in transition; " + rs);
> }
> if (am.isRegionInTransition(region) != null) {
> throw new IOException("Waited hbase.master.wait.on.region (" +
> waitTime + "ms) for region to leave region " +
> region.getRegionNameAsString() + " in transitions");
> }
> {code}
> however A is still being unassigned, when it finished closed the A,it finds
> that the disabled state in zk is deleted, and then A will be assigned again.
--
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-6473) deleted table is not deleted completely, some region may be still online
[
https://issues.apache.org/jira/browse/HBASE-6473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13445594#comment-13445594
]
zhou wenjian commented on HBASE-6473:
-
@Lars, i have got the patch for 94.
but since test for trunk is not passed (i do not know why, they are nothing
with my case..)
> deleted table is not deleted completely, some region may be still online
>
>
> Key: HBASE-6473
> URL: https://issues.apache.org/jira/browse/HBASE-6473
> Project: HBase
> Issue Type: Bug
>Affects Versions: 0.94.0
>Reporter: zhou wenjian
>Assignee: Zhou wenjian
> Fix For: 0.96.0, 0.94.2
>
> Attachments: HBASE-6473-trunk.patch, HBASE-6473-trunk-v2.patch,
> HBASE-6473-trunk-v3.patch, HBASE-6473-trunk-v4.patch
>
>
> consider such Scenario:
> we have a table called T1, which has 1 regions: A
> 1. move A from rs1 to rs2,and A is now closed
> 2. disable T1,
> 3. delete T1.
> when we disable T1, disable handler will just set the zk to disabled and A
> will still be assigned. when Ais opened, A in transition will be clean out.
> At that time, Deletetable found it is safe to delete all regions and table in
> meta and fs , it will also delete the zk node of T1.
> {code}
> while (System.currentTimeMillis() < done) {
> AssignmentManager.RegionState rs = am.isRegionInTransition(region);
> if (rs == null) break;
> Threads.sleep(waitingTimeForEvents);
> LOG.debug("Waiting on region to clear regions in transition; " + rs);
> }
> if (am.isRegionInTransition(region) != null) {
> throw new IOException("Waited hbase.master.wait.on.region (" +
> waitTime + "ms) for region to leave region " +
> region.getRegionNameAsString() + " in transitions");
> }
> {code}
> however A is still being unassigned, when it finished closed the A,it finds
> that the disabled state in zk is deleted, and then A will be assigned again.
--
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-6537) Balancer compete with disable table will lead to cluster inconsistent
[ https://issues.apache.org/jira/browse/HBASE-6537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13445591#comment-13445591 ] zhou wenjian commented on HBASE-6537: - @Lars,thanks for reply. update patch for 94 > Balancer compete with disable table will lead to cluster inconsistent > -- > > Key: HBASE-6537 > URL: https://issues.apache.org/jira/browse/HBASE-6537 > Project: HBase > Issue Type: Bug > Components: master >Affects Versions: 0.94.0 >Reporter: Zhou wenjian >Assignee: Zhou wenjian > Fix For: 0.94.2 > > Attachments: HBASE-6537-94-v2.patch, HBASE-6537-trunk.patch, > HBASE-6537-trunk-v2.patch > > > Appear in 94. trunk is ok for the issue > Balancer will collect the regionplans to move(unassign and then assign). > before unassign, disable table appears, > after close the region in rs, master will delete the znode, romove region > from RIT, > and then clean the region from the online regions. > During romoving region from RIT and cleaning out the region from the online > regions. > balancer begins to unassign, it will get a NotServingRegionException and if > the table is disabling, it will deal with the state in master and delete the > znode . However the table is disabled now, so the RIT and znode will remain. > TimeoutMonitor draws a blank on it. > It will hold back enabling the table or balancer unless restart -- 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-6537) Balancer compete with disable table will lead to cluster inconsistent
[ https://issues.apache.org/jira/browse/HBASE-6537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhou wenjian updated HBASE-6537: Attachment: HBASE-6537-94-v2.patch > Balancer compete with disable table will lead to cluster inconsistent > -- > > Key: HBASE-6537 > URL: https://issues.apache.org/jira/browse/HBASE-6537 > Project: HBase > Issue Type: Bug > Components: master >Affects Versions: 0.94.0 >Reporter: Zhou wenjian >Assignee: Zhou wenjian > Fix For: 0.94.2 > > Attachments: HBASE-6537-94-v2.patch, HBASE-6537-trunk.patch, > HBASE-6537-trunk-v2.patch > > > Appear in 94. trunk is ok for the issue > Balancer will collect the regionplans to move(unassign and then assign). > before unassign, disable table appears, > after close the region in rs, master will delete the znode, romove region > from RIT, > and then clean the region from the online regions. > During romoving region from RIT and cleaning out the region from the online > regions. > balancer begins to unassign, it will get a NotServingRegionException and if > the table is disabling, it will deal with the state in master and delete the > znode . However the table is disabled now, so the RIT and znode will remain. > TimeoutMonitor draws a blank on it. > It will hold back enabling the table or balancer unless restart -- 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-6668) disable in shell may make confused to user
[ https://issues.apache.org/jira/browse/HBASE-6668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13443027#comment-13443027 ] Zhou wenjian commented on HBASE-6668: - @Lars fonud in 94, did not check other versions > disable in shell may make confused to user > --- > > Key: HBASE-6668 > URL: https://issues.apache.org/jira/browse/HBASE-6668 > Project: HBase > Issue Type: Bug > Components: shell >Affects Versions: 0.94.1 >Reporter: Zhou wenjian >Assignee: Zhou wenjian > Fix For: 0.94.2 > > > hbase(main):002:0> disable 'logTable' > 0 row(s) in 2.0910 seconds > hbase(main):003:0> disable 'logTable' > 0 row(s) in 0.0260 seconds > and we can found table are disabled in log when disable first appears > but when i disable it again the client just return seemed to be sucessful and > I can not find any log described it in the log. > look into the admin.rb, find below > > #-- > # Disables a table > def disable(table_name) > tableExists(table_name) > return if disabled?(table_name) > @admin.disableTable(table_name) > end > that would confuse us when we found it disabled already but returns nothing -- 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-6668) disable in shell may make confused to user
[ https://issues.apache.org/jira/browse/HBASE-6668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13443025#comment-13443025 ] Zhou wenjian commented on HBASE-6668: - [~lhofhansl] if the table is already disabled, when we disabled it again , it needs to be given some message in shell such as table is disabled already rather than return nothing > disable in shell may make confused to user > --- > > Key: HBASE-6668 > URL: https://issues.apache.org/jira/browse/HBASE-6668 > Project: HBase > Issue Type: Bug > Components: shell >Affects Versions: 0.94.1 >Reporter: Zhou wenjian >Assignee: Zhou wenjian > Fix For: 0.94.2 > > > hbase(main):002:0> disable 'logTable' > 0 row(s) in 2.0910 seconds > hbase(main):003:0> disable 'logTable' > 0 row(s) in 0.0260 seconds > and we can found table are disabled in log when disable first appears > but when i disable it again the client just return seemed to be sucessful and > I can not find any log described it in the log. > look into the admin.rb, find below > > #-- > # Disables a table > def disable(table_name) > tableExists(table_name) > return if disabled?(table_name) > @admin.disableTable(table_name) > end > that would confuse us when we found it disabled already but returns nothing -- 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-6668) disable in shell may make confused to user
[ https://issues.apache.org/jira/browse/HBASE-6668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13442259#comment-13442259 ] Zhou wenjian commented on HBASE-6668: - also appears in enable twice hbase(main):001:0> enable 'logTable' 0 row(s) in 1.4390 seconds hbase(main):002:0> enable 'logTable' 0 row(s) in 0.0150 seconds > disable in shell may make confused to user > --- > > Key: HBASE-6668 > URL: https://issues.apache.org/jira/browse/HBASE-6668 > Project: HBase > Issue Type: Bug > Components: shell >Affects Versions: 0.94.1 >Reporter: Zhou wenjian >Assignee: Zhou wenjian > Fix For: 0.94.2 > > > hbase(main):002:0> disable 'logTable' > 0 row(s) in 2.0910 seconds > hbase(main):003:0> disable 'logTable' > 0 row(s) in 0.0260 seconds > and we can found table are disabled in log when disable first appears > but when i disable it again the client just return seemed to be sucessful and > I can not find any log described it in the log. > look into the admin.rb, find below > > #-- > # Disables a table > def disable(table_name) > tableExists(table_name) > return if disabled?(table_name) > @admin.disableTable(table_name) > end > that would confuse us when we found it disabled already but returns nothing -- 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-6668) disable in shell may make confused to user
Zhou wenjian created HBASE-6668: --- Summary: disable in shell may make confused to user Key: HBASE-6668 URL: https://issues.apache.org/jira/browse/HBASE-6668 Project: HBase Issue Type: Bug Components: shell Affects Versions: 0.94.1 Reporter: Zhou wenjian Assignee: Zhou wenjian Fix For: 0.94.2 hbase(main):002:0> disable 'logTable' 0 row(s) in 2.0910 seconds hbase(main):003:0> disable 'logTable' 0 row(s) in 0.0260 seconds and we can found table are disabled in log when disable first appears but when i disable it again the client just return seemed to be sucessful and I can not find any log described it in the log. look into the admin.rb, find below #-- # Disables a table def disable(table_name) tableExists(table_name) return if disabled?(table_name) @admin.disableTable(table_name) end that would confuse us when we found it disabled already but returns nothing -- 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-6537) Balancer compete with disable table will lead to cluster inconsistent
[ https://issues.apache.org/jira/browse/HBASE-6537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13442254#comment-13442254 ] Zhou wenjian commented on HBASE-6537: - @Lars & rajeshbabu. i found it unavailable to run hudson, i do not know why, so i just delete the 94 attach. I'll resubmit it if nesscery > Balancer compete with disable table will lead to cluster inconsistent > -- > > Key: HBASE-6537 > URL: https://issues.apache.org/jira/browse/HBASE-6537 > Project: HBase > Issue Type: Bug > Components: master >Affects Versions: 0.94.0 >Reporter: Zhou wenjian >Assignee: Zhou wenjian > Fix For: 0.94.2 > > Attachments: HBASE-6537-trunk.patch, HBASE-6537-trunk-v2.patch > > > Appear in 94. trunk is ok for the issue > Balancer will collect the regionplans to move(unassign and then assign). > before unassign, disable table appears, > after close the region in rs, master will delete the znode, romove region > from RIT, > and then clean the region from the online regions. > During romoving region from RIT and cleaning out the region from the online > regions. > balancer begins to unassign, it will get a NotServingRegionException and if > the table is disabling, it will deal with the state in master and delete the > znode . However the table is disabled now, so the RIT and znode will remain. > TimeoutMonitor draws a blank on it. > It will hold back enabling the table or balancer unless restart -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (HBASE-6563) s.isMajorCompaction() throws npe will cause current major Compaction checking abort
[ https://issues.apache.org/jira/browse/HBASE-6563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhou wenjian reassigned HBASE-6563: --- Assignee: Zhou wenjian > s.isMajorCompaction() throws npe will cause current major Compaction checking > abort > --- > > Key: HBASE-6563 > URL: https://issues.apache.org/jira/browse/HBASE-6563 > Project: HBase > Issue Type: Bug > Components: regionserver >Reporter: Zhou wenjian >Assignee: Zhou wenjian > Fix For: 0.94.1 > > Attachments: HBASE-6563-trunk.patch, HBASE-6563-trunk-v2.patch, > HBASE-6563-trunk-v3.patch > > > 2012-05-05 00:49:43,265 ERROR > org.apache.hadoop.hbase.regionserver.HRegionServer$MajorCompactionChecker: > Caught exception > java.lang.NullPointerException > at > org.apache.hadoop.hbase.regionserver.Store.isMajorCompaction(Store.java:938) > at > org.apache.hadoop.hbase.regionserver.Store.isMajorCompaction(Store.java:917) > at > org.apache.hadoop.hbase.regionserver.HRegion.isMajorCompaction(HRegion.java:3250) > at > org.apache.hadoop.hbase.regionserver.HRegionServer$MajorCompactionChecker.chore(HRegionServer.java:1222) > at org.apache.hadoop.hbase.Chore.run(Chore.java:66) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-6563) s.isMajorCompaction() throws npe will cause current major Compaction checking abort
[ https://issues.apache.org/jira/browse/HBASE-6563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhou wenjian updated HBASE-6563: Attachment: HBASE-6563-trunk-v3.patch > s.isMajorCompaction() throws npe will cause current major Compaction checking > abort > --- > > Key: HBASE-6563 > URL: https://issues.apache.org/jira/browse/HBASE-6563 > Project: HBase > Issue Type: Bug > Components: regionserver >Reporter: Zhou wenjian >Assignee: Zhou wenjian > Fix For: 0.94.1 > > Attachments: HBASE-6563-trunk.patch, HBASE-6563-trunk-v2.patch, > HBASE-6563-trunk-v3.patch > > > 2012-05-05 00:49:43,265 ERROR > org.apache.hadoop.hbase.regionserver.HRegionServer$MajorCompactionChecker: > Caught exception > java.lang.NullPointerException > at > org.apache.hadoop.hbase.regionserver.Store.isMajorCompaction(Store.java:938) > at > org.apache.hadoop.hbase.regionserver.Store.isMajorCompaction(Store.java:917) > at > org.apache.hadoop.hbase.regionserver.HRegion.isMajorCompaction(HRegion.java:3250) > at > org.apache.hadoop.hbase.regionserver.HRegionServer$MajorCompactionChecker.chore(HRegionServer.java:1222) > at org.apache.hadoop.hbase.Chore.run(Chore.java:66) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-6537) Balancer compete with disable table will lead to cluster inconsistent
[ https://issues.apache.org/jira/browse/HBASE-6537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhou wenjian updated HBASE-6537: Attachment: HBASE-6537-trunk-v2.patch > Balancer compete with disable table will lead to cluster inconsistent > -- > > Key: HBASE-6537 > URL: https://issues.apache.org/jira/browse/HBASE-6537 > Project: HBase > Issue Type: Bug > Components: master >Affects Versions: 0.94.0 >Reporter: Zhou wenjian >Assignee: Zhou wenjian > Fix For: 0.94.2 > > Attachments: HBASE-6537-trunk.patch, HBASE-6537-trunk-v2.patch > > > Appear in 94. trunk is ok for the issue > Balancer will collect the regionplans to move(unassign and then assign). > before unassign, disable table appears, > after close the region in rs, master will delete the znode, romove region > from RIT, > and then clean the region from the online regions. > During romoving region from RIT and cleaning out the region from the online > regions. > balancer begins to unassign, it will get a NotServingRegionException and if > the table is disabling, it will deal with the state in master and delete the > znode . However the table is disabled now, so the RIT and znode will remain. > TimeoutMonitor draws a blank on it. > It will hold back enabling the table or balancer unless restart -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-6537) Balancer compete with disable table will lead to cluster inconsistent
[ https://issues.apache.org/jira/browse/HBASE-6537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhou wenjian updated HBASE-6537: Attachment: (was: HBASE-6537-94-v2.patch) > Balancer compete with disable table will lead to cluster inconsistent > -- > > Key: HBASE-6537 > URL: https://issues.apache.org/jira/browse/HBASE-6537 > Project: HBase > Issue Type: Bug > Components: master >Affects Versions: 0.94.0 >Reporter: Zhou wenjian >Assignee: Zhou wenjian > Fix For: 0.94.2 > > Attachments: HBASE-6537-trunk.patch > > > Appear in 94. trunk is ok for the issue > Balancer will collect the regionplans to move(unassign and then assign). > before unassign, disable table appears, > after close the region in rs, master will delete the znode, romove region > from RIT, > and then clean the region from the online regions. > During romoving region from RIT and cleaning out the region from the online > regions. > balancer begins to unassign, it will get a NotServingRegionException and if > the table is disabling, it will deal with the state in master and delete the > znode . However the table is disabled now, so the RIT and znode will remain. > TimeoutMonitor draws a blank on it. > It will hold back enabling the table or balancer unless restart -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-6537) Balancer compete with disable table will lead to cluster inconsistent
[ https://issues.apache.org/jira/browse/HBASE-6537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhou wenjian updated HBASE-6537: Attachment: (was: HBASE-6537-94.patch) > Balancer compete with disable table will lead to cluster inconsistent > -- > > Key: HBASE-6537 > URL: https://issues.apache.org/jira/browse/HBASE-6537 > Project: HBase > Issue Type: Bug > Components: master >Affects Versions: 0.94.0 >Reporter: Zhou wenjian >Assignee: Zhou wenjian > Fix For: 0.94.2 > > Attachments: HBASE-6537-trunk.patch > > > Appear in 94. trunk is ok for the issue > Balancer will collect the regionplans to move(unassign and then assign). > before unassign, disable table appears, > after close the region in rs, master will delete the znode, romove region > from RIT, > and then clean the region from the online regions. > During romoving region from RIT and cleaning out the region from the online > regions. > balancer begins to unassign, it will get a NotServingRegionException and if > the table is disabling, it will deal with the state in master and delete the > znode . However the table is disabled now, so the RIT and znode will remain. > TimeoutMonitor draws a blank on it. > It will hold back enabling the table or balancer unless restart -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (HBASE-6537) Balancer compete with disable table will lead to cluster inconsistent
[ https://issues.apache.org/jira/browse/HBASE-6537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhou wenjian reassigned HBASE-6537: --- Assignee: Zhou wenjian > Balancer compete with disable table will lead to cluster inconsistent > -- > > Key: HBASE-6537 > URL: https://issues.apache.org/jira/browse/HBASE-6537 > Project: HBase > Issue Type: Bug > Components: master >Affects Versions: 0.94.0 >Reporter: Zhou wenjian >Assignee: Zhou wenjian > Fix For: 0.94.2 > > Attachments: HBASE-6537-trunk.patch > > > Appear in 94. trunk is ok for the issue > Balancer will collect the regionplans to move(unassign and then assign). > before unassign, disable table appears, > after close the region in rs, master will delete the znode, romove region > from RIT, > and then clean the region from the online regions. > During romoving region from RIT and cleaning out the region from the online > regions. > balancer begins to unassign, it will get a NotServingRegionException and if > the table is disabling, it will deal with the state in master and delete the > znode . However the table is disabled now, so the RIT and znode will remain. > TimeoutMonitor draws a blank on it. > It will hold back enabling the table or balancer unless restart -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-6473) deleted table is not deleted completely, some region may be still online
[
https://issues.apache.org/jira/browse/HBASE-6473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhou wenjian updated HBASE-6473:
Attachment: HBASE-6473-trunk-v4.patch
> deleted table is not deleted completely, some region may be still online
>
>
> Key: HBASE-6473
> URL: https://issues.apache.org/jira/browse/HBASE-6473
> Project: HBase
> Issue Type: Bug
>Affects Versions: 0.94.0
>Reporter: zhou wenjian
>Assignee: Zhou wenjian
> Fix For: 0.96.0, 0.94.2
>
> Attachments: HBASE-6473-trunk.patch, HBASE-6473-trunk-v2.patch,
> HBASE-6473-trunk-v3.patch, HBASE-6473-trunk-v4.patch
>
>
> consider such Scenario:
> we have a table called T1, which has 1 regions: A
> 1. move A from rs1 to rs2,and A is now closed
> 2. disable T1,
> 3. delete T1.
> when we disable T1, disable handler will just set the zk to disabled and A
> will still be assigned. when Ais opened, A in transition will be clean out.
> At that time, Deletetable found it is safe to delete all regions and table in
> meta and fs , it will also delete the zk node of T1.
> {code}
> while (System.currentTimeMillis() < done) {
> AssignmentManager.RegionState rs = am.isRegionInTransition(region);
> if (rs == null) break;
> Threads.sleep(waitingTimeForEvents);
> LOG.debug("Waiting on region to clear regions in transition; " + rs);
> }
> if (am.isRegionInTransition(region) != null) {
> throw new IOException("Waited hbase.master.wait.on.region (" +
> waitTime + "ms) for region to leave region " +
> region.getRegionNameAsString() + " in transitions");
> }
> {code}
> however A is still being unassigned, when it finished closed the A,it finds
> that the disabled state in zk is deleted, and then A will be assigned again.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6641) more message with DoNotRetryIOException in client
[
https://issues.apache.org/jira/browse/HBASE-6641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13440230#comment-13440230
]
Zhou wenjian commented on HBASE-6641:
-
After applying the patch,we could get what happened
org.apache.hadoop.hbase.client.RetriesExhaustedWithDetailsException: Failed
2000 actions: org.apache.hadoop.hbase.DoNotRetryIOException: Column family a
does not exist in region
logTable,8LK27P38EYG15H7JDEB5YT6TK1MADYZYGFXFE330L3MB29G5Z7,1345183514575.0c8bf995b1e70d6f26fdcaa03c701035.
in table {NAME => 'logTable', FAMILIES => [{NAME => 'cf', DATA_BLOCK_ENCODING
=> 'NONE', BLOOMFILTER => 'NONE', REPLICATION_SCOPE => '0', COMPRESSION =>
'NONE', VERSIONS => '3', TTL => '2147483647', MIN_VERSIONS => '0',
KEEP_DELETED_CELLS => 'false', BLOCKSIZE => '65536', ENCODE_ON_DISK => 'true',
IN_MEMORY => 'false', BLOCKCACHE => 'true'}]}
at
org.apache.hadoop.hbase.regionserver.HRegionServer.multi(HRegionServer.java:3773)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.apache.hadoop.hbase.ipc.WritableRpcEngine$Server.call(WritableRpcEngine.java:364)
at org.apache.hadoop.hbase.ipc.HBaseServer$Handler.run(HBaseServer.java:1401)
> more message with DoNotRetryIOException in client
> -
>
> Key: HBASE-6641
> URL: https://issues.apache.org/jira/browse/HBASE-6641
> Project: HBase
> Issue Type: Bug
> Components: client
>Affects Versions: 0.94.0
>Reporter: Zhou wenjian
>Assignee: Zhou wenjian
> Fix For: 0.94.2
>
> Attachments: HBASE-6641.patch
>
>
> when write a row with wrong or unexist family into a table , we will get
> message below
> org.apache.hadoop.hbase.client.RetriesExhaustedWithDetailsException: Failed
> 2000 actions: DoNotRetryIOException: 2000 times, servers with issues:
> dw82.kgb.sqa.cm4:64020, at
> org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.processBatchCallback(HConnectionManager.java:1591)
> at
> org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.processBatch(HConnectionManager.java:1367)
> at org.apache.hadoop.hbase.client.HTable.flushCommits(HTable.java:945)
> at org.apache.hadoop.hbase.client.HTable.doPut(HTable.java:801)
> at org.apache.hadoop.hbase.client.HTable.put(HTable.java:784)
> at zookeeper.WriteMultiThread.doInsert(WriteToTable.java:101)
> at zookeeper.WriteMultiThread.run(WriteToTable.java:80)
> it not friendly to the client. Need to show the client more details about the
> exception.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-6641) more message with DoNotRetryIOException in client
[ https://issues.apache.org/jira/browse/HBASE-6641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhou wenjian updated HBASE-6641: Attachment: HBASE-6641.patch > more message with DoNotRetryIOException in client > - > > Key: HBASE-6641 > URL: https://issues.apache.org/jira/browse/HBASE-6641 > Project: HBase > Issue Type: Bug > Components: client >Affects Versions: 0.94.0 >Reporter: Zhou wenjian >Assignee: Zhou wenjian > Fix For: 0.94.2 > > Attachments: HBASE-6641.patch > > > when write a row with wrong or unexist family into a table , we will get > message below > org.apache.hadoop.hbase.client.RetriesExhaustedWithDetailsException: Failed > 2000 actions: DoNotRetryIOException: 2000 times, servers with issues: > dw82.kgb.sqa.cm4:64020, at > org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.processBatchCallback(HConnectionManager.java:1591) > at > org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.processBatch(HConnectionManager.java:1367) > at org.apache.hadoop.hbase.client.HTable.flushCommits(HTable.java:945) > at org.apache.hadoop.hbase.client.HTable.doPut(HTable.java:801) > at org.apache.hadoop.hbase.client.HTable.put(HTable.java:784) > at zookeeper.WriteMultiThread.doInsert(WriteToTable.java:101) > at zookeeper.WriteMultiThread.run(WriteToTable.java:80) > it not friendly to the client. Need to show the client more details about the > exception. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HBASE-6641) more message with DoNotRetryIOException in client
Zhou wenjian created HBASE-6641: --- Summary: more message with DoNotRetryIOException in client Key: HBASE-6641 URL: https://issues.apache.org/jira/browse/HBASE-6641 Project: HBase Issue Type: Bug Components: client Affects Versions: 0.94.0 Reporter: Zhou wenjian Assignee: Zhou wenjian Fix For: 0.94.2 when write a row with wrong or unexist family into a table , we will get message below org.apache.hadoop.hbase.client.RetriesExhaustedWithDetailsException: Failed 2000 actions: DoNotRetryIOException: 2000 times, servers with issues: dw82.kgb.sqa.cm4:64020, at org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.processBatchCallback(HConnectionManager.java:1591) at org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.processBatch(HConnectionManager.java:1367) at org.apache.hadoop.hbase.client.HTable.flushCommits(HTable.java:945) at org.apache.hadoop.hbase.client.HTable.doPut(HTable.java:801) at org.apache.hadoop.hbase.client.HTable.put(HTable.java:784) at zookeeper.WriteMultiThread.doInsert(WriteToTable.java:101) at zookeeper.WriteMultiThread.run(WriteToTable.java:80) it not friendly to the client. Need to show the client more details about the exception. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6625) If we have hundreds of thousands of regions getChildren will encouter zk exception
[
https://issues.apache.org/jira/browse/HBASE-6625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13438522#comment-13438522
]
Zhou wenjian commented on HBASE-6625:
-
the log appears in 90.
zk version： 3.3.3
seems 3.4 is affected too.
when the client read from zk, it will check the length of data default is 4M
if (len < 0 || len >= ClientCnxn.packetLen) {
throw new IOException("Packet len" + len + " is out of range!");
}
I think maybe we can increase the size of jute.maxbuffer when we start the
cluster.
> If we have hundreds of thousands of regions getChildren will encouter zk
> exception
> ---
>
> Key: HBASE-6625
> URL: https://issues.apache.org/jira/browse/HBASE-6625
> Project: HBase
> Issue Type: Bug
>Reporter: Zhou wenjian
>Assignee: Zhou wenjian
>
> 2012-05-13 19:37:37,528 DEBUG
> org.apache.hadoop.hbase.master.AssignmentManager$ExistsUnassignedAsyncCallback:
> rs=CreateNewTableWith10Regions,\x05\xB3\x06
> g\xE8r\xBB]\x09\xCF,1336724029944.079cb2f8a375e66fa089291b82f2a03f.
> state=OFFLINE, ts=1336909053108
> 2012-05-13 19:37:37,528 DEBUG
> org.apache.hadoop.hbase.master.AssignmentManager$CreateUnassignedAsyncCallback:
> rs=CreateNewTableWith10Regions,\x08s\x84\x8
> 8$7\xB1\xC4\xFCg,1336724030660.76c07780231942231013c7feb5e5eb14.
> state=OFFLINE, ts=1336909055089, server=dw76.kgb.sqa.cm4,60020,1336908983944
> 2012-05-13 19:37:37,528 DEBUG
> org.apache.hadoop.hbase.master.AssignmentManager$CreateUnassignedAsyncCallback:
> rs=CreateNewTableWith10Regions,\x08s\x89\xC
> B\x9B\xF0\xE4\xCA\x97\xB0,1336724030660.fa38b9d8367387a64a327087cb43b3e0.
> state=OFFLINE, ts=1336909055089, server=dw76.kgb.sqa.cm4,60020,1336908983944
> 2012-05-13 19:37:37,528 INFO
> org.apache.hadoop.hbase.master.AssignmentManager:
> dw76.kgb.sqa.cm4,60020,1336908983944 unassigned znodes=58464 of total=120002
> 2012-05-13 19:37:37,758 WARN org.apache.zookeeper.ClientCnxn: Session
> 0x13745fc2c8d0001 for server dw51.kgb.sqa.cm4/10.232.98.51:2180, unexpected
> error, clos
> ing socket connection and attempting reconnect
> java.io.IOException: Packet len4320092 is out of range!
> at
> org.apache.zookeeper.ClientCnxn$SendThread.readLength(ClientCnxn.java:710)
> at
> org.apache.zookeeper.ClientCnxn$SendThread.doIO(ClientCnxn.java:869)
> at
> org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1130)
> 2012-05-13 19:37:37,860 WARN org.apache.hadoop.hbase.zookeeper.ZKUtil:
> master:6-0x13745fc2c8d0001 Unable to list children of znode
> /hbase-new4/unassigned
> org.apache.zookeeper.KeeperException$ConnectionLossException: KeeperErrorCode
> = ConnectionLoss for /hbase-new4/unassigned
> at
> org.apache.zookeeper.KeeperException.create(KeeperException.java:90)
> at
> org.apache.zookeeper.KeeperException.create(KeeperException.java:42)
> at org.apache.zookeeper.ZooKeeper.getChildren(ZooKeeper.java:1243)
> at
> org.apache.hadoop.hbase.zookeeper.ZKUtil.listChildrenAndWatchForNewChildren(ZKUtil.java:302)
>
> at
> org.apache.hadoop.hbase.zookeeper.ZKUtil.watchAndGetNewChildren(ZKUtil.java:413)
>
> at
> org.apache.hadoop.hbase.master.AssignmentManager.nodeChildrenChanged(AssignmentManager.java:759)
>
> at
> org.apache.hadoop.hbase.zookeeper.ZooKeeperWatcher.process(ZooKeeperWatcher.java:314)
>
> at
> org.apache.zookeeper.ClientCnxn$EventThread.processEvent(ClientCnxn.java:530)
> at
> org.apache.zookeeper.ClientCnxn$EventThread.run(ClientCnxn.java:506)
> 2012-05-13 19:37:37,861 ERROR
> org.apache.hadoop.hbase.zookeeper.ZooKeeperWatcher:
> master:6-0x13745fc2c8d0001 Received unexpected KeeperException, re-thro
> wing exception
> org.apache.zookeeper.KeeperException$ConnectionLossException: KeeperErrorCode
> = ConnectionLoss for /hbase-new4/unassigned
> at
> org.apache.zookeeper.KeeperException.create(KeeperException.java:90)
> at
> org.apache.zookeeper.KeeperException.create(KeeperException.java:42)
> at org.apache.zookeeper.ZooKeeper.getChildren(ZooKeeper.java:1243)
> at
> org.apache.hadoop.hbase.zookeeper.ZKUtil.listChildrenAndWatchForNewChildren(ZKUtil.java:302)
>
> at
> org.apache.hadoop.hbase.zookeeper.ZKUtil.watchAndGetNewChildren(ZKUtil.java:413)
>
> at
> org.apache.hadoop.hbase.master.AssignmentManager.nodeChildrenChanged(AssignmentManager.java:759)
>
> at
> org.apache.hadoop.hbase.zookeeper.ZooKeeperWatcher.process(ZooKeeperWatcher.java:314)
>
> at
> org.apache.zookeeper.ClientCnxn$EventThread.processEvent(ClientCnxn.java:530)
> at
> org.apache.zookeeper.ClientCnxn$EventThread.run(ClientCnxn.j
[jira] [Created] (HBASE-6625) If we have hundreds of thousands of regions getChildren will encouter zk exception
Zhou wenjian created HBASE-6625: --- Summary: If we have hundreds of thousands of regions getChildren will encouter zk exception Key: HBASE-6625 URL: https://issues.apache.org/jira/browse/HBASE-6625 Project: HBase Issue Type: Bug Reporter: Zhou wenjian Assignee: Zhou wenjian 2012-05-13 19:37:37,528 DEBUG org.apache.hadoop.hbase.master.AssignmentManager$ExistsUnassignedAsyncCallback: rs=CreateNewTableWith10Regions,\x05\xB3\x06 g\xE8r\xBB]\x09\xCF,1336724029944.079cb2f8a375e66fa089291b82f2a03f. state=OFFLINE, ts=1336909053108 2012-05-13 19:37:37,528 DEBUG org.apache.hadoop.hbase.master.AssignmentManager$CreateUnassignedAsyncCallback: rs=CreateNewTableWith10Regions,\x08s\x84\x8 8$7\xB1\xC4\xFCg,1336724030660.76c07780231942231013c7feb5e5eb14. state=OFFLINE, ts=1336909055089, server=dw76.kgb.sqa.cm4,60020,1336908983944 2012-05-13 19:37:37,528 DEBUG org.apache.hadoop.hbase.master.AssignmentManager$CreateUnassignedAsyncCallback: rs=CreateNewTableWith10Regions,\x08s\x89\xC B\x9B\xF0\xE4\xCA\x97\xB0,1336724030660.fa38b9d8367387a64a327087cb43b3e0. state=OFFLINE, ts=1336909055089, server=dw76.kgb.sqa.cm4,60020,1336908983944 2012-05-13 19:37:37,528 INFO org.apache.hadoop.hbase.master.AssignmentManager: dw76.kgb.sqa.cm4,60020,1336908983944 unassigned znodes=58464 of total=120002 2012-05-13 19:37:37,758 WARN org.apache.zookeeper.ClientCnxn: Session 0x13745fc2c8d0001 for server dw51.kgb.sqa.cm4/10.232.98.51:2180, unexpected error, clos ing socket connection and attempting reconnect java.io.IOException: Packet len4320092 is out of range! at org.apache.zookeeper.ClientCnxn$SendThread.readLength(ClientCnxn.java:710) at org.apache.zookeeper.ClientCnxn$SendThread.doIO(ClientCnxn.java:869) at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1130) 2012-05-13 19:37:37,860 WARN org.apache.hadoop.hbase.zookeeper.ZKUtil: master:6-0x13745fc2c8d0001 Unable to list children of znode /hbase-new4/unassigned org.apache.zookeeper.KeeperException$ConnectionLossException: KeeperErrorCode = ConnectionLoss for /hbase-new4/unassigned at org.apache.zookeeper.KeeperException.create(KeeperException.java:90) at org.apache.zookeeper.KeeperException.create(KeeperException.java:42) at org.apache.zookeeper.ZooKeeper.getChildren(ZooKeeper.java:1243) at org.apache.hadoop.hbase.zookeeper.ZKUtil.listChildrenAndWatchForNewChildren(ZKUtil.java:302) at org.apache.hadoop.hbase.zookeeper.ZKUtil.watchAndGetNewChildren(ZKUtil.java:413) at org.apache.hadoop.hbase.master.AssignmentManager.nodeChildrenChanged(AssignmentManager.java:759) at org.apache.hadoop.hbase.zookeeper.ZooKeeperWatcher.process(ZooKeeperWatcher.java:314) at org.apache.zookeeper.ClientCnxn$EventThread.processEvent(ClientCnxn.java:530) at org.apache.zookeeper.ClientCnxn$EventThread.run(ClientCnxn.java:506) 2012-05-13 19:37:37,861 ERROR org.apache.hadoop.hbase.zookeeper.ZooKeeperWatcher: master:6-0x13745fc2c8d0001 Received unexpected KeeperException, re-thro wing exception org.apache.zookeeper.KeeperException$ConnectionLossException: KeeperErrorCode = ConnectionLoss for /hbase-new4/unassigned at org.apache.zookeeper.KeeperException.create(KeeperException.java:90) at org.apache.zookeeper.KeeperException.create(KeeperException.java:42) at org.apache.zookeeper.ZooKeeper.getChildren(ZooKeeper.java:1243) at org.apache.hadoop.hbase.zookeeper.ZKUtil.listChildrenAndWatchForNewChildren(ZKUtil.java:302) at org.apache.hadoop.hbase.zookeeper.ZKUtil.watchAndGetNewChildren(ZKUtil.java:413) at org.apache.hadoop.hbase.master.AssignmentManager.nodeChildrenChanged(AssignmentManager.java:759) at org.apache.hadoop.hbase.zookeeper.ZooKeeperWatcher.process(ZooKeeperWatcher.java:314) at org.apache.zookeeper.ClientCnxn$EventThread.processEvent(ClientCnxn.java:530) at org.apache.zookeeper.ClientCnxn$EventThread.run(ClientCnxn.java:506) 2012-05-13 19:37:37,861 FATAL org.apache.hadoop.hbase.master.HMaster: Unexpected ZK exception reading unassigned children org.apache.zookeeper.KeeperException$ConnectionLossException: KeeperErrorCode = ConnectionLoss for /hbase-new4/unassigned at org.apache.zookeeper.KeeperException.create(KeeperException.java:90) at org.apache.zookeeper.KeeperException.create(KeeperException.java:42) at org.apache.zookeeper.ZooKeeper.getChildren(ZooKeeper.java:1243) at org.apache.hadoop.hbase.zookeeper.ZKUtil.listChildrenAndWatchForNewChildren(ZKUtil.java:302) at org.apache.hadoop.hbase.zookeeper.ZKUtil.watchAndGetNewChildren(ZKUtil.java:413) at org.apache.hadoop.hbase.master.AssignmentManager.nodeChildrenChanged(AssignmentManager.java:759)
[jira] [Updated] (HBASE-6588) enable table throws npe and leaves trash in zk in competition with delete table
[
https://issues.apache.org/jira/browse/HBASE-6588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhou wenjian updated HBASE-6588:
Attachment: HBASE-6588-trunk-v6.patch
> enable table throws npe and leaves trash in zk in competition with delete
> table
> ---
>
> Key: HBASE-6588
> URL: https://issues.apache.org/jira/browse/HBASE-6588
> Project: HBase
> Issue Type: Bug
>Affects Versions: 0.94.0
>Reporter: Zhou wenjian
>Assignee: Zhou wenjian
> Fix For: 0.94.2
>
> Attachments: HBASE-6588-trunk.patch, HBASE-6588-trunk-v2.patch,
> HBASE-6588-trunk-v3.patch, HBASE-6588-trunk-v4.patch,
> HBASE-6588-trunk-v5.patch, HBASE-6588-trunk-v6.patch
>
>
> 2012-08-15 19:23:36,178 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Creating scanner over .META. starting at key 'test,,'
> 2012-08-15 19:23:36,178 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Advancing internal scanner to startKey at 'test,,'
> 2012-08-15 19:24:09,180 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Creating scanner over .META. starting at key ''
> 2012-08-15 19:24:09,180 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Advancing internal scanner to startKey at ''
> 2012-08-15 19:24:09,183 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Finished with scanning at {NAME => '.META.,,1', STARTKEY => '', ENDKEY => '',
> ENCODED => 1028785192,}
> 2012-08-15 19:24:09,183 DEBUG org.apache.hadoop.hbase.master.CatalogJanitor:
> Scanned 2 catalog row(s) and gc'd 0 unreferenced parent region(s)
> 2012-08-15 19:25:12,260 DEBUG
> org.apache.hadoop.hbase.master.handler.DeleteTableHandler: Deleting region
> test,,1345029764571.d1e24b251ca6286c840a9a5f571b7db1. from META and FS
> 2012-08-15 19:25:12,263 INFO org.apache.hadoop.hbase.catalog.MetaEditor:
> Deleted region test,,1345029764571.d1e24b251ca6286c840a9a5f571b7db1. from META
> 2012-08-15 19:25:12,265 INFO
> org.apache.hadoop.hbase.master.handler.EnableTableHandler: Attemping to
> enable the table test
> 2012-08-15 19:25:12,265 WARN org.apache.hadoop.hbase.zookeeper.ZKTable:
> Moving table test state to enabling but was not first in disabled state: null
> 2012-08-15 19:25:12,267 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Creating scanner over .META. starting at key 'test,,'
> 2012-08-15 19:25:12,267 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Advancing internal scanner to startKey at 'test,,'
> 2012-08-15 19:25:12,270 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Finished with scanning at {NAME => '.META.,,1', STARTKEY => '', ENDKEY => '',
> ENCODED => 1028785192,}
> 2012-08-15 19:25:12,270 ERROR org.apache.hadoop.hbase.executor.EventHandler:
> Caught throwable while processing event C_M_ENABLE_TABLE
> java.lang.NullPointerException
> at
> org.apache.hadoop.hbase.master.handler.EnableTableHandler.handleEnableTable(EnableTableHandler.java:116)
> at
> org.apache.hadoop.hbase.master.handler.EnableTableHandler.process(EnableTableHandler.java:97)
> at
> org.apache.hadoop.hbase.executor.EventHandler.run(EventHandler.java:169)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:662)
> table is disabled now, then we enable and delete the table at the same time.
> Since the thread num of MASTER_TABLE_OPERATIONS is 1 by default. The two
> operations are serial in master.Before deletetable deletes all the regions in
> meta, CreateTableHandler ships the check of tableExists,then it will block
> until deletetable finishs, then CreateTableHandler will set zk enabling, and
> find no data in meta:
> regionsInMeta = MetaReader.getTableRegions(this.ct, tableName, true);
> int countOfRegionsInTable = regionsInMeta.size();
> npe will be throwed here. And we could not create the same table anymore.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6588) enable table throws npe and leaves trash in zk in competition with delete table
[
https://issues.apache.org/jira/browse/HBASE-6588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13438467#comment-13438467
]
Zhou wenjian commented on HBASE-6588:
-
sorry, forget to import org.apache.hadoop.hbase.master.RegionState in testAdmin
> enable table throws npe and leaves trash in zk in competition with delete
> table
> ---
>
> Key: HBASE-6588
> URL: https://issues.apache.org/jira/browse/HBASE-6588
> Project: HBase
> Issue Type: Bug
>Affects Versions: 0.94.0
>Reporter: Zhou wenjian
>Assignee: Zhou wenjian
> Fix For: 0.94.2
>
> Attachments: HBASE-6588-trunk.patch, HBASE-6588-trunk-v2.patch,
> HBASE-6588-trunk-v3.patch, HBASE-6588-trunk-v4.patch,
> HBASE-6588-trunk-v5.patch, HBASE-6588-trunk-v6.patch
>
>
> 2012-08-15 19:23:36,178 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Creating scanner over .META. starting at key 'test,,'
> 2012-08-15 19:23:36,178 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Advancing internal scanner to startKey at 'test,,'
> 2012-08-15 19:24:09,180 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Creating scanner over .META. starting at key ''
> 2012-08-15 19:24:09,180 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Advancing internal scanner to startKey at ''
> 2012-08-15 19:24:09,183 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Finished with scanning at {NAME => '.META.,,1', STARTKEY => '', ENDKEY => '',
> ENCODED => 1028785192,}
> 2012-08-15 19:24:09,183 DEBUG org.apache.hadoop.hbase.master.CatalogJanitor:
> Scanned 2 catalog row(s) and gc'd 0 unreferenced parent region(s)
> 2012-08-15 19:25:12,260 DEBUG
> org.apache.hadoop.hbase.master.handler.DeleteTableHandler: Deleting region
> test,,1345029764571.d1e24b251ca6286c840a9a5f571b7db1. from META and FS
> 2012-08-15 19:25:12,263 INFO org.apache.hadoop.hbase.catalog.MetaEditor:
> Deleted region test,,1345029764571.d1e24b251ca6286c840a9a5f571b7db1. from META
> 2012-08-15 19:25:12,265 INFO
> org.apache.hadoop.hbase.master.handler.EnableTableHandler: Attemping to
> enable the table test
> 2012-08-15 19:25:12,265 WARN org.apache.hadoop.hbase.zookeeper.ZKTable:
> Moving table test state to enabling but was not first in disabled state: null
> 2012-08-15 19:25:12,267 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Creating scanner over .META. starting at key 'test,,'
> 2012-08-15 19:25:12,267 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Advancing internal scanner to startKey at 'test,,'
> 2012-08-15 19:25:12,270 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Finished with scanning at {NAME => '.META.,,1', STARTKEY => '', ENDKEY => '',
> ENCODED => 1028785192,}
> 2012-08-15 19:25:12,270 ERROR org.apache.hadoop.hbase.executor.EventHandler:
> Caught throwable while processing event C_M_ENABLE_TABLE
> java.lang.NullPointerException
> at
> org.apache.hadoop.hbase.master.handler.EnableTableHandler.handleEnableTable(EnableTableHandler.java:116)
> at
> org.apache.hadoop.hbase.master.handler.EnableTableHandler.process(EnableTableHandler.java:97)
> at
> org.apache.hadoop.hbase.executor.EventHandler.run(EventHandler.java:169)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:662)
> table is disabled now, then we enable and delete the table at the same time.
> Since the thread num of MASTER_TABLE_OPERATIONS is 1 by default. The two
> operations are serial in master.Before deletetable deletes all the regions in
> meta, CreateTableHandler ships the check of tableExists,then it will block
> until deletetable finishs, then CreateTableHandler will set zk enabling, and
> find no data in meta:
> regionsInMeta = MetaReader.getTableRegions(this.ct, tableName, true);
> int countOfRegionsInTable = regionsInMeta.size();
> npe will be throwed here. And we could not create the same table anymore.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-6615) hbase.rs.evictblocksonclose seems to be ineffective
[ https://issues.apache.org/jira/browse/HBASE-6615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhou wenjian updated HBASE-6615: Affects Version/s: 0.94.1 Fix Version/s: 0.94.2 > hbase.rs.evictblocksonclose seems to be ineffective > --- > > Key: HBASE-6615 > URL: https://issues.apache.org/jira/browse/HBASE-6615 > Project: HBase > Issue Type: Bug >Affects Versions: 0.94.1 >Reporter: Zhou wenjian >Assignee: Zhou wenjian > Fix For: 0.94.2 > > > when we close region，storefile.closeReader(true) is invoked, it seems that > hbase.rs.evictblocksonclose is ineffective. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HBASE-6615) hbase.rs.evictblocksonclose seems to be ineffective
Zhou wenjian created HBASE-6615: --- Summary: hbase.rs.evictblocksonclose seems to be ineffective Key: HBASE-6615 URL: https://issues.apache.org/jira/browse/HBASE-6615 Project: HBase Issue Type: Bug Reporter: Zhou wenjian Assignee: Zhou wenjian when we close region，storefile.closeReader(true) is invoked, it seems that hbase.rs.evictblocksonclose is ineffective. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-6537) Balancer compete with disable table will lead to cluster inconsistent
[ https://issues.apache.org/jira/browse/HBASE-6537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhou wenjian updated HBASE-6537: Status: Open (was: Patch Available) > Balancer compete with disable table will lead to cluster inconsistent > -- > > Key: HBASE-6537 > URL: https://issues.apache.org/jira/browse/HBASE-6537 > Project: HBase > Issue Type: Bug > Components: master >Affects Versions: 0.94.0 >Reporter: Zhou wenjian > Fix For: 0.94.2 > > Attachments: HBASE-6537-94.patch, HBASE-6537-94-v2.patch, > HBASE-6537-trunk.patch > > > Appear in 94. trunk is ok for the issue > Balancer will collect the regionplans to move(unassign and then assign). > before unassign, disable table appears, > after close the region in rs, master will delete the znode, romove region > from RIT, > and then clean the region from the online regions. > During romoving region from RIT and cleaning out the region from the online > regions. > balancer begins to unassign, it will get a NotServingRegionException and if > the table is disabling, it will deal with the state in master and delete the > znode . However the table is disabled now, so the RIT and znode will remain. > TimeoutMonitor draws a blank on it. > It will hold back enabling the table or balancer unless restart -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-6537) Balancer compete with disable table will lead to cluster inconsistent
[ https://issues.apache.org/jira/browse/HBASE-6537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhou wenjian updated HBASE-6537: Status: Patch Available (was: Open) > Balancer compete with disable table will lead to cluster inconsistent > -- > > Key: HBASE-6537 > URL: https://issues.apache.org/jira/browse/HBASE-6537 > Project: HBase > Issue Type: Bug > Components: master >Affects Versions: 0.94.0 >Reporter: Zhou wenjian > Fix For: 0.94.2 > > Attachments: HBASE-6537-94.patch, HBASE-6537-94-v2.patch, > HBASE-6537-trunk.patch > > > Appear in 94. trunk is ok for the issue > Balancer will collect the regionplans to move(unassign and then assign). > before unassign, disable table appears, > after close the region in rs, master will delete the znode, romove region > from RIT, > and then clean the region from the online regions. > During romoving region from RIT and cleaning out the region from the online > regions. > balancer begins to unassign, it will get a NotServingRegionException and if > the table is disabling, it will deal with the state in master and delete the > znode . However the table is disabled now, so the RIT and znode will remain. > TimeoutMonitor draws a blank on it. > It will hold back enabling the table or balancer unless restart -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-6537) Balancer compete with disable table will lead to cluster inconsistent
[ https://issues.apache.org/jira/browse/HBASE-6537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhou wenjian updated HBASE-6537: Status: Patch Available (was: Open) > Balancer compete with disable table will lead to cluster inconsistent > -- > > Key: HBASE-6537 > URL: https://issues.apache.org/jira/browse/HBASE-6537 > Project: HBase > Issue Type: Bug > Components: master >Affects Versions: 0.94.0 >Reporter: Zhou wenjian > Fix For: 0.94.2 > > Attachments: HBASE-6537-94.patch, HBASE-6537-94-v2.patch, > HBASE-6537-trunk.patch > > > Appear in 94. trunk is ok for the issue > Balancer will collect the regionplans to move(unassign and then assign). > before unassign, disable table appears, > after close the region in rs, master will delete the znode, romove region > from RIT, > and then clean the region from the online regions. > During romoving region from RIT and cleaning out the region from the online > regions. > balancer begins to unassign, it will get a NotServingRegionException and if > the table is disabling, it will deal with the state in master and delete the > znode . However the table is disabled now, so the RIT and znode will remain. > TimeoutMonitor draws a blank on it. > It will hold back enabling the table or balancer unless restart -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6473) deleted table is not deleted completely, some region may be still online
[
https://issues.apache.org/jira/browse/HBASE-6473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13437635#comment-13437635
]
Zhou wenjian commented on HBASE-6473:
-
Look into the failed case ,found nothing with my case, may be caused by
unstable hudsun
> deleted table is not deleted completely, some region may be still online
>
>
> Key: HBASE-6473
> URL: https://issues.apache.org/jira/browse/HBASE-6473
> Project: HBase
> Issue Type: Bug
>Affects Versions: 0.94.0
>Reporter: zhou wenjian
> Fix For: 0.96.0, 0.94.2
>
> Attachments: HBASE-6473-trunk.patch, HBASE-6473-trunk-v2.patch,
> HBASE-6473-trunk-v3.patch
>
>
> consider such Scenario:
> we have a table called T1, which has 1 regions: A
> 1. move A from rs1 to rs2,and A is now closed
> 2. disable T1,
> 3. delete T1.
> when we disable T1, disable handler will just set the zk to disabled and A
> will still be assigned. when Ais opened, A in transition will be clean out.
> At that time, Deletetable found it is safe to delete all regions and table in
> meta and fs , it will also delete the zk node of T1.
> {code}
> while (System.currentTimeMillis() < done) {
> AssignmentManager.RegionState rs = am.isRegionInTransition(region);
> if (rs == null) break;
> Threads.sleep(waitingTimeForEvents);
> LOG.debug("Waiting on region to clear regions in transition; " + rs);
> }
> if (am.isRegionInTransition(region) != null) {
> throw new IOException("Waited hbase.master.wait.on.region (" +
> waitTime + "ms) for region to leave region " +
> region.getRegionNameAsString() + " in transitions");
> }
> {code}
> however A is still being unassigned, when it finished closed the A,it finds
> that the disabled state in zk is deleted, and then A will be assigned again.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6473) deleted table is not deleted completely, some region may be still online
[
https://issues.apache.org/jira/browse/HBASE-6473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13437633#comment-13437633
]
Zhou wenjian commented on HBASE-6473:
-
@stack
that is right, if a region is offline, it will not in
am.getRegionStates().getRegionsOfTable(tableName) and rit.
Nice of you to add the parens on commit.
> deleted table is not deleted completely, some region may be still online
>
>
> Key: HBASE-6473
> URL: https://issues.apache.org/jira/browse/HBASE-6473
> Project: HBase
> Issue Type: Bug
>Affects Versions: 0.94.0
>Reporter: zhou wenjian
> Fix For: 0.96.0, 0.94.2
>
> Attachments: HBASE-6473-trunk.patch, HBASE-6473-trunk-v2.patch,
> HBASE-6473-trunk-v3.patch
>
>
> consider such Scenario:
> we have a table called T1, which has 1 regions: A
> 1. move A from rs1 to rs2,and A is now closed
> 2. disable T1,
> 3. delete T1.
> when we disable T1, disable handler will just set the zk to disabled and A
> will still be assigned. when Ais opened, A in transition will be clean out.
> At that time, Deletetable found it is safe to delete all regions and table in
> meta and fs , it will also delete the zk node of T1.
> {code}
> while (System.currentTimeMillis() < done) {
> AssignmentManager.RegionState rs = am.isRegionInTransition(region);
> if (rs == null) break;
> Threads.sleep(waitingTimeForEvents);
> LOG.debug("Waiting on region to clear regions in transition; " + rs);
> }
> if (am.isRegionInTransition(region) != null) {
> throw new IOException("Waited hbase.master.wait.on.region (" +
> waitTime + "ms) for region to leave region " +
> region.getRegionNameAsString() + " in transitions");
> }
> {code}
> however A is still being unassigned, when it finished closed the A,it finds
> that the disabled state in zk is deleted, and then A will be assigned again.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-6588) enable table throws npe and leaves trash in zk in competition with delete table
[
https://issues.apache.org/jira/browse/HBASE-6588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhou wenjian updated HBASE-6588:
Attachment: HBASE-6588-trunk-v5.patch
> enable table throws npe and leaves trash in zk in competition with delete
> table
> ---
>
> Key: HBASE-6588
> URL: https://issues.apache.org/jira/browse/HBASE-6588
> Project: HBase
> Issue Type: Bug
>Affects Versions: 0.94.0
>Reporter: Zhou wenjian
> Fix For: 0.94.2
>
> Attachments: HBASE-6588-trunk.patch, HBASE-6588-trunk-v2.patch,
> HBASE-6588-trunk-v3.patch, HBASE-6588-trunk-v4.patch,
> HBASE-6588-trunk-v5.patch
>
>
> 2012-08-15 19:23:36,178 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Creating scanner over .META. starting at key 'test,,'
> 2012-08-15 19:23:36,178 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Advancing internal scanner to startKey at 'test,,'
> 2012-08-15 19:24:09,180 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Creating scanner over .META. starting at key ''
> 2012-08-15 19:24:09,180 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Advancing internal scanner to startKey at ''
> 2012-08-15 19:24:09,183 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Finished with scanning at {NAME => '.META.,,1', STARTKEY => '', ENDKEY => '',
> ENCODED => 1028785192,}
> 2012-08-15 19:24:09,183 DEBUG org.apache.hadoop.hbase.master.CatalogJanitor:
> Scanned 2 catalog row(s) and gc'd 0 unreferenced parent region(s)
> 2012-08-15 19:25:12,260 DEBUG
> org.apache.hadoop.hbase.master.handler.DeleteTableHandler: Deleting region
> test,,1345029764571.d1e24b251ca6286c840a9a5f571b7db1. from META and FS
> 2012-08-15 19:25:12,263 INFO org.apache.hadoop.hbase.catalog.MetaEditor:
> Deleted region test,,1345029764571.d1e24b251ca6286c840a9a5f571b7db1. from META
> 2012-08-15 19:25:12,265 INFO
> org.apache.hadoop.hbase.master.handler.EnableTableHandler: Attemping to
> enable the table test
> 2012-08-15 19:25:12,265 WARN org.apache.hadoop.hbase.zookeeper.ZKTable:
> Moving table test state to enabling but was not first in disabled state: null
> 2012-08-15 19:25:12,267 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Creating scanner over .META. starting at key 'test,,'
> 2012-08-15 19:25:12,267 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Advancing internal scanner to startKey at 'test,,'
> 2012-08-15 19:25:12,270 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Finished with scanning at {NAME => '.META.,,1', STARTKEY => '', ENDKEY => '',
> ENCODED => 1028785192,}
> 2012-08-15 19:25:12,270 ERROR org.apache.hadoop.hbase.executor.EventHandler:
> Caught throwable while processing event C_M_ENABLE_TABLE
> java.lang.NullPointerException
> at
> org.apache.hadoop.hbase.master.handler.EnableTableHandler.handleEnableTable(EnableTableHandler.java:116)
> at
> org.apache.hadoop.hbase.master.handler.EnableTableHandler.process(EnableTableHandler.java:97)
> at
> org.apache.hadoop.hbase.executor.EventHandler.run(EventHandler.java:169)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:662)
> table is disabled now, then we enable and delete the table at the same time.
> Since the thread num of MASTER_TABLE_OPERATIONS is 1 by default. The two
> operations are serial in master.Before deletetable deletes all the regions in
> meta, CreateTableHandler ships the check of tableExists,then it will block
> until deletetable finishs, then CreateTableHandler will set zk enabling, and
> find no data in meta:
> regionsInMeta = MetaReader.getTableRegions(this.ct, tableName, true);
> int countOfRegionsInTable = regionsInMeta.size();
> npe will be throwed here. And we could not create the same table anymore.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6588) enable table throws npe and leaves trash in zk in competition with delete table
[
https://issues.apache.org/jira/browse/HBASE-6588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13437626#comment-13437626
]
Zhou wenjian commented on HBASE-6588:
-
@stack
has corrected what Ram found.
the synchronous delete now uses async delete, that is right.
will update for v5 as suggested
> enable table throws npe and leaves trash in zk in competition with delete
> table
> ---
>
> Key: HBASE-6588
> URL: https://issues.apache.org/jira/browse/HBASE-6588
> Project: HBase
> Issue Type: Bug
>Affects Versions: 0.94.0
>Reporter: Zhou wenjian
> Fix For: 0.94.2
>
> Attachments: HBASE-6588-trunk.patch, HBASE-6588-trunk-v2.patch,
> HBASE-6588-trunk-v3.patch, HBASE-6588-trunk-v4.patch
>
>
> 2012-08-15 19:23:36,178 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Creating scanner over .META. starting at key 'test,,'
> 2012-08-15 19:23:36,178 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Advancing internal scanner to startKey at 'test,,'
> 2012-08-15 19:24:09,180 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Creating scanner over .META. starting at key ''
> 2012-08-15 19:24:09,180 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Advancing internal scanner to startKey at ''
> 2012-08-15 19:24:09,183 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Finished with scanning at {NAME => '.META.,,1', STARTKEY => '', ENDKEY => '',
> ENCODED => 1028785192,}
> 2012-08-15 19:24:09,183 DEBUG org.apache.hadoop.hbase.master.CatalogJanitor:
> Scanned 2 catalog row(s) and gc'd 0 unreferenced parent region(s)
> 2012-08-15 19:25:12,260 DEBUG
> org.apache.hadoop.hbase.master.handler.DeleteTableHandler: Deleting region
> test,,1345029764571.d1e24b251ca6286c840a9a5f571b7db1. from META and FS
> 2012-08-15 19:25:12,263 INFO org.apache.hadoop.hbase.catalog.MetaEditor:
> Deleted region test,,1345029764571.d1e24b251ca6286c840a9a5f571b7db1. from META
> 2012-08-15 19:25:12,265 INFO
> org.apache.hadoop.hbase.master.handler.EnableTableHandler: Attemping to
> enable the table test
> 2012-08-15 19:25:12,265 WARN org.apache.hadoop.hbase.zookeeper.ZKTable:
> Moving table test state to enabling but was not first in disabled state: null
> 2012-08-15 19:25:12,267 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Creating scanner over .META. starting at key 'test,,'
> 2012-08-15 19:25:12,267 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Advancing internal scanner to startKey at 'test,,'
> 2012-08-15 19:25:12,270 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Finished with scanning at {NAME => '.META.,,1', STARTKEY => '', ENDKEY => '',
> ENCODED => 1028785192,}
> 2012-08-15 19:25:12,270 ERROR org.apache.hadoop.hbase.executor.EventHandler:
> Caught throwable while processing event C_M_ENABLE_TABLE
> java.lang.NullPointerException
> at
> org.apache.hadoop.hbase.master.handler.EnableTableHandler.handleEnableTable(EnableTableHandler.java:116)
> at
> org.apache.hadoop.hbase.master.handler.EnableTableHandler.process(EnableTableHandler.java:97)
> at
> org.apache.hadoop.hbase.executor.EventHandler.run(EventHandler.java:169)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:662)
> table is disabled now, then we enable and delete the table at the same time.
> Since the thread num of MASTER_TABLE_OPERATIONS is 1 by default. The two
> operations are serial in master.Before deletetable deletes all the regions in
> meta, CreateTableHandler ships the check of tableExists,then it will block
> until deletetable finishs, then CreateTableHandler will set zk enabling, and
> find no data in meta:
> regionsInMeta = MetaReader.getTableRegions(this.ct, tableName, true);
> int countOfRegionsInTable = regionsInMeta.size();
> npe will be throwed here. And we could not create the same table anymore.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-6588) enable table throws npe and leaves trash in zk in competition with delete table
[
https://issues.apache.org/jira/browse/HBASE-6588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhou wenjian updated HBASE-6588:
Attachment: HBASE-6588-trunk-v4.patch
> enable table throws npe and leaves trash in zk in competition with delete
> table
> ---
>
> Key: HBASE-6588
> URL: https://issues.apache.org/jira/browse/HBASE-6588
> Project: HBase
> Issue Type: Bug
>Affects Versions: 0.94.0
>Reporter: Zhou wenjian
> Fix For: 0.94.2
>
> Attachments: HBASE-6588-trunk.patch, HBASE-6588-trunk-v2.patch,
> HBASE-6588-trunk-v3.patch, HBASE-6588-trunk-v4.patch
>
>
> 2012-08-15 19:23:36,178 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Creating scanner over .META. starting at key 'test,,'
> 2012-08-15 19:23:36,178 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Advancing internal scanner to startKey at 'test,,'
> 2012-08-15 19:24:09,180 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Creating scanner over .META. starting at key ''
> 2012-08-15 19:24:09,180 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Advancing internal scanner to startKey at ''
> 2012-08-15 19:24:09,183 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Finished with scanning at {NAME => '.META.,,1', STARTKEY => '', ENDKEY => '',
> ENCODED => 1028785192,}
> 2012-08-15 19:24:09,183 DEBUG org.apache.hadoop.hbase.master.CatalogJanitor:
> Scanned 2 catalog row(s) and gc'd 0 unreferenced parent region(s)
> 2012-08-15 19:25:12,260 DEBUG
> org.apache.hadoop.hbase.master.handler.DeleteTableHandler: Deleting region
> test,,1345029764571.d1e24b251ca6286c840a9a5f571b7db1. from META and FS
> 2012-08-15 19:25:12,263 INFO org.apache.hadoop.hbase.catalog.MetaEditor:
> Deleted region test,,1345029764571.d1e24b251ca6286c840a9a5f571b7db1. from META
> 2012-08-15 19:25:12,265 INFO
> org.apache.hadoop.hbase.master.handler.EnableTableHandler: Attemping to
> enable the table test
> 2012-08-15 19:25:12,265 WARN org.apache.hadoop.hbase.zookeeper.ZKTable:
> Moving table test state to enabling but was not first in disabled state: null
> 2012-08-15 19:25:12,267 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Creating scanner over .META. starting at key 'test,,'
> 2012-08-15 19:25:12,267 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Advancing internal scanner to startKey at 'test,,'
> 2012-08-15 19:25:12,270 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Finished with scanning at {NAME => '.META.,,1', STARTKEY => '', ENDKEY => '',
> ENCODED => 1028785192,}
> 2012-08-15 19:25:12,270 ERROR org.apache.hadoop.hbase.executor.EventHandler:
> Caught throwable while processing event C_M_ENABLE_TABLE
> java.lang.NullPointerException
> at
> org.apache.hadoop.hbase.master.handler.EnableTableHandler.handleEnableTable(EnableTableHandler.java:116)
> at
> org.apache.hadoop.hbase.master.handler.EnableTableHandler.process(EnableTableHandler.java:97)
> at
> org.apache.hadoop.hbase.executor.EventHandler.run(EventHandler.java:169)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:662)
> table is disabled now, then we enable and delete the table at the same time.
> Since the thread num of MASTER_TABLE_OPERATIONS is 1 by default. The two
> operations are serial in master.Before deletetable deletes all the regions in
> meta, CreateTableHandler ships the check of tableExists,then it will block
> until deletetable finishs, then CreateTableHandler will set zk enabling, and
> find no data in meta:
> regionsInMeta = MetaReader.getTableRegions(this.ct, tableName, true);
> int countOfRegionsInTable = regionsInMeta.size();
> npe will be throwed here. And we could not create the same table anymore.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6588) enable table throws npe and leaves trash in zk in competition with delete table
[
https://issues.apache.org/jira/browse/HBASE-6588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13436600#comment-13436600
]
Zhou wenjian commented on HBASE-6588:
-
@ramkrishna.s.vasudevan
thanks for your review.
I did miss the throws clause.
update in v3.
> enable table throws npe and leaves trash in zk in competition with delete
> table
> ---
>
> Key: HBASE-6588
> URL: https://issues.apache.org/jira/browse/HBASE-6588
> Project: HBase
> Issue Type: Bug
>Affects Versions: 0.94.0
>Reporter: Zhou wenjian
> Fix For: 0.94.2
>
> Attachments: HBASE-6588-trunk.patch, HBASE-6588-trunk-v2.patch,
> HBASE-6588-trunk-v3.patch
>
>
> 2012-08-15 19:23:36,178 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Creating scanner over .META. starting at key 'test,,'
> 2012-08-15 19:23:36,178 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Advancing internal scanner to startKey at 'test,,'
> 2012-08-15 19:24:09,180 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Creating scanner over .META. starting at key ''
> 2012-08-15 19:24:09,180 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Advancing internal scanner to startKey at ''
> 2012-08-15 19:24:09,183 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Finished with scanning at {NAME => '.META.,,1', STARTKEY => '', ENDKEY => '',
> ENCODED => 1028785192,}
> 2012-08-15 19:24:09,183 DEBUG org.apache.hadoop.hbase.master.CatalogJanitor:
> Scanned 2 catalog row(s) and gc'd 0 unreferenced parent region(s)
> 2012-08-15 19:25:12,260 DEBUG
> org.apache.hadoop.hbase.master.handler.DeleteTableHandler: Deleting region
> test,,1345029764571.d1e24b251ca6286c840a9a5f571b7db1. from META and FS
> 2012-08-15 19:25:12,263 INFO org.apache.hadoop.hbase.catalog.MetaEditor:
> Deleted region test,,1345029764571.d1e24b251ca6286c840a9a5f571b7db1. from META
> 2012-08-15 19:25:12,265 INFO
> org.apache.hadoop.hbase.master.handler.EnableTableHandler: Attemping to
> enable the table test
> 2012-08-15 19:25:12,265 WARN org.apache.hadoop.hbase.zookeeper.ZKTable:
> Moving table test state to enabling but was not first in disabled state: null
> 2012-08-15 19:25:12,267 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Creating scanner over .META. starting at key 'test,,'
> 2012-08-15 19:25:12,267 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Advancing internal scanner to startKey at 'test,,'
> 2012-08-15 19:25:12,270 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Finished with scanning at {NAME => '.META.,,1', STARTKEY => '', ENDKEY => '',
> ENCODED => 1028785192,}
> 2012-08-15 19:25:12,270 ERROR org.apache.hadoop.hbase.executor.EventHandler:
> Caught throwable while processing event C_M_ENABLE_TABLE
> java.lang.NullPointerException
> at
> org.apache.hadoop.hbase.master.handler.EnableTableHandler.handleEnableTable(EnableTableHandler.java:116)
> at
> org.apache.hadoop.hbase.master.handler.EnableTableHandler.process(EnableTableHandler.java:97)
> at
> org.apache.hadoop.hbase.executor.EventHandler.run(EventHandler.java:169)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:662)
> table is disabled now, then we enable and delete the table at the same time.
> Since the thread num of MASTER_TABLE_OPERATIONS is 1 by default. The two
> operations are serial in master.Before deletetable deletes all the regions in
> meta, CreateTableHandler ships the check of tableExists,then it will block
> until deletetable finishs, then CreateTableHandler will set zk enabling, and
> find no data in meta:
> regionsInMeta = MetaReader.getTableRegions(this.ct, tableName, true);
> int countOfRegionsInTable = regionsInMeta.size();
> npe will be throwed here. And we could not create the same table anymore.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-6588) enable table throws npe and leaves trash in zk in competition with delete table
[
https://issues.apache.org/jira/browse/HBASE-6588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhou wenjian updated HBASE-6588:
Attachment: HBASE-6588-trunk-v3.patch
> enable table throws npe and leaves trash in zk in competition with delete
> table
> ---
>
> Key: HBASE-6588
> URL: https://issues.apache.org/jira/browse/HBASE-6588
> Project: HBase
> Issue Type: Bug
>Affects Versions: 0.94.0
>Reporter: Zhou wenjian
> Fix For: 0.94.2
>
> Attachments: HBASE-6588-trunk.patch, HBASE-6588-trunk-v2.patch,
> HBASE-6588-trunk-v3.patch
>
>
> 2012-08-15 19:23:36,178 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Creating scanner over .META. starting at key 'test,,'
> 2012-08-15 19:23:36,178 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Advancing internal scanner to startKey at 'test,,'
> 2012-08-15 19:24:09,180 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Creating scanner over .META. starting at key ''
> 2012-08-15 19:24:09,180 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Advancing internal scanner to startKey at ''
> 2012-08-15 19:24:09,183 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Finished with scanning at {NAME => '.META.,,1', STARTKEY => '', ENDKEY => '',
> ENCODED => 1028785192,}
> 2012-08-15 19:24:09,183 DEBUG org.apache.hadoop.hbase.master.CatalogJanitor:
> Scanned 2 catalog row(s) and gc'd 0 unreferenced parent region(s)
> 2012-08-15 19:25:12,260 DEBUG
> org.apache.hadoop.hbase.master.handler.DeleteTableHandler: Deleting region
> test,,1345029764571.d1e24b251ca6286c840a9a5f571b7db1. from META and FS
> 2012-08-15 19:25:12,263 INFO org.apache.hadoop.hbase.catalog.MetaEditor:
> Deleted region test,,1345029764571.d1e24b251ca6286c840a9a5f571b7db1. from META
> 2012-08-15 19:25:12,265 INFO
> org.apache.hadoop.hbase.master.handler.EnableTableHandler: Attemping to
> enable the table test
> 2012-08-15 19:25:12,265 WARN org.apache.hadoop.hbase.zookeeper.ZKTable:
> Moving table test state to enabling but was not first in disabled state: null
> 2012-08-15 19:25:12,267 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Creating scanner over .META. starting at key 'test,,'
> 2012-08-15 19:25:12,267 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Advancing internal scanner to startKey at 'test,,'
> 2012-08-15 19:25:12,270 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Finished with scanning at {NAME => '.META.,,1', STARTKEY => '', ENDKEY => '',
> ENCODED => 1028785192,}
> 2012-08-15 19:25:12,270 ERROR org.apache.hadoop.hbase.executor.EventHandler:
> Caught throwable while processing event C_M_ENABLE_TABLE
> java.lang.NullPointerException
> at
> org.apache.hadoop.hbase.master.handler.EnableTableHandler.handleEnableTable(EnableTableHandler.java:116)
> at
> org.apache.hadoop.hbase.master.handler.EnableTableHandler.process(EnableTableHandler.java:97)
> at
> org.apache.hadoop.hbase.executor.EventHandler.run(EventHandler.java:169)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:662)
> table is disabled now, then we enable and delete the table at the same time.
> Since the thread num of MASTER_TABLE_OPERATIONS is 1 by default. The two
> operations are serial in master.Before deletetable deletes all the regions in
> meta, CreateTableHandler ships the check of tableExists,then it will block
> until deletetable finishs, then CreateTableHandler will set zk enabling, and
> find no data in meta:
> regionsInMeta = MetaReader.getTableRegions(this.ct, tableName, true);
> int countOfRegionsInTable = regionsInMeta.size();
> npe will be throwed here. And we could not create the same table anymore.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-6473) deleted table is not deleted completely, some region may be still online
[
https://issues.apache.org/jira/browse/HBASE-6473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhou wenjian updated HBASE-6473:
Attachment: HBASE-6473-trunk-v3.patch
> deleted table is not deleted completely, some region may be still online
>
>
> Key: HBASE-6473
> URL: https://issues.apache.org/jira/browse/HBASE-6473
> Project: HBase
> Issue Type: Bug
>Affects Versions: 0.94.0
>Reporter: zhou wenjian
> Fix For: 0.96.0, 0.94.2
>
> Attachments: HBASE-6473-trunk.patch, HBASE-6473-trunk-v2.patch,
> HBASE-6473-trunk-v3.patch
>
>
> consider such Scenario:
> we have a table called T1, which has 1 regions: A
> 1. move A from rs1 to rs2,and A is now closed
> 2. disable T1,
> 3. delete T1.
> when we disable T1, disable handler will just set the zk to disabled and A
> will still be assigned. when Ais opened, A in transition will be clean out.
> At that time, Deletetable found it is safe to delete all regions and table in
> meta and fs , it will also delete the zk node of T1.
> {code}
> while (System.currentTimeMillis() < done) {
> AssignmentManager.RegionState rs = am.isRegionInTransition(region);
> if (rs == null) break;
> Threads.sleep(waitingTimeForEvents);
> LOG.debug("Waiting on region to clear regions in transition; " + rs);
> }
> if (am.isRegionInTransition(region) != null) {
> throw new IOException("Waited hbase.master.wait.on.region (" +
> waitTime + "ms) for region to leave region " +
> region.getRegionNameAsString() + " in transitions");
> }
> {code}
> however A is still being unassigned, when it finished closed the A,it finds
> that the disabled state in zk is deleted, and then A will be assigned again.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6473) deleted table is not deleted completely, some region may be still online
[
https://issues.apache.org/jira/browse/HBASE-6473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13436543#comment-13436543
]
Zhou wenjian commented on HBASE-6473:
-
Our cluster online has encounter the bug.
After disable and delete then create the same table, We found the region in
deleted table is still on the meta with info:regioninfo missed. HBCK seems
drawing a blank on it, We have to clean the region invalid from the meta
manually
> deleted table is not deleted completely, some region may be still online
>
>
> Key: HBASE-6473
> URL: https://issues.apache.org/jira/browse/HBASE-6473
> Project: HBase
> Issue Type: Bug
>Affects Versions: 0.94.0
>Reporter: zhou wenjian
> Fix For: 0.96.0, 0.94.2
>
> Attachments: HBASE-6473-trunk.patch, HBASE-6473-trunk-v2.patch
>
>
> consider such Scenario:
> we have a table called T1, which has 1 regions: A
> 1. move A from rs1 to rs2,and A is now closed
> 2. disable T1,
> 3. delete T1.
> when we disable T1, disable handler will just set the zk to disabled and A
> will still be assigned. when Ais opened, A in transition will be clean out.
> At that time, Deletetable found it is safe to delete all regions and table in
> meta and fs , it will also delete the zk node of T1.
> {code}
> while (System.currentTimeMillis() < done) {
> AssignmentManager.RegionState rs = am.isRegionInTransition(region);
> if (rs == null) break;
> Threads.sleep(waitingTimeForEvents);
> LOG.debug("Waiting on region to clear regions in transition; " + rs);
> }
> if (am.isRegionInTransition(region) != null) {
> throw new IOException("Waited hbase.master.wait.on.region (" +
> waitTime + "ms) for region to leave region " +
> region.getRegionNameAsString() + " in transitions");
> }
> {code}
> however A is still being unassigned, when it finished closed the A,it finds
> that the disabled state in zk is deleted, and then A will be assigned again.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6588) enable table throws npe and leaves trash in zk in competition with delete table
[
https://issues.apache.org/jira/browse/HBASE-6588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13436539#comment-13436539
]
Zhou wenjian commented on HBASE-6588:
-
patch v2 for trunk with testcase . Please review and provide your
comments/suggestions
> enable table throws npe and leaves trash in zk in competition with delete
> table
> ---
>
> Key: HBASE-6588
> URL: https://issues.apache.org/jira/browse/HBASE-6588
> Project: HBase
> Issue Type: Bug
>Affects Versions: 0.94.0
>Reporter: Zhou wenjian
> Fix For: 0.94.2
>
> Attachments: HBASE-6588-trunk.patch, HBASE-6588-trunk-v2.patch
>
>
> 2012-08-15 19:23:36,178 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Creating scanner over .META. starting at key 'test,,'
> 2012-08-15 19:23:36,178 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Advancing internal scanner to startKey at 'test,,'
> 2012-08-15 19:24:09,180 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Creating scanner over .META. starting at key ''
> 2012-08-15 19:24:09,180 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Advancing internal scanner to startKey at ''
> 2012-08-15 19:24:09,183 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Finished with scanning at {NAME => '.META.,,1', STARTKEY => '', ENDKEY => '',
> ENCODED => 1028785192,}
> 2012-08-15 19:24:09,183 DEBUG org.apache.hadoop.hbase.master.CatalogJanitor:
> Scanned 2 catalog row(s) and gc'd 0 unreferenced parent region(s)
> 2012-08-15 19:25:12,260 DEBUG
> org.apache.hadoop.hbase.master.handler.DeleteTableHandler: Deleting region
> test,,1345029764571.d1e24b251ca6286c840a9a5f571b7db1. from META and FS
> 2012-08-15 19:25:12,263 INFO org.apache.hadoop.hbase.catalog.MetaEditor:
> Deleted region test,,1345029764571.d1e24b251ca6286c840a9a5f571b7db1. from META
> 2012-08-15 19:25:12,265 INFO
> org.apache.hadoop.hbase.master.handler.EnableTableHandler: Attemping to
> enable the table test
> 2012-08-15 19:25:12,265 WARN org.apache.hadoop.hbase.zookeeper.ZKTable:
> Moving table test state to enabling but was not first in disabled state: null
> 2012-08-15 19:25:12,267 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Creating scanner over .META. starting at key 'test,,'
> 2012-08-15 19:25:12,267 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Advancing internal scanner to startKey at 'test,,'
> 2012-08-15 19:25:12,270 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Finished with scanning at {NAME => '.META.,,1', STARTKEY => '', ENDKEY => '',
> ENCODED => 1028785192,}
> 2012-08-15 19:25:12,270 ERROR org.apache.hadoop.hbase.executor.EventHandler:
> Caught throwable while processing event C_M_ENABLE_TABLE
> java.lang.NullPointerException
> at
> org.apache.hadoop.hbase.master.handler.EnableTableHandler.handleEnableTable(EnableTableHandler.java:116)
> at
> org.apache.hadoop.hbase.master.handler.EnableTableHandler.process(EnableTableHandler.java:97)
> at
> org.apache.hadoop.hbase.executor.EventHandler.run(EventHandler.java:169)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:662)
> table is disabled now, then we enable and delete the table at the same time.
> Since the thread num of MASTER_TABLE_OPERATIONS is 1 by default. The two
> operations are serial in master.Before deletetable deletes all the regions in
> meta, CreateTableHandler ships the check of tableExists,then it will block
> until deletetable finishs, then CreateTableHandler will set zk enabling, and
> find no data in meta:
> regionsInMeta = MetaReader.getTableRegions(this.ct, tableName, true);
> int countOfRegionsInTable = regionsInMeta.size();
> npe will be throwed here. And we could not create the same table anymore.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-6588) enable table throws npe and leaves trash in zk in competition with delete table
[
https://issues.apache.org/jira/browse/HBASE-6588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhou wenjian updated HBASE-6588:
Attachment: HBASE-6588-trunk-v2.patch
> enable table throws npe and leaves trash in zk in competition with delete
> table
> ---
>
> Key: HBASE-6588
> URL: https://issues.apache.org/jira/browse/HBASE-6588
> Project: HBase
> Issue Type: Bug
>Affects Versions: 0.94.0
>Reporter: Zhou wenjian
> Fix For: 0.94.2
>
> Attachments: HBASE-6588-trunk.patch, HBASE-6588-trunk-v2.patch
>
>
> 2012-08-15 19:23:36,178 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Creating scanner over .META. starting at key 'test,,'
> 2012-08-15 19:23:36,178 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Advancing internal scanner to startKey at 'test,,'
> 2012-08-15 19:24:09,180 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Creating scanner over .META. starting at key ''
> 2012-08-15 19:24:09,180 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Advancing internal scanner to startKey at ''
> 2012-08-15 19:24:09,183 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Finished with scanning at {NAME => '.META.,,1', STARTKEY => '', ENDKEY => '',
> ENCODED => 1028785192,}
> 2012-08-15 19:24:09,183 DEBUG org.apache.hadoop.hbase.master.CatalogJanitor:
> Scanned 2 catalog row(s) and gc'd 0 unreferenced parent region(s)
> 2012-08-15 19:25:12,260 DEBUG
> org.apache.hadoop.hbase.master.handler.DeleteTableHandler: Deleting region
> test,,1345029764571.d1e24b251ca6286c840a9a5f571b7db1. from META and FS
> 2012-08-15 19:25:12,263 INFO org.apache.hadoop.hbase.catalog.MetaEditor:
> Deleted region test,,1345029764571.d1e24b251ca6286c840a9a5f571b7db1. from META
> 2012-08-15 19:25:12,265 INFO
> org.apache.hadoop.hbase.master.handler.EnableTableHandler: Attemping to
> enable the table test
> 2012-08-15 19:25:12,265 WARN org.apache.hadoop.hbase.zookeeper.ZKTable:
> Moving table test state to enabling but was not first in disabled state: null
> 2012-08-15 19:25:12,267 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Creating scanner over .META. starting at key 'test,,'
> 2012-08-15 19:25:12,267 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Advancing internal scanner to startKey at 'test,,'
> 2012-08-15 19:25:12,270 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Finished with scanning at {NAME => '.META.,,1', STARTKEY => '', ENDKEY => '',
> ENCODED => 1028785192,}
> 2012-08-15 19:25:12,270 ERROR org.apache.hadoop.hbase.executor.EventHandler:
> Caught throwable while processing event C_M_ENABLE_TABLE
> java.lang.NullPointerException
> at
> org.apache.hadoop.hbase.master.handler.EnableTableHandler.handleEnableTable(EnableTableHandler.java:116)
> at
> org.apache.hadoop.hbase.master.handler.EnableTableHandler.process(EnableTableHandler.java:97)
> at
> org.apache.hadoop.hbase.executor.EventHandler.run(EventHandler.java:169)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:662)
> table is disabled now, then we enable and delete the table at the same time.
> Since the thread num of MASTER_TABLE_OPERATIONS is 1 by default. The two
> operations are serial in master.Before deletetable deletes all the regions in
> meta, CreateTableHandler ships the check of tableExists,then it will block
> until deletetable finishs, then CreateTableHandler will set zk enabling, and
> find no data in meta:
> regionsInMeta = MetaReader.getTableRegions(this.ct, tableName, true);
> int countOfRegionsInTable = regionsInMeta.size();
> npe will be throwed here. And we could not create the same table anymore.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-6588) enable table throws npe and leaves trash in zk in competition with delete table
[
https://issues.apache.org/jira/browse/HBASE-6588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhou wenjian updated HBASE-6588:
Attachment: (was: HBASE-6588-trunk-v2.patch)
> enable table throws npe and leaves trash in zk in competition with delete
> table
> ---
>
> Key: HBASE-6588
> URL: https://issues.apache.org/jira/browse/HBASE-6588
> Project: HBase
> Issue Type: Bug
>Affects Versions: 0.94.0
>Reporter: Zhou wenjian
> Fix For: 0.94.2
>
> Attachments: HBASE-6588-trunk.patch
>
>
> 2012-08-15 19:23:36,178 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Creating scanner over .META. starting at key 'test,,'
> 2012-08-15 19:23:36,178 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Advancing internal scanner to startKey at 'test,,'
> 2012-08-15 19:24:09,180 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Creating scanner over .META. starting at key ''
> 2012-08-15 19:24:09,180 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Advancing internal scanner to startKey at ''
> 2012-08-15 19:24:09,183 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Finished with scanning at {NAME => '.META.,,1', STARTKEY => '', ENDKEY => '',
> ENCODED => 1028785192,}
> 2012-08-15 19:24:09,183 DEBUG org.apache.hadoop.hbase.master.CatalogJanitor:
> Scanned 2 catalog row(s) and gc'd 0 unreferenced parent region(s)
> 2012-08-15 19:25:12,260 DEBUG
> org.apache.hadoop.hbase.master.handler.DeleteTableHandler: Deleting region
> test,,1345029764571.d1e24b251ca6286c840a9a5f571b7db1. from META and FS
> 2012-08-15 19:25:12,263 INFO org.apache.hadoop.hbase.catalog.MetaEditor:
> Deleted region test,,1345029764571.d1e24b251ca6286c840a9a5f571b7db1. from META
> 2012-08-15 19:25:12,265 INFO
> org.apache.hadoop.hbase.master.handler.EnableTableHandler: Attemping to
> enable the table test
> 2012-08-15 19:25:12,265 WARN org.apache.hadoop.hbase.zookeeper.ZKTable:
> Moving table test state to enabling but was not first in disabled state: null
> 2012-08-15 19:25:12,267 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Creating scanner over .META. starting at key 'test,,'
> 2012-08-15 19:25:12,267 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Advancing internal scanner to startKey at 'test,,'
> 2012-08-15 19:25:12,270 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Finished with scanning at {NAME => '.META.,,1', STARTKEY => '', ENDKEY => '',
> ENCODED => 1028785192,}
> 2012-08-15 19:25:12,270 ERROR org.apache.hadoop.hbase.executor.EventHandler:
> Caught throwable while processing event C_M_ENABLE_TABLE
> java.lang.NullPointerException
> at
> org.apache.hadoop.hbase.master.handler.EnableTableHandler.handleEnableTable(EnableTableHandler.java:116)
> at
> org.apache.hadoop.hbase.master.handler.EnableTableHandler.process(EnableTableHandler.java:97)
> at
> org.apache.hadoop.hbase.executor.EventHandler.run(EventHandler.java:169)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:662)
> table is disabled now, then we enable and delete the table at the same time.
> Since the thread num of MASTER_TABLE_OPERATIONS is 1 by default. The two
> operations are serial in master.Before deletetable deletes all the regions in
> meta, CreateTableHandler ships the check of tableExists,then it will block
> until deletetable finishs, then CreateTableHandler will set zk enabling, and
> find no data in meta:
> regionsInMeta = MetaReader.getTableRegions(this.ct, tableName, true);
> int countOfRegionsInTable = regionsInMeta.size();
> npe will be throwed here. And we could not create the same table anymore.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-6588) enable table throws npe and leaves trash in zk in competition with delete table
[
https://issues.apache.org/jira/browse/HBASE-6588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhou wenjian updated HBASE-6588:
Attachment: (was: HBASE-6588-trunk-v2.patch)
> enable table throws npe and leaves trash in zk in competition with delete
> table
> ---
>
> Key: HBASE-6588
> URL: https://issues.apache.org/jira/browse/HBASE-6588
> Project: HBase
> Issue Type: Bug
>Affects Versions: 0.94.0
>Reporter: Zhou wenjian
> Fix For: 0.94.2
>
> Attachments: HBASE-6588-trunk.patch
>
>
> 2012-08-15 19:23:36,178 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Creating scanner over .META. starting at key 'test,,'
> 2012-08-15 19:23:36,178 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Advancing internal scanner to startKey at 'test,,'
> 2012-08-15 19:24:09,180 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Creating scanner over .META. starting at key ''
> 2012-08-15 19:24:09,180 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Advancing internal scanner to startKey at ''
> 2012-08-15 19:24:09,183 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Finished with scanning at {NAME => '.META.,,1', STARTKEY => '', ENDKEY => '',
> ENCODED => 1028785192,}
> 2012-08-15 19:24:09,183 DEBUG org.apache.hadoop.hbase.master.CatalogJanitor:
> Scanned 2 catalog row(s) and gc'd 0 unreferenced parent region(s)
> 2012-08-15 19:25:12,260 DEBUG
> org.apache.hadoop.hbase.master.handler.DeleteTableHandler: Deleting region
> test,,1345029764571.d1e24b251ca6286c840a9a5f571b7db1. from META and FS
> 2012-08-15 19:25:12,263 INFO org.apache.hadoop.hbase.catalog.MetaEditor:
> Deleted region test,,1345029764571.d1e24b251ca6286c840a9a5f571b7db1. from META
> 2012-08-15 19:25:12,265 INFO
> org.apache.hadoop.hbase.master.handler.EnableTableHandler: Attemping to
> enable the table test
> 2012-08-15 19:25:12,265 WARN org.apache.hadoop.hbase.zookeeper.ZKTable:
> Moving table test state to enabling but was not first in disabled state: null
> 2012-08-15 19:25:12,267 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Creating scanner over .META. starting at key 'test,,'
> 2012-08-15 19:25:12,267 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Advancing internal scanner to startKey at 'test,,'
> 2012-08-15 19:25:12,270 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Finished with scanning at {NAME => '.META.,,1', STARTKEY => '', ENDKEY => '',
> ENCODED => 1028785192,}
> 2012-08-15 19:25:12,270 ERROR org.apache.hadoop.hbase.executor.EventHandler:
> Caught throwable while processing event C_M_ENABLE_TABLE
> java.lang.NullPointerException
> at
> org.apache.hadoop.hbase.master.handler.EnableTableHandler.handleEnableTable(EnableTableHandler.java:116)
> at
> org.apache.hadoop.hbase.master.handler.EnableTableHandler.process(EnableTableHandler.java:97)
> at
> org.apache.hadoop.hbase.executor.EventHandler.run(EventHandler.java:169)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:662)
> table is disabled now, then we enable and delete the table at the same time.
> Since the thread num of MASTER_TABLE_OPERATIONS is 1 by default. The two
> operations are serial in master.Before deletetable deletes all the regions in
> meta, CreateTableHandler ships the check of tableExists,then it will block
> until deletetable finishs, then CreateTableHandler will set zk enabling, and
> find no data in meta:
> regionsInMeta = MetaReader.getTableRegions(this.ct, tableName, true);
> int countOfRegionsInTable = regionsInMeta.size();
> npe will be throwed here. And we could not create the same table anymore.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-6588) enable table throws npe and leaves trash in zk in competition with delete table
[
https://issues.apache.org/jira/browse/HBASE-6588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhou wenjian updated HBASE-6588:
Attachment: HBASE-6588-trunk-v2.patch
HBASE-6588-trunk-v2.patch
> enable table throws npe and leaves trash in zk in competition with delete
> table
> ---
>
> Key: HBASE-6588
> URL: https://issues.apache.org/jira/browse/HBASE-6588
> Project: HBase
> Issue Type: Bug
>Affects Versions: 0.94.0
>Reporter: Zhou wenjian
> Fix For: 0.94.2
>
> Attachments: HBASE-6588-trunk.patch
>
>
> 2012-08-15 19:23:36,178 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Creating scanner over .META. starting at key 'test,,'
> 2012-08-15 19:23:36,178 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Advancing internal scanner to startKey at 'test,,'
> 2012-08-15 19:24:09,180 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Creating scanner over .META. starting at key ''
> 2012-08-15 19:24:09,180 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Advancing internal scanner to startKey at ''
> 2012-08-15 19:24:09,183 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Finished with scanning at {NAME => '.META.,,1', STARTKEY => '', ENDKEY => '',
> ENCODED => 1028785192,}
> 2012-08-15 19:24:09,183 DEBUG org.apache.hadoop.hbase.master.CatalogJanitor:
> Scanned 2 catalog row(s) and gc'd 0 unreferenced parent region(s)
> 2012-08-15 19:25:12,260 DEBUG
> org.apache.hadoop.hbase.master.handler.DeleteTableHandler: Deleting region
> test,,1345029764571.d1e24b251ca6286c840a9a5f571b7db1. from META and FS
> 2012-08-15 19:25:12,263 INFO org.apache.hadoop.hbase.catalog.MetaEditor:
> Deleted region test,,1345029764571.d1e24b251ca6286c840a9a5f571b7db1. from META
> 2012-08-15 19:25:12,265 INFO
> org.apache.hadoop.hbase.master.handler.EnableTableHandler: Attemping to
> enable the table test
> 2012-08-15 19:25:12,265 WARN org.apache.hadoop.hbase.zookeeper.ZKTable:
> Moving table test state to enabling but was not first in disabled state: null
> 2012-08-15 19:25:12,267 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Creating scanner over .META. starting at key 'test,,'
> 2012-08-15 19:25:12,267 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Advancing internal scanner to startKey at 'test,,'
> 2012-08-15 19:25:12,270 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Finished with scanning at {NAME => '.META.,,1', STARTKEY => '', ENDKEY => '',
> ENCODED => 1028785192,}
> 2012-08-15 19:25:12,270 ERROR org.apache.hadoop.hbase.executor.EventHandler:
> Caught throwable while processing event C_M_ENABLE_TABLE
> java.lang.NullPointerException
> at
> org.apache.hadoop.hbase.master.handler.EnableTableHandler.handleEnableTable(EnableTableHandler.java:116)
> at
> org.apache.hadoop.hbase.master.handler.EnableTableHandler.process(EnableTableHandler.java:97)
> at
> org.apache.hadoop.hbase.executor.EventHandler.run(EventHandler.java:169)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:662)
> table is disabled now, then we enable and delete the table at the same time.
> Since the thread num of MASTER_TABLE_OPERATIONS is 1 by default. The two
> operations are serial in master.Before deletetable deletes all the regions in
> meta, CreateTableHandler ships the check of tableExists,then it will block
> until deletetable finishs, then CreateTableHandler will set zk enabling, and
> find no data in meta:
> regionsInMeta = MetaReader.getTableRegions(this.ct, tableName, true);
> int countOfRegionsInTable = regionsInMeta.size();
> npe will be throwed here. And we could not create the same table anymore.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6537) Balancer compete with disable table will lead to cluster inconsistent
[ https://issues.apache.org/jira/browse/HBASE-6537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13435771#comment-13435771 ] Zhou wenjian commented on HBASE-6537: - @ramkrishna.s.vasudevan We can shutdown the window between RIT and regions with the change, lots of problems may be caused by it. Since truck has made the function synchronized, the change in regionOffline does no harm. > Balancer compete with disable table will lead to cluster inconsistent > -- > > Key: HBASE-6537 > URL: https://issues.apache.org/jira/browse/HBASE-6537 > Project: HBase > Issue Type: Bug > Components: master >Affects Versions: 0.94.0 >Reporter: Zhou wenjian > Fix For: 0.94.2 > > Attachments: HBASE-6537-94.patch, HBASE-6537-94-v2.patch, > HBASE-6537-trunk.patch > > > Appear in 94. trunk is ok for the issue > Balancer will collect the regionplans to move(unassign and then assign). > before unassign, disable table appears, > after close the region in rs, master will delete the znode, romove region > from RIT, > and then clean the region from the online regions. > During romoving region from RIT and cleaning out the region from the online > regions. > balancer begins to unassign, it will get a NotServingRegionException and if > the table is disabling, it will deal with the state in master and delete the > znode . However the table is disabled now, so the RIT and znode will remain. > TimeoutMonitor draws a blank on it. > It will hold back enabling the table or balancer unless restart -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6588) enable table throws npe and leaves trash in zk in competition with delete table
[
https://issues.apache.org/jira/browse/HBASE-6588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13435716#comment-13435716
]
zhou wenjian commented on HBASE-6588:
-
@Ted
i was doing some tests on table balancer, disable and then enable it.
howerver i mistake using drop table instead of enable,
Ctrl + c is immediately sent, and enable table is also closed behind, then i
found table is deleted, but i couldn't create it anymore. So i reproduce the
scenario.
> enable table throws npe and leaves trash in zk in competition with delete
> table
> ---
>
> Key: HBASE-6588
> URL: https://issues.apache.org/jira/browse/HBASE-6588
> Project: HBase
> Issue Type: Bug
>Affects Versions: 0.94.0
>Reporter: Zhou wenjian
> Fix For: 0.94.2
>
> Attachments: HBASE-6588-trunk.patch
>
>
> 2012-08-15 19:23:36,178 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Creating scanner over .META. starting at key 'test,,'
> 2012-08-15 19:23:36,178 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Advancing internal scanner to startKey at 'test,,'
> 2012-08-15 19:24:09,180 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Creating scanner over .META. starting at key ''
> 2012-08-15 19:24:09,180 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Advancing internal scanner to startKey at ''
> 2012-08-15 19:24:09,183 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Finished with scanning at {NAME => '.META.,,1', STARTKEY => '', ENDKEY => '',
> ENCODED => 1028785192,}
> 2012-08-15 19:24:09,183 DEBUG org.apache.hadoop.hbase.master.CatalogJanitor:
> Scanned 2 catalog row(s) and gc'd 0 unreferenced parent region(s)
> 2012-08-15 19:25:12,260 DEBUG
> org.apache.hadoop.hbase.master.handler.DeleteTableHandler: Deleting region
> test,,1345029764571.d1e24b251ca6286c840a9a5f571b7db1. from META and FS
> 2012-08-15 19:25:12,263 INFO org.apache.hadoop.hbase.catalog.MetaEditor:
> Deleted region test,,1345029764571.d1e24b251ca6286c840a9a5f571b7db1. from META
> 2012-08-15 19:25:12,265 INFO
> org.apache.hadoop.hbase.master.handler.EnableTableHandler: Attemping to
> enable the table test
> 2012-08-15 19:25:12,265 WARN org.apache.hadoop.hbase.zookeeper.ZKTable:
> Moving table test state to enabling but was not first in disabled state: null
> 2012-08-15 19:25:12,267 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Creating scanner over .META. starting at key 'test,,'
> 2012-08-15 19:25:12,267 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Advancing internal scanner to startKey at 'test,,'
> 2012-08-15 19:25:12,270 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Finished with scanning at {NAME => '.META.,,1', STARTKEY => '', ENDKEY => '',
> ENCODED => 1028785192,}
> 2012-08-15 19:25:12,270 ERROR org.apache.hadoop.hbase.executor.EventHandler:
> Caught throwable while processing event C_M_ENABLE_TABLE
> java.lang.NullPointerException
> at
> org.apache.hadoop.hbase.master.handler.EnableTableHandler.handleEnableTable(EnableTableHandler.java:116)
> at
> org.apache.hadoop.hbase.master.handler.EnableTableHandler.process(EnableTableHandler.java:97)
> at
> org.apache.hadoop.hbase.executor.EventHandler.run(EventHandler.java:169)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:662)
> table is disabled now, then we enable and delete the table at the same time.
> Since the thread num of MASTER_TABLE_OPERATIONS is 1 by default. The two
> operations are serial in master.Before deletetable deletes all the regions in
> meta, CreateTableHandler ships the check of tableExists,then it will block
> until deletetable finishs, then CreateTableHandler will set zk enabling, and
> find no data in meta:
> regionsInMeta = MetaReader.getTableRegions(this.ct, tableName, true);
> int countOfRegionsInTable = regionsInMeta.size();
> npe will be throwed here. And we could not create the same table anymore.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-6588) enable table throws npe and leaves trash in zk in competition with delete table
[
https://issues.apache.org/jira/browse/HBASE-6588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhou wenjian updated HBASE-6588:
Status: Patch Available (was: Open)
> enable table throws npe and leaves trash in zk in competition with delete
> table
> ---
>
> Key: HBASE-6588
> URL: https://issues.apache.org/jira/browse/HBASE-6588
> Project: HBase
> Issue Type: Bug
>Affects Versions: 0.94.0
>Reporter: Zhou wenjian
> Fix For: 0.94.2
>
> Attachments: HBASE-6588-trunk.patch
>
>
> 2012-08-15 19:23:36,178 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Creating scanner over .META. starting at key 'test,,'
> 2012-08-15 19:23:36,178 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Advancing internal scanner to startKey at 'test,,'
> 2012-08-15 19:24:09,180 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Creating scanner over .META. starting at key ''
> 2012-08-15 19:24:09,180 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Advancing internal scanner to startKey at ''
> 2012-08-15 19:24:09,183 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Finished with scanning at {NAME => '.META.,,1', STARTKEY => '', ENDKEY => '',
> ENCODED => 1028785192,}
> 2012-08-15 19:24:09,183 DEBUG org.apache.hadoop.hbase.master.CatalogJanitor:
> Scanned 2 catalog row(s) and gc'd 0 unreferenced parent region(s)
> 2012-08-15 19:25:12,260 DEBUG
> org.apache.hadoop.hbase.master.handler.DeleteTableHandler: Deleting region
> test,,1345029764571.d1e24b251ca6286c840a9a5f571b7db1. from META and FS
> 2012-08-15 19:25:12,263 INFO org.apache.hadoop.hbase.catalog.MetaEditor:
> Deleted region test,,1345029764571.d1e24b251ca6286c840a9a5f571b7db1. from META
> 2012-08-15 19:25:12,265 INFO
> org.apache.hadoop.hbase.master.handler.EnableTableHandler: Attemping to
> enable the table test
> 2012-08-15 19:25:12,265 WARN org.apache.hadoop.hbase.zookeeper.ZKTable:
> Moving table test state to enabling but was not first in disabled state: null
> 2012-08-15 19:25:12,267 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Creating scanner over .META. starting at key 'test,,'
> 2012-08-15 19:25:12,267 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Advancing internal scanner to startKey at 'test,,'
> 2012-08-15 19:25:12,270 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Finished with scanning at {NAME => '.META.,,1', STARTKEY => '', ENDKEY => '',
> ENCODED => 1028785192,}
> 2012-08-15 19:25:12,270 ERROR org.apache.hadoop.hbase.executor.EventHandler:
> Caught throwable while processing event C_M_ENABLE_TABLE
> java.lang.NullPointerException
> at
> org.apache.hadoop.hbase.master.handler.EnableTableHandler.handleEnableTable(EnableTableHandler.java:116)
> at
> org.apache.hadoop.hbase.master.handler.EnableTableHandler.process(EnableTableHandler.java:97)
> at
> org.apache.hadoop.hbase.executor.EventHandler.run(EventHandler.java:169)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:662)
> table is disabled now, then we enable and delete the table at the same time.
> Since the thread num of MASTER_TABLE_OPERATIONS is 1 by default. The two
> operations are serial in master.Before deletetable deletes all the regions in
> meta, CreateTableHandler ships the check of tableExists,then it will block
> until deletetable finishs, then CreateTableHandler will set zk enabling, and
> find no data in meta:
> regionsInMeta = MetaReader.getTableRegions(this.ct, tableName, true);
> int countOfRegionsInTable = regionsInMeta.size();
> npe will be throwed here. And we could not create the same table anymore.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6588) enable table throws npe and leaves trash in zk in competition with delete table
[
https://issues.apache.org/jira/browse/HBASE-6588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13435010#comment-13435010
]
Zhou wenjian commented on HBASE-6588:
-
Submitted patch for trunk. Please review and provide your comments/suggestions
> enable table throws npe and leaves trash in zk in competition with delete
> table
> ---
>
> Key: HBASE-6588
> URL: https://issues.apache.org/jira/browse/HBASE-6588
> Project: HBase
> Issue Type: Bug
>Affects Versions: 0.94.0
>Reporter: Zhou wenjian
> Fix For: 0.94.2
>
> Attachments: HBASE-6588-trunk.patch
>
>
> 2012-08-15 19:23:36,178 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Creating scanner over .META. starting at key 'test,,'
> 2012-08-15 19:23:36,178 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Advancing internal scanner to startKey at 'test,,'
> 2012-08-15 19:24:09,180 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Creating scanner over .META. starting at key ''
> 2012-08-15 19:24:09,180 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Advancing internal scanner to startKey at ''
> 2012-08-15 19:24:09,183 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Finished with scanning at {NAME => '.META.,,1', STARTKEY => '', ENDKEY => '',
> ENCODED => 1028785192,}
> 2012-08-15 19:24:09,183 DEBUG org.apache.hadoop.hbase.master.CatalogJanitor:
> Scanned 2 catalog row(s) and gc'd 0 unreferenced parent region(s)
> 2012-08-15 19:25:12,260 DEBUG
> org.apache.hadoop.hbase.master.handler.DeleteTableHandler: Deleting region
> test,,1345029764571.d1e24b251ca6286c840a9a5f571b7db1. from META and FS
> 2012-08-15 19:25:12,263 INFO org.apache.hadoop.hbase.catalog.MetaEditor:
> Deleted region test,,1345029764571.d1e24b251ca6286c840a9a5f571b7db1. from META
> 2012-08-15 19:25:12,265 INFO
> org.apache.hadoop.hbase.master.handler.EnableTableHandler: Attemping to
> enable the table test
> 2012-08-15 19:25:12,265 WARN org.apache.hadoop.hbase.zookeeper.ZKTable:
> Moving table test state to enabling but was not first in disabled state: null
> 2012-08-15 19:25:12,267 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Creating scanner over .META. starting at key 'test,,'
> 2012-08-15 19:25:12,267 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Advancing internal scanner to startKey at 'test,,'
> 2012-08-15 19:25:12,270 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Finished with scanning at {NAME => '.META.,,1', STARTKEY => '', ENDKEY => '',
> ENCODED => 1028785192,}
> 2012-08-15 19:25:12,270 ERROR org.apache.hadoop.hbase.executor.EventHandler:
> Caught throwable while processing event C_M_ENABLE_TABLE
> java.lang.NullPointerException
> at
> org.apache.hadoop.hbase.master.handler.EnableTableHandler.handleEnableTable(EnableTableHandler.java:116)
> at
> org.apache.hadoop.hbase.master.handler.EnableTableHandler.process(EnableTableHandler.java:97)
> at
> org.apache.hadoop.hbase.executor.EventHandler.run(EventHandler.java:169)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:662)
> table is disabled now, then we enable and delete the table at the same time.
> Since the thread num of MASTER_TABLE_OPERATIONS is 1 by default. The two
> operations are serial in master.Before deletetable deletes all the regions in
> meta, CreateTableHandler ships the check of tableExists,then it will block
> until deletetable finishs, then CreateTableHandler will set zk enabling, and
> find no data in meta:
> regionsInMeta = MetaReader.getTableRegions(this.ct, tableName, true);
> int countOfRegionsInTable = regionsInMeta.size();
> npe will be throwed here. And we could not create the same table anymore.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-6588) enable table throws npe and leaves trash in zk in competition with delete table
[
https://issues.apache.org/jira/browse/HBASE-6588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhou wenjian updated HBASE-6588:
Attachment: HBASE-6588-trunk.patch
> enable table throws npe and leaves trash in zk in competition with delete
> table
> ---
>
> Key: HBASE-6588
> URL: https://issues.apache.org/jira/browse/HBASE-6588
> Project: HBase
> Issue Type: Bug
>Affects Versions: 0.94.0
>Reporter: Zhou wenjian
> Fix For: 0.94.2
>
> Attachments: HBASE-6588-trunk.patch
>
>
> 2012-08-15 19:23:36,178 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Creating scanner over .META. starting at key 'test,,'
> 2012-08-15 19:23:36,178 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Advancing internal scanner to startKey at 'test,,'
> 2012-08-15 19:24:09,180 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Creating scanner over .META. starting at key ''
> 2012-08-15 19:24:09,180 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Advancing internal scanner to startKey at ''
> 2012-08-15 19:24:09,183 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Finished with scanning at {NAME => '.META.,,1', STARTKEY => '', ENDKEY => '',
> ENCODED => 1028785192,}
> 2012-08-15 19:24:09,183 DEBUG org.apache.hadoop.hbase.master.CatalogJanitor:
> Scanned 2 catalog row(s) and gc'd 0 unreferenced parent region(s)
> 2012-08-15 19:25:12,260 DEBUG
> org.apache.hadoop.hbase.master.handler.DeleteTableHandler: Deleting region
> test,,1345029764571.d1e24b251ca6286c840a9a5f571b7db1. from META and FS
> 2012-08-15 19:25:12,263 INFO org.apache.hadoop.hbase.catalog.MetaEditor:
> Deleted region test,,1345029764571.d1e24b251ca6286c840a9a5f571b7db1. from META
> 2012-08-15 19:25:12,265 INFO
> org.apache.hadoop.hbase.master.handler.EnableTableHandler: Attemping to
> enable the table test
> 2012-08-15 19:25:12,265 WARN org.apache.hadoop.hbase.zookeeper.ZKTable:
> Moving table test state to enabling but was not first in disabled state: null
> 2012-08-15 19:25:12,267 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Creating scanner over .META. starting at key 'test,,'
> 2012-08-15 19:25:12,267 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Advancing internal scanner to startKey at 'test,,'
> 2012-08-15 19:25:12,270 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Finished with scanning at {NAME => '.META.,,1', STARTKEY => '', ENDKEY => '',
> ENCODED => 1028785192,}
> 2012-08-15 19:25:12,270 ERROR org.apache.hadoop.hbase.executor.EventHandler:
> Caught throwable while processing event C_M_ENABLE_TABLE
> java.lang.NullPointerException
> at
> org.apache.hadoop.hbase.master.handler.EnableTableHandler.handleEnableTable(EnableTableHandler.java:116)
> at
> org.apache.hadoop.hbase.master.handler.EnableTableHandler.process(EnableTableHandler.java:97)
> at
> org.apache.hadoop.hbase.executor.EventHandler.run(EventHandler.java:169)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:662)
> table is disabled now, then we enable and delete the table at the same time.
> Since the thread num of MASTER_TABLE_OPERATIONS is 1 by default. The two
> operations are serial in master.Before deletetable deletes all the regions in
> meta, CreateTableHandler ships the check of tableExists,then it will block
> until deletetable finishs, then CreateTableHandler will set zk enabling, and
> find no data in meta:
> regionsInMeta = MetaReader.getTableRegions(this.ct, tableName, true);
> int countOfRegionsInTable = regionsInMeta.size();
> npe will be throwed here. And we could not create the same table anymore.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6588) enable table throws npe and leaves trash in zk in competition with delete table
[
https://issues.apache.org/jira/browse/HBASE-6588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13434989#comment-13434989
]
Zhou wenjian commented on HBASE-6588:
-
needs delete the znode
> enable table throws npe and leaves trash in zk in competition with delete
> table
> ---
>
> Key: HBASE-6588
> URL: https://issues.apache.org/jira/browse/HBASE-6588
> Project: HBase
> Issue Type: Bug
>Affects Versions: 0.94.0
>Reporter: Zhou wenjian
> Fix For: 0.94.2
>
>
> 2012-08-15 19:23:36,178 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Creating scanner over .META. starting at key 'test,,'
> 2012-08-15 19:23:36,178 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Advancing internal scanner to startKey at 'test,,'
> 2012-08-15 19:24:09,180 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Creating scanner over .META. starting at key ''
> 2012-08-15 19:24:09,180 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Advancing internal scanner to startKey at ''
> 2012-08-15 19:24:09,183 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Finished with scanning at {NAME => '.META.,,1', STARTKEY => '', ENDKEY => '',
> ENCODED => 1028785192,}
> 2012-08-15 19:24:09,183 DEBUG org.apache.hadoop.hbase.master.CatalogJanitor:
> Scanned 2 catalog row(s) and gc'd 0 unreferenced parent region(s)
> 2012-08-15 19:25:12,260 DEBUG
> org.apache.hadoop.hbase.master.handler.DeleteTableHandler: Deleting region
> test,,1345029764571.d1e24b251ca6286c840a9a5f571b7db1. from META and FS
> 2012-08-15 19:25:12,263 INFO org.apache.hadoop.hbase.catalog.MetaEditor:
> Deleted region test,,1345029764571.d1e24b251ca6286c840a9a5f571b7db1. from META
> 2012-08-15 19:25:12,265 INFO
> org.apache.hadoop.hbase.master.handler.EnableTableHandler: Attemping to
> enable the table test
> 2012-08-15 19:25:12,265 WARN org.apache.hadoop.hbase.zookeeper.ZKTable:
> Moving table test state to enabling but was not first in disabled state: null
> 2012-08-15 19:25:12,267 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Creating scanner over .META. starting at key 'test,,'
> 2012-08-15 19:25:12,267 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Advancing internal scanner to startKey at 'test,,'
> 2012-08-15 19:25:12,270 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Finished with scanning at {NAME => '.META.,,1', STARTKEY => '', ENDKEY => '',
> ENCODED => 1028785192,}
> 2012-08-15 19:25:12,270 ERROR org.apache.hadoop.hbase.executor.EventHandler:
> Caught throwable while processing event C_M_ENABLE_TABLE
> java.lang.NullPointerException
> at
> org.apache.hadoop.hbase.master.handler.EnableTableHandler.handleEnableTable(EnableTableHandler.java:116)
> at
> org.apache.hadoop.hbase.master.handler.EnableTableHandler.process(EnableTableHandler.java:97)
> at
> org.apache.hadoop.hbase.executor.EventHandler.run(EventHandler.java:169)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:662)
> table is disabled now, then we enable and delete the table at the same time.
> Since the thread num of MASTER_TABLE_OPERATIONS is 1 by default. The two
> operations are serial in master.Before deletetable deletes all the regions in
> meta, CreateTableHandler ships the check of tableExists,then it will block
> until deletetable finishs, then CreateTableHandler will set zk enabling, and
> find no data in meta:
> regionsInMeta = MetaReader.getTableRegions(this.ct, tableName, true);
> int countOfRegionsInTable = regionsInMeta.size();
> npe will be throwed here. And we could not create the same table anymore.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6588) enable table throws npe and leaves trash in zk in competition with delete table
[
https://issues.apache.org/jira/browse/HBASE-6588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13434979#comment-13434979
]
Zhou wenjian commented on HBASE-6588:
-
the table node in zk
[zk: 10.232.98.77:2181(CONNECTED) 2] get /hbase-feiyun94/table/test
ENABLING
cZxid = 0x1d0044a3de
ctime = Wed Aug 15 19:25:12 CST 2012
mZxid = 0x1d0044a3df
mtime = Wed Aug 15 19:25:12 CST 2012
pZxid = 0x1d0044a3de
cversion = 0
dataVersion = 1
aclVersion = 0
ephemeralOwner = 0x0
dataLength = 35
numChildren = 0
> enable table throws npe and leaves trash in zk in competition with delete
> table
> ---
>
> Key: HBASE-6588
> URL: https://issues.apache.org/jira/browse/HBASE-6588
> Project: HBase
> Issue Type: Bug
>Affects Versions: 0.94.0
>Reporter: Zhou wenjian
> Fix For: 0.94.2
>
>
> 2012-08-15 19:23:36,178 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Creating scanner over .META. starting at key 'test,,'
> 2012-08-15 19:23:36,178 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Advancing internal scanner to startKey at 'test,,'
> 2012-08-15 19:24:09,180 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Creating scanner over .META. starting at key ''
> 2012-08-15 19:24:09,180 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Advancing internal scanner to startKey at ''
> 2012-08-15 19:24:09,183 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Finished with scanning at {NAME => '.META.,,1', STARTKEY => '', ENDKEY => '',
> ENCODED => 1028785192,}
> 2012-08-15 19:24:09,183 DEBUG org.apache.hadoop.hbase.master.CatalogJanitor:
> Scanned 2 catalog row(s) and gc'd 0 unreferenced parent region(s)
> 2012-08-15 19:25:12,260 DEBUG
> org.apache.hadoop.hbase.master.handler.DeleteTableHandler: Deleting region
> test,,1345029764571.d1e24b251ca6286c840a9a5f571b7db1. from META and FS
> 2012-08-15 19:25:12,263 INFO org.apache.hadoop.hbase.catalog.MetaEditor:
> Deleted region test,,1345029764571.d1e24b251ca6286c840a9a5f571b7db1. from META
> 2012-08-15 19:25:12,265 INFO
> org.apache.hadoop.hbase.master.handler.EnableTableHandler: Attemping to
> enable the table test
> 2012-08-15 19:25:12,265 WARN org.apache.hadoop.hbase.zookeeper.ZKTable:
> Moving table test state to enabling but was not first in disabled state: null
> 2012-08-15 19:25:12,267 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Creating scanner over .META. starting at key 'test,,'
> 2012-08-15 19:25:12,267 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Advancing internal scanner to startKey at 'test,,'
> 2012-08-15 19:25:12,270 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
> Finished with scanning at {NAME => '.META.,,1', STARTKEY => '', ENDKEY => '',
> ENCODED => 1028785192,}
> 2012-08-15 19:25:12,270 ERROR org.apache.hadoop.hbase.executor.EventHandler:
> Caught throwable while processing event C_M_ENABLE_TABLE
> java.lang.NullPointerException
> at
> org.apache.hadoop.hbase.master.handler.EnableTableHandler.handleEnableTable(EnableTableHandler.java:116)
> at
> org.apache.hadoop.hbase.master.handler.EnableTableHandler.process(EnableTableHandler.java:97)
> at
> org.apache.hadoop.hbase.executor.EventHandler.run(EventHandler.java:169)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:662)
> table is disabled now, then we enable and delete the table at the same time.
> Since the thread num of MASTER_TABLE_OPERATIONS is 1 by default. The two
> operations are serial in master.Before deletetable deletes all the regions in
> meta, CreateTableHandler ships the check of tableExists,then it will block
> until deletetable finishs, then CreateTableHandler will set zk enabling, and
> find no data in meta:
> regionsInMeta = MetaReader.getTableRegions(this.ct, tableName, true);
> int countOfRegionsInTable = regionsInMeta.size();
> npe will be throwed here. And we could not create the same table anymore.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HBASE-6588) enable table throws npe and leaves trash in zk in competition with delete table
Zhou wenjian created HBASE-6588:
---
Summary: enable table throws npe and leaves trash in zk in
competition with delete table
Key: HBASE-6588
URL: https://issues.apache.org/jira/browse/HBASE-6588
Project: HBase
Issue Type: Bug
Affects Versions: 0.94.0
Reporter: Zhou wenjian
Fix For: 0.94.2
2012-08-15 19:23:36,178 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
Creating scanner over .META. starting at key 'test,,'
2012-08-15 19:23:36,178 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
Advancing internal scanner to startKey at 'test,,'
2012-08-15 19:24:09,180 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
Creating scanner over .META. starting at key ''
2012-08-15 19:24:09,180 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
Advancing internal scanner to startKey at ''
2012-08-15 19:24:09,183 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
Finished with scanning at {NAME => '.META.,,1', STARTKEY => '', ENDKEY => '',
ENCODED => 1028785192,}
2012-08-15 19:24:09,183 DEBUG org.apache.hadoop.hbase.master.CatalogJanitor:
Scanned 2 catalog row(s) and gc'd 0 unreferenced parent region(s)
2012-08-15 19:25:12,260 DEBUG
org.apache.hadoop.hbase.master.handler.DeleteTableHandler: Deleting region
test,,1345029764571.d1e24b251ca6286c840a9a5f571b7db1. from META and FS
2012-08-15 19:25:12,263 INFO org.apache.hadoop.hbase.catalog.MetaEditor:
Deleted region test,,1345029764571.d1e24b251ca6286c840a9a5f571b7db1. from META
2012-08-15 19:25:12,265 INFO
org.apache.hadoop.hbase.master.handler.EnableTableHandler: Attemping to enable
the table test
2012-08-15 19:25:12,265 WARN org.apache.hadoop.hbase.zookeeper.ZKTable: Moving
table test state to enabling but was not first in disabled state: null
2012-08-15 19:25:12,267 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
Creating scanner over .META. starting at key 'test,,'
2012-08-15 19:25:12,267 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
Advancing internal scanner to startKey at 'test,,'
2012-08-15 19:25:12,270 DEBUG org.apache.hadoop.hbase.client.ClientScanner:
Finished with scanning at {NAME => '.META.,,1', STARTKEY => '', ENDKEY => '',
ENCODED => 1028785192,}
2012-08-15 19:25:12,270 ERROR org.apache.hadoop.hbase.executor.EventHandler:
Caught throwable while processing event C_M_ENABLE_TABLE
java.lang.NullPointerException
at
org.apache.hadoop.hbase.master.handler.EnableTableHandler.handleEnableTable(EnableTableHandler.java:116)
at
org.apache.hadoop.hbase.master.handler.EnableTableHandler.process(EnableTableHandler.java:97)
at
org.apache.hadoop.hbase.executor.EventHandler.run(EventHandler.java:169)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
table is disabled now, then we enable and delete the table at the same time.
Since the thread num of MASTER_TABLE_OPERATIONS is 1 by default. The two
operations are serial in master.Before deletetable deletes all the regions in
meta, CreateTableHandler ships the check of tableExists,then it will block
until deletetable finishs, then CreateTableHandler will set zk enabling, and
find no data in meta:
regionsInMeta = MetaReader.getTableRegions(this.ct, tableName, true);
int countOfRegionsInTable = regionsInMeta.size();
npe will be throwed here. And we could not create the same table anymore.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6473) deletedtable is not deleted completely, some region may be still online
[
https://issues.apache.org/jira/browse/HBASE-6473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13434879#comment-13434879
]
Zhou wenjian commented on HBASE-6473:
-
Submitted patch v2 for trunk. Please review and provide your
comments/suggestions
> deletedtable is not deleted completely, some region may be still online
> ---
>
> Key: HBASE-6473
> URL: https://issues.apache.org/jira/browse/HBASE-6473
> Project: HBase
> Issue Type: Bug
>Affects Versions: 0.94.0
>Reporter: zhou wenjian
> Fix For: 0.96.0, 0.94.2
>
> Attachments: HBASE-6473-trunk.patch, HBASE-6473-trunk-v2.patch
>
>
> consider such Scenario:
> we have a table called T1, which has 1 regions: A
> 1. move A from rs1 to rs2,and A is now closed
> 2. disable T1,
> 3. delete T1.
> when we disable T1, disable handler will just set the zk to disabled and A
> will still be assigned. when Ais opened, A in transition will be clean out.
> At that time, Deletetable found it is safe to delete all regions and table in
> meta and fs , it will also delete the zk node of T1.
> {code}
> while (System.currentTimeMillis() < done) {
> AssignmentManager.RegionState rs = am.isRegionInTransition(region);
> if (rs == null) break;
> Threads.sleep(waitingTimeForEvents);
> LOG.debug("Waiting on region to clear regions in transition; " + rs);
> }
> if (am.isRegionInTransition(region) != null) {
> throw new IOException("Waited hbase.master.wait.on.region (" +
> waitTime + "ms) for region to leave region " +
> region.getRegionNameAsString() + " in transitions");
> }
> {code}
> however A is still being unassigned, when it finished closed the A,it finds
> that the disabled state in zk is deleted, and then A will be assigned again.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-6473) deletedtable is not deleted completely, some region may be still online
[
https://issues.apache.org/jira/browse/HBASE-6473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhou wenjian updated HBASE-6473:
Attachment: HBASE-6473-trunk-v2.patch
> deletedtable is not deleted completely, some region may be still online
> ---
>
> Key: HBASE-6473
> URL: https://issues.apache.org/jira/browse/HBASE-6473
> Project: HBase
> Issue Type: Bug
>Affects Versions: 0.94.0
>Reporter: zhou wenjian
> Fix For: 0.96.0, 0.94.2
>
> Attachments: HBASE-6473-trunk.patch, HBASE-6473-trunk-v2.patch
>
>
> consider such Scenario:
> we have a table called T1, which has 1 regions: A
> 1. move A from rs1 to rs2,and A is now closed
> 2. disable T1,
> 3. delete T1.
> when we disable T1, disable handler will just set the zk to disabled and A
> will still be assigned. when Ais opened, A in transition will be clean out.
> At that time, Deletetable found it is safe to delete all regions and table in
> meta and fs , it will also delete the zk node of T1.
> {code}
> while (System.currentTimeMillis() < done) {
> AssignmentManager.RegionState rs = am.isRegionInTransition(region);
> if (rs == null) break;
> Threads.sleep(waitingTimeForEvents);
> LOG.debug("Waiting on region to clear regions in transition; " + rs);
> }
> if (am.isRegionInTransition(region) != null) {
> throw new IOException("Waited hbase.master.wait.on.region (" +
> waitTime + "ms) for region to leave region " +
> region.getRegionNameAsString() + " in transitions");
> }
> {code}
> however A is still being unassigned, when it finished closed the A,it finds
> that the disabled state in zk is deleted, and then A will be assigned again.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6563) s.isMajorCompaction() throws npe will cause current major Compaction checking abort
[ https://issues.apache.org/jira/browse/HBASE-6563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13433936#comment-13433936 ] Zhou wenjian commented on HBASE-6563: - Submitted patch v2 for trunk. Please review and provide your comments/suggestions > s.isMajorCompaction() throws npe will cause current major Compaction checking > abort > --- > > Key: HBASE-6563 > URL: https://issues.apache.org/jira/browse/HBASE-6563 > Project: HBase > Issue Type: Bug > Components: regionserver >Reporter: Zhou wenjian > Fix For: 0.94.1 > > Attachments: HBASE-6563-trunk.patch, HBASE-6563-trunk-v2.patch > > > 2012-05-05 00:49:43,265 ERROR > org.apache.hadoop.hbase.regionserver.HRegionServer$MajorCompactionChecker: > Caught exception > java.lang.NullPointerException > at > org.apache.hadoop.hbase.regionserver.Store.isMajorCompaction(Store.java:938) > at > org.apache.hadoop.hbase.regionserver.Store.isMajorCompaction(Store.java:917) > at > org.apache.hadoop.hbase.regionserver.HRegion.isMajorCompaction(HRegion.java:3250) > at > org.apache.hadoop.hbase.regionserver.HRegionServer$MajorCompactionChecker.chore(HRegionServer.java:1222) > at org.apache.hadoop.hbase.Chore.run(Chore.java:66) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-6563) s.isMajorCompaction() throws npe will cause current major Compaction checking abort
[ https://issues.apache.org/jira/browse/HBASE-6563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhou wenjian updated HBASE-6563: Attachment: HBASE-6563-trunk-v2.patch > s.isMajorCompaction() throws npe will cause current major Compaction checking > abort > --- > > Key: HBASE-6563 > URL: https://issues.apache.org/jira/browse/HBASE-6563 > Project: HBase > Issue Type: Bug > Components: regionserver >Reporter: Zhou wenjian > Fix For: 0.94.1 > > Attachments: HBASE-6563-trunk.patch, HBASE-6563-trunk-v2.patch > > > 2012-05-05 00:49:43,265 ERROR > org.apache.hadoop.hbase.regionserver.HRegionServer$MajorCompactionChecker: > Caught exception > java.lang.NullPointerException > at > org.apache.hadoop.hbase.regionserver.Store.isMajorCompaction(Store.java:938) > at > org.apache.hadoop.hbase.regionserver.Store.isMajorCompaction(Store.java:917) > at > org.apache.hadoop.hbase.regionserver.HRegion.isMajorCompaction(HRegion.java:3250) > at > org.apache.hadoop.hbase.regionserver.HRegionServer$MajorCompactionChecker.chore(HRegionServer.java:1222) > at org.apache.hadoop.hbase.Chore.run(Chore.java:66) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-6478) TestClassLoading.testClassLoadingFromLibDirInJar in coprocessor may appear fail due to waitTableAvailable
[
https://issues.apache.org/jira/browse/HBASE-6478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhou wenjian updated HBASE-6478:
Attachment: HBASE-6478-trunk-v2.patch
> TestClassLoading.testClassLoadingFromLibDirInJar in coprocessor may appear
> fail due to waitTableAvailable
> -
>
> Key: HBASE-6478
> URL: https://issues.apache.org/jira/browse/HBASE-6478
> Project: HBase
> Issue Type: Bug
> Components: test
>Affects Versions: 0.94.0
>Reporter: zhou wenjian
> Fix For: 0.96.0, 0.94.2
>
> Attachments: HBASE-6478-trunk.patch, HBASE-6478-trunk-v2.patch
>
>
> When hudson runs for HBASE-6459, it encounters a failed testcase in
> org.apache.hadoop.hbase.coprocessor.TestClassLoading.testClassLoadingFromLibDirInJar.
> The link is
> https://builds.apache.org/job/PreCommit-HBASE-Build/2455/testReport/org.apache.hadoop.hbase.coprocessor/TestClassLoading/testClassLoadingFromLibDirInJar/
> I check the log, and find that the function waitTableAvailable will only
> check the meta table, when rs open the region and update the metalocation in
> meta, it may not be added to the onlineregions in rs.
> for (HRegion region:
> hbase.getRegionServer(0).getOnlineRegionsLocalContext()) {
> this Loop will ship, and found1 will be false altogether.
> that's why the testcase failed.
> So maybe we can hbave some strictly check when table is created
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6478) TestClassLoading.testClassLoadingFromLibDirInJar in coprocessor may appear fail due to waitTableAvailable
[
https://issues.apache.org/jira/browse/HBASE-6478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13432956#comment-13432956
]
Zhou wenjian commented on HBASE-6478:
-
https://builds.apache.org/job/PreCommit-HBASE-Build/2552//testReport/org.apache.hadoop.hbase.coprocessor/TestClassLoading/testClassLoadingFromLibDirInJar/
it appears again
> TestClassLoading.testClassLoadingFromLibDirInJar in coprocessor may appear
> fail due to waitTableAvailable
> -
>
> Key: HBASE-6478
> URL: https://issues.apache.org/jira/browse/HBASE-6478
> Project: HBase
> Issue Type: Bug
> Components: test
>Affects Versions: 0.94.0
>Reporter: zhou wenjian
> Fix For: 0.96.0, 0.94.2
>
> Attachments: HBASE-6478-trunk.patch
>
>
> When hudson runs for HBASE-6459, it encounters a failed testcase in
> org.apache.hadoop.hbase.coprocessor.TestClassLoading.testClassLoadingFromLibDirInJar.
> The link is
> https://builds.apache.org/job/PreCommit-HBASE-Build/2455/testReport/org.apache.hadoop.hbase.coprocessor/TestClassLoading/testClassLoadingFromLibDirInJar/
> I check the log, and find that the function waitTableAvailable will only
> check the meta table, when rs open the region and update the metalocation in
> meta, it may not be added to the onlineregions in rs.
> for (HRegion region:
> hbase.getRegionServer(0).getOnlineRegionsLocalContext()) {
> this Loop will ship, and found1 will be false altogether.
> that's why the testcase failed.
> So maybe we can hbave some strictly check when table is created
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6563) s.isMajorCompaction() throws npe will cause current major Compaction checking abort
[ https://issues.apache.org/jira/browse/HBASE-6563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13432955#comment-13432955 ] Zhou wenjian commented on HBASE-6563: - The failed testcases have nothing to do with the patch > s.isMajorCompaction() throws npe will cause current major Compaction checking > abort > --- > > Key: HBASE-6563 > URL: https://issues.apache.org/jira/browse/HBASE-6563 > Project: HBase > Issue Type: Bug > Components: regionserver >Reporter: Zhou wenjian > Fix For: 0.94.1 > > Attachments: HBASE-6563-trunk.patch > > > 2012-05-05 00:49:43,265 ERROR > org.apache.hadoop.hbase.regionserver.HRegionServer$MajorCompactionChecker: > Caught exception > java.lang.NullPointerException > at > org.apache.hadoop.hbase.regionserver.Store.isMajorCompaction(Store.java:938) > at > org.apache.hadoop.hbase.regionserver.Store.isMajorCompaction(Store.java:917) > at > org.apache.hadoop.hbase.regionserver.HRegion.isMajorCompaction(HRegion.java:3250) > at > org.apache.hadoop.hbase.regionserver.HRegionServer$MajorCompactionChecker.chore(HRegionServer.java:1222) > at org.apache.hadoop.hbase.Chore.run(Chore.java:66) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6537) Balancer compete with disable table will lead to cluster inconsistent
[ https://issues.apache.org/jira/browse/HBASE-6537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13432921#comment-13432921 ] Zhou wenjian commented on HBASE-6537: - @Ted we have no trunk hudson, just 94 in local > Balancer compete with disable table will lead to cluster inconsistent > -- > > Key: HBASE-6537 > URL: https://issues.apache.org/jira/browse/HBASE-6537 > Project: HBase > Issue Type: Bug > Components: master >Affects Versions: 0.94.0 >Reporter: Zhou wenjian > Fix For: 0.94.2 > > Attachments: HBASE-6537-94.patch, HBASE-6537-94-v2.patch, > HBASE-6537-trunk.patch > > > Appear in 94. trunk is ok for the issue > Balancer will collect the regionplans to move(unassign and then assign). > before unassign, disable table appears, > after close the region in rs, master will delete the znode, romove region > from RIT, > and then clean the region from the online regions. > During romoving region from RIT and cleaning out the region from the online > regions. > balancer begins to unassign, it will get a NotServingRegionException and if > the table is disabling, it will deal with the state in master and delete the > znode . However the table is disabled now, so the RIT and znode will remain. > TimeoutMonitor draws a blank on it. > It will hold back enabling the table or balancer unless restart -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-6563) s.isMajorCompaction() throws npe will cause current major Compaction checking abort
[ https://issues.apache.org/jira/browse/HBASE-6563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhou wenjian updated HBASE-6563: Status: Patch Available (was: Open) > s.isMajorCompaction() throws npe will cause current major Compaction checking > abort > --- > > Key: HBASE-6563 > URL: https://issues.apache.org/jira/browse/HBASE-6563 > Project: HBase > Issue Type: Bug > Components: regionserver >Reporter: Zhou wenjian > Fix For: 0.94.1 > > Attachments: HBASE-6563-trunk.patch > > > 2012-05-05 00:49:43,265 ERROR > org.apache.hadoop.hbase.regionserver.HRegionServer$MajorCompactionChecker: > Caught exception > java.lang.NullPointerException > at > org.apache.hadoop.hbase.regionserver.Store.isMajorCompaction(Store.java:938) > at > org.apache.hadoop.hbase.regionserver.Store.isMajorCompaction(Store.java:917) > at > org.apache.hadoop.hbase.regionserver.HRegion.isMajorCompaction(HRegion.java:3250) > at > org.apache.hadoop.hbase.regionserver.HRegionServer$MajorCompactionChecker.chore(HRegionServer.java:1222) > at org.apache.hadoop.hbase.Chore.run(Chore.java:66) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6563) s.isMajorCompaction() throws npe will cause current major Compaction checking abort
[ https://issues.apache.org/jira/browse/HBASE-6563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13432912#comment-13432912 ] Zhou wenjian commented on HBASE-6563: - patch for trunk > s.isMajorCompaction() throws npe will cause current major Compaction checking > abort > --- > > Key: HBASE-6563 > URL: https://issues.apache.org/jira/browse/HBASE-6563 > Project: HBase > Issue Type: Bug > Components: regionserver >Reporter: Zhou wenjian > Fix For: 0.94.1 > > Attachments: HBASE-6563-trunk.patch > > > 2012-05-05 00:49:43,265 ERROR > org.apache.hadoop.hbase.regionserver.HRegionServer$MajorCompactionChecker: > Caught exception > java.lang.NullPointerException > at > org.apache.hadoop.hbase.regionserver.Store.isMajorCompaction(Store.java:938) > at > org.apache.hadoop.hbase.regionserver.Store.isMajorCompaction(Store.java:917) > at > org.apache.hadoop.hbase.regionserver.HRegion.isMajorCompaction(HRegion.java:3250) > at > org.apache.hadoop.hbase.regionserver.HRegionServer$MajorCompactionChecker.chore(HRegionServer.java:1222) > at org.apache.hadoop.hbase.Chore.run(Chore.java:66) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-6563) s.isMajorCompaction() throws npe will cause current major Compaction checking abort
[ https://issues.apache.org/jira/browse/HBASE-6563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhou wenjian updated HBASE-6563: Attachment: HBASE-6563-trunk.patch > s.isMajorCompaction() throws npe will cause current major Compaction checking > abort > --- > > Key: HBASE-6563 > URL: https://issues.apache.org/jira/browse/HBASE-6563 > Project: HBase > Issue Type: Bug > Components: regionserver >Reporter: Zhou wenjian > Fix For: 0.94.1 > > Attachments: HBASE-6563-trunk.patch > > > 2012-05-05 00:49:43,265 ERROR > org.apache.hadoop.hbase.regionserver.HRegionServer$MajorCompactionChecker: > Caught exception > java.lang.NullPointerException > at > org.apache.hadoop.hbase.regionserver.Store.isMajorCompaction(Store.java:938) > at > org.apache.hadoop.hbase.regionserver.Store.isMajorCompaction(Store.java:917) > at > org.apache.hadoop.hbase.regionserver.HRegion.isMajorCompaction(HRegion.java:3250) > at > org.apache.hadoop.hbase.regionserver.HRegionServer$MajorCompactionChecker.chore(HRegionServer.java:1222) > at org.apache.hadoop.hbase.Chore.run(Chore.java:66) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-6563) s.isMajorCompaction() throws npe will cause current major Compaction checking abort
[ https://issues.apache.org/jira/browse/HBASE-6563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhou wenjian updated HBASE-6563: Attachment: (was: HBASE-6563.patch) > s.isMajorCompaction() throws npe will cause current major Compaction checking > abort > --- > > Key: HBASE-6563 > URL: https://issues.apache.org/jira/browse/HBASE-6563 > Project: HBase > Issue Type: Bug > Components: regionserver >Reporter: Zhou wenjian > Fix For: 0.94.1 > > > 2012-05-05 00:49:43,265 ERROR > org.apache.hadoop.hbase.regionserver.HRegionServer$MajorCompactionChecker: > Caught exception > java.lang.NullPointerException > at > org.apache.hadoop.hbase.regionserver.Store.isMajorCompaction(Store.java:938) > at > org.apache.hadoop.hbase.regionserver.Store.isMajorCompaction(Store.java:917) > at > org.apache.hadoop.hbase.regionserver.HRegion.isMajorCompaction(HRegion.java:3250) > at > org.apache.hadoop.hbase.regionserver.HRegionServer$MajorCompactionChecker.chore(HRegionServer.java:1222) > at org.apache.hadoop.hbase.Chore.run(Chore.java:66) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-6563) s.isMajorCompaction() throws npe will cause current major Compaction checking abort
[ https://issues.apache.org/jira/browse/HBASE-6563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhou wenjian updated HBASE-6563: Attachment: HBASE-6563.patch > s.isMajorCompaction() throws npe will cause current major Compaction checking > abort > --- > > Key: HBASE-6563 > URL: https://issues.apache.org/jira/browse/HBASE-6563 > Project: HBase > Issue Type: Bug > Components: regionserver >Reporter: Zhou wenjian > Fix For: 0.94.1 > > > 2012-05-05 00:49:43,265 ERROR > org.apache.hadoop.hbase.regionserver.HRegionServer$MajorCompactionChecker: > Caught exception > java.lang.NullPointerException > at > org.apache.hadoop.hbase.regionserver.Store.isMajorCompaction(Store.java:938) > at > org.apache.hadoop.hbase.regionserver.Store.isMajorCompaction(Store.java:917) > at > org.apache.hadoop.hbase.regionserver.HRegion.isMajorCompaction(HRegion.java:3250) > at > org.apache.hadoop.hbase.regionserver.HRegionServer$MajorCompactionChecker.chore(HRegionServer.java:1222) > at org.apache.hadoop.hbase.Chore.run(Chore.java:66) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6563) s.isMajorCompaction() throws npe will cause current major Compaction checking abort
[ https://issues.apache.org/jira/browse/HBASE-6563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13432910#comment-13432910 ] Zhou wenjian commented on HBASE-6563: - appears in 90, when we do major compaction checking, the storefile maybe is closed now so sf.getReader().timeRangeTracker will throw npe, which will abort current major Compaction I think trunk will be affected too. > s.isMajorCompaction() throws npe will cause current major Compaction checking > abort > --- > > Key: HBASE-6563 > URL: https://issues.apache.org/jira/browse/HBASE-6563 > Project: HBase > Issue Type: Bug > Components: regionserver >Reporter: Zhou wenjian > Fix For: 0.94.1 > > > 2012-05-05 00:49:43,265 ERROR > org.apache.hadoop.hbase.regionserver.HRegionServer$MajorCompactionChecker: > Caught exception > java.lang.NullPointerException > at > org.apache.hadoop.hbase.regionserver.Store.isMajorCompaction(Store.java:938) > at > org.apache.hadoop.hbase.regionserver.Store.isMajorCompaction(Store.java:917) > at > org.apache.hadoop.hbase.regionserver.HRegion.isMajorCompaction(HRegion.java:3250) > at > org.apache.hadoop.hbase.regionserver.HRegionServer$MajorCompactionChecker.chore(HRegionServer.java:1222) > at org.apache.hadoop.hbase.Chore.run(Chore.java:66) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HBASE-6563) s.isMajorCompaction() throws npe will cause current major Compaction checking abort
Zhou wenjian created HBASE-6563: --- Summary: s.isMajorCompaction() throws npe will cause current major Compaction checking abort Key: HBASE-6563 URL: https://issues.apache.org/jira/browse/HBASE-6563 Project: HBase Issue Type: Bug Components: regionserver Reporter: Zhou wenjian Fix For: 0.94.1 2012-05-05 00:49:43,265 ERROR org.apache.hadoop.hbase.regionserver.HRegionServer$MajorCompactionChecker: Caught exception java.lang.NullPointerException at org.apache.hadoop.hbase.regionserver.Store.isMajorCompaction(Store.java:938) at org.apache.hadoop.hbase.regionserver.Store.isMajorCompaction(Store.java:917) at org.apache.hadoop.hbase.regionserver.HRegion.isMajorCompaction(HRegion.java:3250) at org.apache.hadoop.hbase.regionserver.HRegionServer$MajorCompactionChecker.chore(HRegionServer.java:1222) at org.apache.hadoop.hbase.Chore.run(Chore.java:66) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6473) deletedtable is not deleted completely, some region may be still online
[
https://issues.apache.org/jira/browse/HBASE-6473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13432686#comment-13432686
]
Zhou wenjian commented on HBASE-6473:
-
get the region state and make sure it is OFFLINE
function getRegionState(hri) is protected and i think it is does the same thing
with getRegionsOfTable(tableName).contains(region)
> deletedtable is not deleted completely, some region may be still online
> ---
>
> Key: HBASE-6473
> URL: https://issues.apache.org/jira/browse/HBASE-6473
> Project: HBase
> Issue Type: Bug
>Affects Versions: 0.94.0
>Reporter: zhou wenjian
> Fix For: 0.96.0, 0.94.2
>
> Attachments: HBASE-6473-trunk.patch
>
>
> consider such Scenario:
> we have a table called T1, which has 1 regions: A
> 1. move A from rs1 to rs2,and A is now closed
> 2. disable T1,
> 3. delete T1.
> when we disable T1, disable handler will just set the zk to disabled and A
> will still be assigned. when Ais opened, A in transition will be clean out.
> At that time, Deletetable found it is safe to delete all regions and table in
> meta and fs , it will also delete the zk node of T1.
> {code}
> while (System.currentTimeMillis() < done) {
> AssignmentManager.RegionState rs = am.isRegionInTransition(region);
> if (rs == null) break;
> Threads.sleep(waitingTimeForEvents);
> LOG.debug("Waiting on region to clear regions in transition; " + rs);
> }
> if (am.isRegionInTransition(region) != null) {
> throw new IOException("Waited hbase.master.wait.on.region (" +
> waitTime + "ms) for region to leave region " +
> region.getRegionNameAsString() + " in transitions");
> }
> {code}
> however A is still being unassigned, when it finished closed the A,it finds
> that the disabled state in zk is deleted, and then A will be assigned again.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-6537) Balancer compete with disable table will lead to cluster inconsistent
[ https://issues.apache.org/jira/browse/HBASE-6537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhou wenjian updated HBASE-6537: Attachment: HBASE-6537-trunk.patch > Balancer compete with disable table will lead to cluster inconsistent > -- > > Key: HBASE-6537 > URL: https://issues.apache.org/jira/browse/HBASE-6537 > Project: HBase > Issue Type: Bug > Components: master >Affects Versions: 0.94.0 >Reporter: Zhou wenjian > Fix For: 0.94.2 > > Attachments: HBASE-6537-94.patch, HBASE-6537-trunk.patch > > > Appear in 94. trunk is ok for the issue > Balancer will collect the regionplans to move(unassign and then assign). > before unassign, disable table appears, > after close the region in rs, master will delete the znode, romove region > from RIT, > and then clean the region from the online regions. > During romoving region from RIT and cleaning out the region from the online > regions. > balancer begins to unassign, it will get a NotServingRegionException and if > the table is disabling, it will deal with the state in master and delete the > znode . However the table is disabled now, so the RIT and znode will remain. > TimeoutMonitor draws a blank on it. > It will hold back enabling the table or balancer unless restart -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-6537) Balancer compete with disable table will lead to cluster inconsistent
[ https://issues.apache.org/jira/browse/HBASE-6537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhou wenjian updated HBASE-6537: Attachment: HBASE-6537-94-v2.patch > Balancer compete with disable table will lead to cluster inconsistent > -- > > Key: HBASE-6537 > URL: https://issues.apache.org/jira/browse/HBASE-6537 > Project: HBase > Issue Type: Bug > Components: master >Affects Versions: 0.94.0 >Reporter: Zhou wenjian > Fix For: 0.94.2 > > Attachments: HBASE-6537-94-v2.patch, HBASE-6537-94.patch, > HBASE-6537-trunk.patch > > > Appear in 94. trunk is ok for the issue > Balancer will collect the regionplans to move(unassign and then assign). > before unassign, disable table appears, > after close the region in rs, master will delete the znode, romove region > from RIT, > and then clean the region from the online regions. > During romoving region from RIT and cleaning out the region from the online > regions. > balancer begins to unassign, it will get a NotServingRegionException and if > the table is disabling, it will deal with the state in master and delete the > znode . However the table is disabled now, so the RIT and znode will remain. > TimeoutMonitor draws a blank on it. > It will hold back enabling the table or balancer unless restart -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
