[jira] [Updated] (HBASE-5202) NPE in master.AssignmentManager.regionOnline()
[
https://issues.apache.org/jira/browse/HBASE-5202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eugene Koontz updated HBASE-5202:
-
Attachment: testMasterFailoverWithSlowRS.txt
patch to TestMasterFailover.java to cause NPE.
NPE in master.AssignmentManager.regionOnline()
--
Key: HBASE-5202
URL: https://issues.apache.org/jira/browse/HBASE-5202
Project: HBase
Issue Type: Bug
Affects Versions: 0.90.6
Reporter: Eugene Koontz
Assignee: Eugene Koontz
Attachments: testMasterFailoverWithSlowRS.txt
The following NPE can occur during master failover:
{code}
2012-01-15 17:45:00,314 FATAL
[Master:1;ip-10-166-123-193.us-west-1.compute.internal:36708]
master.HMaster(944): Unhandled exception. Starting shutdown.
java.lang.NullPointerException
at
org.apache.hadoop.hbase.master.AssignmentManager.regionOnline(AssignmentManager.java:724)
at
org.apache.hadoop.hbase.master.AssignmentManager.processFailover(AssignmentManager.java:214)
at
org.apache.hadoop.hbase.master.HMaster.finishInitialization(HMaster.java:396)
at org.apache.hadoop.hbase.master.HMaster.run(HMaster.java:279)
at java.lang.Thread.run(Thread.java:636)
{code}
This is caused by regionOnline() being passed a null serverInfo (its second
parameter).
The AssignmentManager's processFailover() method is passing a null to
regionOnline() because the value that regionOnline is passing, hsi, is set as:
{code}
hsi =
this.serverManager.getHServerInfo(this.catalogTracker.getMetaLocation());
{code}
and
{code}
hsi =
this.serverManager.getHServerInfo(this.catalogTracker.getRootLocation());
{code}
getHServerInfo(), is defined as:
{code}
public HServerInfo getHServerInfo(final HServerAddress hsa) {
synchronized(this.onlineServers) {
// TODO: This is primitive. Do a better search.
for (Map.EntryString, HServerInfo e: this.onlineServers.entrySet()) {
if (e.getValue().getServerAddress().equals(hsa)) {
return e.getValue();
}
}
}
return null;
}
{code}
This can return null because the onlineServers map does not yet have a value
corresponding to the key supplied by the catalogTracker's getRootLocation()
or getMetaLocation().
Since the catalogTracker uses zookeeper to establish the server locations of
{{-ROOT-}} and {{.META.}}, while the onlineServers map is set according to
the these servers registering with the master, there can be an inconsistency
between the catalogTracker and the onlineServers if either of these
regionservers is online with respect to zookeeper, but haven't yet registered
with the master (perhaps due to a high latency network between the master and
the regionserver).
The attached testMasterFailoverWithSlowRS.txt patch can be used to modify
TestMasterFailover to cause this NPE.
The proposed fix (provided along with the above test in a separate
attachment) is for the master to use the new verifyMetaTablesAreUp() to wait
for both of the servers named by the catalog tracker's getRootLocation() and
getMetaLocation() to register with the master before the master can continue
with failover.
--
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-5202) NPE in master.AssignmentManager.regionOnline()
[
https://issues.apache.org/jira/browse/HBASE-5202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eugene Koontz updated HBASE-5202:
-
Attachment: HBASE-5202.patch
NPE in master.AssignmentManager.regionOnline()
--
Key: HBASE-5202
URL: https://issues.apache.org/jira/browse/HBASE-5202
Project: HBase
Issue Type: Bug
Affects Versions: 0.90.6
Reporter: Eugene Koontz
Assignee: Eugene Koontz
Attachments: HBASE-5202.patch, testMasterFailoverWithSlowRS.txt
The following NPE can occur during master failover:
{code}
2012-01-15 17:45:00,314 FATAL
[Master:1;ip-10-166-123-193.us-west-1.compute.internal:36708]
master.HMaster(944): Unhandled exception. Starting shutdown.
java.lang.NullPointerException
at
org.apache.hadoop.hbase.master.AssignmentManager.regionOnline(AssignmentManager.java:724)
at
org.apache.hadoop.hbase.master.AssignmentManager.processFailover(AssignmentManager.java:214)
at
org.apache.hadoop.hbase.master.HMaster.finishInitialization(HMaster.java:396)
at org.apache.hadoop.hbase.master.HMaster.run(HMaster.java:279)
at java.lang.Thread.run(Thread.java:636)
{code}
This is caused by regionOnline() being passed a null serverInfo (its second
parameter).
The AssignmentManager's processFailover() method is passing a null to
regionOnline() because the value that regionOnline is passing, hsi, is set as:
{code}
hsi =
this.serverManager.getHServerInfo(this.catalogTracker.getMetaLocation());
{code}
and
{code}
hsi =
this.serverManager.getHServerInfo(this.catalogTracker.getRootLocation());
{code}
getHServerInfo(), is defined as:
{code}
public HServerInfo getHServerInfo(final HServerAddress hsa) {
synchronized(this.onlineServers) {
// TODO: This is primitive. Do a better search.
for (Map.EntryString, HServerInfo e: this.onlineServers.entrySet()) {
if (e.getValue().getServerAddress().equals(hsa)) {
return e.getValue();
}
}
}
return null;
}
{code}
This can return null because the onlineServers map does not yet have a value
corresponding to the key supplied by the catalogTracker's getRootLocation()
or getMetaLocation().
Since the catalogTracker uses zookeeper to establish the server locations of
{{-ROOT-}} and {{.META.}}, while the onlineServers map is set according to
the these servers registering with the master, there can be an inconsistency
between the catalogTracker and the onlineServers if either of these
regionservers is online with respect to zookeeper, but haven't yet registered
with the master (perhaps due to a high latency network between the master and
the regionserver).
The attached testMasterFailoverWithSlowRS.txt patch can be used to modify
TestMasterFailover to cause this NPE.
The proposed fix (provided along with the above test in a separate
attachment) is for the master to use the new verifyMetaTablesAreUp() to wait
for both of the servers named by the catalog tracker's getRootLocation() and
getMetaLocation() to register with the master before the master can continue
with failover.
--
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-5202) NPE in master.AssignmentManager.regionOnline()
[
https://issues.apache.org/jira/browse/HBASE-5202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eugene Koontz updated HBASE-5202:
-
Status: Patch Available (was: Open)
NPE in master.AssignmentManager.regionOnline()
--
Key: HBASE-5202
URL: https://issues.apache.org/jira/browse/HBASE-5202
Project: HBase
Issue Type: Bug
Affects Versions: 0.90.6
Reporter: Eugene Koontz
Assignee: Eugene Koontz
Attachments: HBASE-5202.patch, testMasterFailoverWithSlowRS.txt
The following NPE can occur during master failover:
{code}
2012-01-15 17:45:00,314 FATAL
[Master:1;ip-10-166-123-193.us-west-1.compute.internal:36708]
master.HMaster(944): Unhandled exception. Starting shutdown.
java.lang.NullPointerException
at
org.apache.hadoop.hbase.master.AssignmentManager.regionOnline(AssignmentManager.java:724)
at
org.apache.hadoop.hbase.master.AssignmentManager.processFailover(AssignmentManager.java:214)
at
org.apache.hadoop.hbase.master.HMaster.finishInitialization(HMaster.java:396)
at org.apache.hadoop.hbase.master.HMaster.run(HMaster.java:279)
at java.lang.Thread.run(Thread.java:636)
{code}
This is caused by regionOnline() being passed a null serverInfo (its second
parameter).
The AssignmentManager's processFailover() method is passing a null to
regionOnline() because the value that regionOnline is passing, hsi, is set as:
{code}
hsi =
this.serverManager.getHServerInfo(this.catalogTracker.getMetaLocation());
{code}
and
{code}
hsi =
this.serverManager.getHServerInfo(this.catalogTracker.getRootLocation());
{code}
getHServerInfo(), is defined as:
{code}
public HServerInfo getHServerInfo(final HServerAddress hsa) {
synchronized(this.onlineServers) {
// TODO: This is primitive. Do a better search.
for (Map.EntryString, HServerInfo e: this.onlineServers.entrySet()) {
if (e.getValue().getServerAddress().equals(hsa)) {
return e.getValue();
}
}
}
return null;
}
{code}
This can return null because the onlineServers map does not yet have a value
corresponding to the key supplied by the catalogTracker's getRootLocation()
or getMetaLocation().
Since the catalogTracker uses zookeeper to establish the server locations of
{{-ROOT-}} and {{.META.}}, while the onlineServers map is set according to
the these servers registering with the master, there can be an inconsistency
between the catalogTracker and the onlineServers if either of these
regionservers is online with respect to zookeeper, but haven't yet registered
with the master (perhaps due to a high latency network between the master and
the regionserver).
The attached testMasterFailoverWithSlowRS.txt patch can be used to modify
TestMasterFailover to cause this NPE.
The proposed fix (provided along with the above test in a separate
attachment) is for the master to use the new verifyMetaTablesAreUp() to wait
for both of the servers named by the catalog tracker's getRootLocation() and
getMetaLocation() to register with the master before the master can continue
with failover.
--
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-3933) Hmaster throw NullPointerException
[
https://issues.apache.org/jira/browse/HBASE-3933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eugene Koontz updated HBASE-3933:
-
Resolution: Fixed
Release Note: It was recommended to continue working on this on a new JIRA
since this one was closed and was too old to continue with.
Status: Resolved (was: Patch Available)
Hmaster throw NullPointerException
--
Key: HBASE-3933
URL: https://issues.apache.org/jira/browse/HBASE-3933
Project: HBase
Issue Type: Bug
Components: master
Affects Versions: 0.90.6
Reporter: gaojinchao
Assignee: Eugene Koontz
Attachments: HBASE-3933.patch, HBASE-3933.patch, Hmastersetup0.90
NullPointerException while hmaster starting.
{code}
java.lang.NullPointerException
at java.util.TreeMap.getEntry(TreeMap.java:324)
at java.util.TreeMap.get(TreeMap.java:255)
at
org.apache.hadoop.hbase.master.AssignmentManager.addToServers(AssignmentManager.java:1512)
at
org.apache.hadoop.hbase.master.AssignmentManager.regionOnline(AssignmentManager.java:606)
at
org.apache.hadoop.hbase.master.AssignmentManager.processFailover(AssignmentManager.java:214)
at
org.apache.hadoop.hbase.master.HMaster.finishInitialization(HMaster.java:402)
at org.apache.hadoop.hbase.master.HMaster.run(HMaster.java:283)
{code}
--
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-5202) NPE during Master failover in master.AssignmentManager.regionOnline()
[
https://issues.apache.org/jira/browse/HBASE-5202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eugene Koontz updated HBASE-5202:
-
Summary: NPE during Master failover in
master.AssignmentManager.regionOnline() (was: NPE in
master.AssignmentManager.regionOnline())
NPE during Master failover in master.AssignmentManager.regionOnline()
-
Key: HBASE-5202
URL: https://issues.apache.org/jira/browse/HBASE-5202
Project: HBase
Issue Type: Bug
Affects Versions: 0.90.6
Reporter: Eugene Koontz
Assignee: Eugene Koontz
Attachments: HBASE-5202.patch, testMasterFailoverWithSlowRS.txt
The following NPE can occur during master failover:
{code}
2012-01-15 17:45:00,314 FATAL
[Master:1;ip-10-166-123-193.us-west-1.compute.internal:36708]
master.HMaster(944): Unhandled exception. Starting shutdown.
java.lang.NullPointerException
at
org.apache.hadoop.hbase.master.AssignmentManager.regionOnline(AssignmentManager.java:724)
at
org.apache.hadoop.hbase.master.AssignmentManager.processFailover(AssignmentManager.java:214)
at
org.apache.hadoop.hbase.master.HMaster.finishInitialization(HMaster.java:396)
at org.apache.hadoop.hbase.master.HMaster.run(HMaster.java:279)
at java.lang.Thread.run(Thread.java:636)
{code}
This is caused by regionOnline() being passed a null serverInfo (its second
parameter).
The AssignmentManager's processFailover() method is passing a null to
regionOnline() because the value that regionOnline is passing, hsi, is set as:
{code}
hsi =
this.serverManager.getHServerInfo(this.catalogTracker.getMetaLocation());
{code}
and
{code}
hsi =
this.serverManager.getHServerInfo(this.catalogTracker.getRootLocation());
{code}
getHServerInfo(), is defined as:
{code}
public HServerInfo getHServerInfo(final HServerAddress hsa) {
synchronized(this.onlineServers) {
// TODO: This is primitive. Do a better search.
for (Map.EntryString, HServerInfo e: this.onlineServers.entrySet()) {
if (e.getValue().getServerAddress().equals(hsa)) {
return e.getValue();
}
}
}
return null;
}
{code}
This can return null because the onlineServers map does not yet have a value
corresponding to the key supplied by the catalogTracker's getRootLocation()
or getMetaLocation().
Since the catalogTracker uses zookeeper to establish the server locations of
{{-ROOT-}} and {{.META.}}, while the onlineServers map is set according to
the these servers registering with the master, there can be an inconsistency
between the catalogTracker and the onlineServers if either of these
regionservers is online with respect to zookeeper, but haven't yet registered
with the master (perhaps due to a high latency network between the master and
the regionserver).
The attached testMasterFailoverWithSlowRS.txt patch can be used to modify
TestMasterFailover to cause this NPE.
The proposed fix (provided along with the above test in a separate
attachment) is for the master to use the new verifyMetaTablesAreUp() to wait
for both of the servers named by the catalog tracker's getRootLocation() and
getMetaLocation() to register with the master before the master can continue
with failover.
--
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-5202) NPE during Master failover in master.AssignmentManager.regionOnline()
[
https://issues.apache.org/jira/browse/HBASE-5202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eugene Koontz updated HBASE-5202:
-
Description:
The following NPE can occur during master failover:
{code}
2012-01-15 17:45:00,314 FATAL
[Master:1;ip-10-166-123-193.us-west-1.compute.internal:36708]
master.HMaster(944): Unhandled exception. Starting shutdown.
java.lang.NullPointerException
at
org.apache.hadoop.hbase.master.AssignmentManager.regionOnline(AssignmentManager.java:724)
at
org.apache.hadoop.hbase.master.AssignmentManager.processFailover(AssignmentManager.java:214)
at
org.apache.hadoop.hbase.master.HMaster.finishInitialization(HMaster.java:396)
at org.apache.hadoop.hbase.master.HMaster.run(HMaster.java:279)
at java.lang.Thread.run(Thread.java:636)
{code}
This is caused by regionOnline() being passed a null serverInfo (its second
parameter).
The AssignmentManager's processFailover() method is passing a null to
regionOnline() because the value that regionOnline is passing, hsi, is set as:
{code}
hsi = this.serverManager.getHServerInfo(this.catalogTracker.getMetaLocation());
{code}
and
{code}
hsi = this.serverManager.getHServerInfo(this.catalogTracker.getRootLocation());
{code}
getHServerInfo(), is defined as:
{code}
public HServerInfo getHServerInfo(final HServerAddress hsa) {
synchronized(this.onlineServers) {
// TODO: This is primitive. Do a better search.
for (Map.EntryString, HServerInfo e: this.onlineServers.entrySet()) {
if (e.getValue().getServerAddress().equals(hsa)) {
return e.getValue();
}
}
}
return null;
}
{code}
This will return null if the onlineServers map does not yet have a value
corresponding to the key supplied by the catalogTracker's getRootLocation() or
getMetaLocation().
Since the catalogTracker uses zookeeper to establish the server locations of
{{-ROOT-}} and {{.META.}}, while the onlineServers map is set according to the
these servers' registering with the master, there can be an inconsistency
between the catalogTracker and the onlineServers if either of these
regionservers is online with respect to zookeeper, but haven't yet registered
with the master (perhaps due to a high latency network between the master and
the regionserver).
The attached testMasterFailoverWithSlowRS.txt patch can be used to modify
TestMasterFailover to cause this NPE.
The proposed fix (provided along with the above test in a separate attachment)
is for the master to use the new verifyMetaTablesAreUp() to wait for both of
the servers named by the catalog tracker's getRootLocation() and
getMetaLocation() to register with the master before the master can continue
with failover.
was:
The following NPE can occur during master failover:
{code}
2012-01-15 17:45:00,314 FATAL
[Master:1;ip-10-166-123-193.us-west-1.compute.internal:36708]
master.HMaster(944): Unhandled exception. Starting shutdown.
java.lang.NullPointerException
at
org.apache.hadoop.hbase.master.AssignmentManager.regionOnline(AssignmentManager.java:724)
at
org.apache.hadoop.hbase.master.AssignmentManager.processFailover(AssignmentManager.java:214)
at
org.apache.hadoop.hbase.master.HMaster.finishInitialization(HMaster.java:396)
at org.apache.hadoop.hbase.master.HMaster.run(HMaster.java:279)
at java.lang.Thread.run(Thread.java:636)
{code}
This is caused by regionOnline() being passed a null serverInfo (its second
parameter).
The AssignmentManager's processFailover() method is passing a null to
regionOnline() because the value that regionOnline is passing, hsi, is set as:
{code}
hsi = this.serverManager.getHServerInfo(this.catalogTracker.getMetaLocation());
{code}
and
{code}
hsi = this.serverManager.getHServerInfo(this.catalogTracker.getRootLocation());
{code}
getHServerInfo(), is defined as:
{code}
public HServerInfo getHServerInfo(final HServerAddress hsa) {
synchronized(this.onlineServers) {
// TODO: This is primitive. Do a better search.
for (Map.EntryString, HServerInfo e: this.onlineServers.entrySet()) {
if (e.getValue().getServerAddress().equals(hsa)) {
return e.getValue();
}
}
}
return null;
}
{code}
This can return null because the onlineServers map does not yet have a value
corresponding to the key supplied by the catalogTracker's getRootLocation() or
getMetaLocation().
Since the catalogTracker uses zookeeper to establish the server locations of
{{-ROOT-}} and {{.META.}}, while the onlineServers map is set according to the
these servers registering with the master, there can be an inconsistency
between the catalogTracker and the onlineServers if either of these
regionservers is online with respect to zookeeper, but haven't yet registered
with the master (perhaps due to a high latency network between the
[jira] [Updated] (HBASE-5202) NPE during Master failover in master.AssignmentManager.regionOnline()
[
https://issues.apache.org/jira/browse/HBASE-5202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eugene Koontz updated HBASE-5202:
-
Description:
The following NPE can occur during master failover:
{code}
2012-01-15 17:45:00,314 FATAL
[Master:1;ip-10-166-123-193.us-west-1.compute.internal:36708]
master.HMaster(944): Unhandled exception. Starting shutdown.
java.lang.NullPointerException
at
org.apache.hadoop.hbase.master.AssignmentManager.regionOnline(AssignmentManager.java:724)
at
org.apache.hadoop.hbase.master.AssignmentManager.processFailover(AssignmentManager.java:214)
at
org.apache.hadoop.hbase.master.HMaster.finishInitialization(HMaster.java:396)
at org.apache.hadoop.hbase.master.HMaster.run(HMaster.java:279)
at java.lang.Thread.run(Thread.java:636)
{code}
This is caused by regionOnline() being passed a null serverInfo (its second
parameter).
The AssignmentManager's processFailover() method is passing a null to
regionOnline() because the value that regionOnline is passing, hsi, is set as:
{code}
hsi = this.serverManager.getHServerInfo(this.catalogTracker.getMetaLocation());
{code}
and
{code}
hsi = this.serverManager.getHServerInfo(this.catalogTracker.getRootLocation());
{code}
getHServerInfo() is defined as:
{code}
public HServerInfo getHServerInfo(final HServerAddress hsa) {
synchronized(this.onlineServers) {
// TODO: This is primitive. Do a better search.
for (Map.EntryString, HServerInfo e: this.onlineServers.entrySet()) {
if (e.getValue().getServerAddress().equals(hsa)) {
return e.getValue();
}
}
}
return null;
}
{code}
This will return null if the onlineServers map does not yet have a value
corresponding to the key supplied by the catalogTracker's getRootLocation() or
getMetaLocation().
Since the catalogTracker uses zookeeper to establish the server locations of
{{-ROOT-}} and {{.META.}}, while the onlineServers map is set according to the
these servers' registering with the master, there can be an inconsistency
between the catalogTracker and the onlineServers if either of these
regionservers is online with respect to zookeeper, but haven't yet registered
with the master (perhaps due to a high latency network between the master and
the regionserver).
The attached testMasterFailoverWithSlowRS.txt patch can be used to modify
TestMasterFailover to cause this NPE.
The proposed fix (provided along with the above test in a separate attachment)
is for the master to use the new verifyMetaTablesAreUp() to wait for both of
the servers named by the catalog tracker's getRootLocation() and
getMetaLocation() to register with the master before the master can continue
with failover.
was:
The following NPE can occur during master failover:
{code}
2012-01-15 17:45:00,314 FATAL
[Master:1;ip-10-166-123-193.us-west-1.compute.internal:36708]
master.HMaster(944): Unhandled exception. Starting shutdown.
java.lang.NullPointerException
at
org.apache.hadoop.hbase.master.AssignmentManager.regionOnline(AssignmentManager.java:724)
at
org.apache.hadoop.hbase.master.AssignmentManager.processFailover(AssignmentManager.java:214)
at
org.apache.hadoop.hbase.master.HMaster.finishInitialization(HMaster.java:396)
at org.apache.hadoop.hbase.master.HMaster.run(HMaster.java:279)
at java.lang.Thread.run(Thread.java:636)
{code}
This is caused by regionOnline() being passed a null serverInfo (its second
parameter).
The AssignmentManager's processFailover() method is passing a null to
regionOnline() because the value that regionOnline is passing, hsi, is set as:
{code}
hsi = this.serverManager.getHServerInfo(this.catalogTracker.getMetaLocation());
{code}
and
{code}
hsi = this.serverManager.getHServerInfo(this.catalogTracker.getRootLocation());
{code}
getHServerInfo(), is defined as:
{code}
public HServerInfo getHServerInfo(final HServerAddress hsa) {
synchronized(this.onlineServers) {
// TODO: This is primitive. Do a better search.
for (Map.EntryString, HServerInfo e: this.onlineServers.entrySet()) {
if (e.getValue().getServerAddress().equals(hsa)) {
return e.getValue();
}
}
}
return null;
}
{code}
This will return null if the onlineServers map does not yet have a value
corresponding to the key supplied by the catalogTracker's getRootLocation() or
getMetaLocation().
Since the catalogTracker uses zookeeper to establish the server locations of
{{-ROOT-}} and {{.META.}}, while the onlineServers map is set according to the
these servers' registering with the master, there can be an inconsistency
between the catalogTracker and the onlineServers if either of these
regionservers is online with respect to zookeeper, but haven't yet registered
with the master (perhaps due to a high latency network between the master
[jira] [Updated] (HBASE-3933) Hmaster throw NullPointerException
[
https://issues.apache.org/jira/browse/HBASE-3933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eugene Koontz updated HBASE-3933:
-
Attachment: HBASE-3933.patch
increase test timeout on new
testMasterFailoverWithSlowRS() test.
Hmaster throw NullPointerException
--
Key: HBASE-3933
URL: https://issues.apache.org/jira/browse/HBASE-3933
Project: HBase
Issue Type: Bug
Components: master
Affects Versions: 0.90.6
Reporter: gaojinchao
Assignee: Eugene Koontz
Attachments: HBASE-3933.patch, HBASE-3933.patch, Hmastersetup0.90
NullPointerException while hmaster starting.
{code}
java.lang.NullPointerException
at java.util.TreeMap.getEntry(TreeMap.java:324)
at java.util.TreeMap.get(TreeMap.java:255)
at
org.apache.hadoop.hbase.master.AssignmentManager.addToServers(AssignmentManager.java:1512)
at
org.apache.hadoop.hbase.master.AssignmentManager.regionOnline(AssignmentManager.java:606)
at
org.apache.hadoop.hbase.master.AssignmentManager.processFailover(AssignmentManager.java:214)
at
org.apache.hadoop.hbase.master.HMaster.finishInitialization(HMaster.java:402)
at org.apache.hadoop.hbase.master.HMaster.run(HMaster.java:283)
{code}
--
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-3933) Hmaster throw NullPointerException
[
https://issues.apache.org/jira/browse/HBASE-3933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eugene Koontz updated HBASE-3933:
-
Affects Version/s: (was: 0.90.3)
0.90.6
Status: Patch Available (was: Reopened)
Adds new HMaster::verifyMetaTablesAreUp() method to avoid NPE in
AssignmentManager::processFailover().
Hmaster throw NullPointerException
--
Key: HBASE-3933
URL: https://issues.apache.org/jira/browse/HBASE-3933
Project: HBase
Issue Type: Bug
Components: master
Affects Versions: 0.90.6
Reporter: gaojinchao
Assignee: Eugene Koontz
Attachments: HBASE-3993.patch, Hmastersetup0.90
NullPointerException while hmaster starting.
{code}
java.lang.NullPointerException
at java.util.TreeMap.getEntry(TreeMap.java:324)
at java.util.TreeMap.get(TreeMap.java:255)
at
org.apache.hadoop.hbase.master.AssignmentManager.addToServers(AssignmentManager.java:1512)
at
org.apache.hadoop.hbase.master.AssignmentManager.regionOnline(AssignmentManager.java:606)
at
org.apache.hadoop.hbase.master.AssignmentManager.processFailover(AssignmentManager.java:214)
at
org.apache.hadoop.hbase.master.HMaster.finishInitialization(HMaster.java:402)
at org.apache.hadoop.hbase.master.HMaster.run(HMaster.java:283)
{code}
--
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-3933) Hmaster throw NullPointerException
[
https://issues.apache.org/jira/browse/HBASE-3933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eugene Koontz updated HBASE-3933:
-
Attachment: HBASE-3993.patch
Hmaster throw NullPointerException
--
Key: HBASE-3933
URL: https://issues.apache.org/jira/browse/HBASE-3933
Project: HBase
Issue Type: Bug
Components: master
Affects Versions: 0.90.6
Reporter: gaojinchao
Assignee: Eugene Koontz
Attachments: HBASE-3993.patch, Hmastersetup0.90
NullPointerException while hmaster starting.
{code}
java.lang.NullPointerException
at java.util.TreeMap.getEntry(TreeMap.java:324)
at java.util.TreeMap.get(TreeMap.java:255)
at
org.apache.hadoop.hbase.master.AssignmentManager.addToServers(AssignmentManager.java:1512)
at
org.apache.hadoop.hbase.master.AssignmentManager.regionOnline(AssignmentManager.java:606)
at
org.apache.hadoop.hbase.master.AssignmentManager.processFailover(AssignmentManager.java:214)
at
org.apache.hadoop.hbase.master.HMaster.finishInitialization(HMaster.java:402)
at org.apache.hadoop.hbase.master.HMaster.run(HMaster.java:283)
{code}
--
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-3933) Hmaster throw NullPointerException
[
https://issues.apache.org/jira/browse/HBASE-3933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eugene Koontz updated HBASE-3933:
-
Attachment: (was: HBASE-3993.patch)
Hmaster throw NullPointerException
--
Key: HBASE-3933
URL: https://issues.apache.org/jira/browse/HBASE-3933
Project: HBase
Issue Type: Bug
Components: master
Affects Versions: 0.90.6
Reporter: gaojinchao
Assignee: Eugene Koontz
Attachments: HBASE-3933.patch, Hmastersetup0.90
NullPointerException while hmaster starting.
{code}
java.lang.NullPointerException
at java.util.TreeMap.getEntry(TreeMap.java:324)
at java.util.TreeMap.get(TreeMap.java:255)
at
org.apache.hadoop.hbase.master.AssignmentManager.addToServers(AssignmentManager.java:1512)
at
org.apache.hadoop.hbase.master.AssignmentManager.regionOnline(AssignmentManager.java:606)
at
org.apache.hadoop.hbase.master.AssignmentManager.processFailover(AssignmentManager.java:214)
at
org.apache.hadoop.hbase.master.HMaster.finishInitialization(HMaster.java:402)
at org.apache.hadoop.hbase.master.HMaster.run(HMaster.java:283)
{code}
--
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-3933) Hmaster throw NullPointerException
[
https://issues.apache.org/jira/browse/HBASE-3933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eugene Koontz updated HBASE-3933:
-
Attachment: HBASE-3933.patch
Hmaster throw NullPointerException
--
Key: HBASE-3933
URL: https://issues.apache.org/jira/browse/HBASE-3933
Project: HBase
Issue Type: Bug
Components: master
Affects Versions: 0.90.6
Reporter: gaojinchao
Assignee: Eugene Koontz
Attachments: HBASE-3933.patch, Hmastersetup0.90
NullPointerException while hmaster starting.
{code}
java.lang.NullPointerException
at java.util.TreeMap.getEntry(TreeMap.java:324)
at java.util.TreeMap.get(TreeMap.java:255)
at
org.apache.hadoop.hbase.master.AssignmentManager.addToServers(AssignmentManager.java:1512)
at
org.apache.hadoop.hbase.master.AssignmentManager.regionOnline(AssignmentManager.java:606)
at
org.apache.hadoop.hbase.master.AssignmentManager.processFailover(AssignmentManager.java:214)
at
org.apache.hadoop.hbase.master.HMaster.finishInitialization(HMaster.java:402)
at org.apache.hadoop.hbase.master.HMaster.run(HMaster.java:283)
{code}
--
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-3933) Hmaster throw NullPointerException
[
https://issues.apache.org/jira/browse/HBASE-3933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eugene Koontz updated HBASE-3933:
-
Attachment: (was: HBASE-3933.patch)
Hmaster throw NullPointerException
--
Key: HBASE-3933
URL: https://issues.apache.org/jira/browse/HBASE-3933
Project: HBase
Issue Type: Bug
Components: master
Affects Versions: 0.90.6
Reporter: gaojinchao
Assignee: Eugene Koontz
Attachments: Hmastersetup0.90
NullPointerException while hmaster starting.
{code}
java.lang.NullPointerException
at java.util.TreeMap.getEntry(TreeMap.java:324)
at java.util.TreeMap.get(TreeMap.java:255)
at
org.apache.hadoop.hbase.master.AssignmentManager.addToServers(AssignmentManager.java:1512)
at
org.apache.hadoop.hbase.master.AssignmentManager.regionOnline(AssignmentManager.java:606)
at
org.apache.hadoop.hbase.master.AssignmentManager.processFailover(AssignmentManager.java:214)
at
org.apache.hadoop.hbase.master.HMaster.finishInitialization(HMaster.java:402)
at org.apache.hadoop.hbase.master.HMaster.run(HMaster.java:283)
{code}
--
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-3933) Hmaster throw NullPointerException
[
https://issues.apache.org/jira/browse/HBASE-3933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eugene Koontz updated HBASE-3933:
-
Attachment: HBASE-3933.patch
Hmaster throw NullPointerException
--
Key: HBASE-3933
URL: https://issues.apache.org/jira/browse/HBASE-3933
Project: HBase
Issue Type: Bug
Components: master
Affects Versions: 0.90.6
Reporter: gaojinchao
Assignee: Eugene Koontz
Attachments: HBASE-3933.patch, Hmastersetup0.90
NullPointerException while hmaster starting.
{code}
java.lang.NullPointerException
at java.util.TreeMap.getEntry(TreeMap.java:324)
at java.util.TreeMap.get(TreeMap.java:255)
at
org.apache.hadoop.hbase.master.AssignmentManager.addToServers(AssignmentManager.java:1512)
at
org.apache.hadoop.hbase.master.AssignmentManager.regionOnline(AssignmentManager.java:606)
at
org.apache.hadoop.hbase.master.AssignmentManager.processFailover(AssignmentManager.java:214)
at
org.apache.hadoop.hbase.master.HMaster.finishInitialization(HMaster.java:402)
at org.apache.hadoop.hbase.master.HMaster.run(HMaster.java:283)
{code}
--
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-5044) Clarify solution for problem described on http://hbase.apache.org/book/trouble.mapreduce.html
[
https://issues.apache.org/jira/browse/HBASE-5044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eugene Koontz updated HBASE-5044:
-
Attachment: HBASE-5044.patch
Clarify solution for problem described on
http://hbase.apache.org/book/trouble.mapreduce.html
-
Key: HBASE-5044
URL: https://issues.apache.org/jira/browse/HBASE-5044
Project: HBase
Issue Type: Improvement
Components: documentation
Reporter: Eugene Koontz
Assignee: Eugene Koontz
Priority: Trivial
Fix For: 0.90.4, 0.94.0
Attachments: HBASE-5044.patch
Add some documentation regarding how to fix the problem described on :
http://hbase.apache.org/apidocs/org/apache/hadoop/hbase/mapreduce/package-summary.html#classpath
Should be some text like:
{quote}
You should run your mapreduce job with your {{HADOOP_CLASSPATH}} set to
include the HBase jar and HBase's configured classpath. For example
(substitute your own hbase jar location for is {{hbase-0.90.0-SNAPSHOT.jar}}):
{quote}
{code}
HADOOP_CLASSPATH=${HBASE_HOME}/target/hbase-0.90.0-SNAPSHOT.jar:`${HBASE_HOME}/bin/hbase
classpath` ${HADOOP_HOME}/bin/hadoop jar
${HBASE_HOME}/target/hbase-0.90.0-SNAPSHOT.jar rowcounter usertable
{code}
--
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-5044) Clarify solution for problem described on http://hbase.apache.org/book/trouble.mapreduce.html
[
https://issues.apache.org/jira/browse/HBASE-5044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eugene Koontz updated HBASE-5044:
-
Status: Patch Available (was: Open)
patch to src/docbkx/troubleshooting.xml
Clarify solution for problem described on
http://hbase.apache.org/book/trouble.mapreduce.html
-
Key: HBASE-5044
URL: https://issues.apache.org/jira/browse/HBASE-5044
Project: HBase
Issue Type: Improvement
Components: documentation
Reporter: Eugene Koontz
Assignee: Eugene Koontz
Priority: Trivial
Fix For: 0.94.0, 0.90.4
Attachments: HBASE-5044.patch
Add some documentation regarding how to fix the problem described on :
http://hbase.apache.org/apidocs/org/apache/hadoop/hbase/mapreduce/package-summary.html#classpath
Should be some text like:
{quote}
You should run your mapreduce job with your {{HADOOP_CLASSPATH}} set to
include the HBase jar and HBase's configured classpath. For example
(substitute your own hbase jar location for is {{hbase-0.90.0-SNAPSHOT.jar}}):
{quote}
{code}
HADOOP_CLASSPATH=${HBASE_HOME}/target/hbase-0.90.0-SNAPSHOT.jar:`${HBASE_HOME}/bin/hbase
classpath` ${HADOOP_HOME}/bin/hadoop jar
${HBASE_HOME}/target/hbase-0.90.0-SNAPSHOT.jar rowcounter usertable
{code}
--
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-4960) Document mutual authentication between HBase and Zookeeper using SASL
[ https://issues.apache.org/jira/browse/HBASE-4960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eugene Koontz updated HBASE-4960: - Release Note: adds content to src/docbkx/configuration.xml regarding Zookeeper/HBase mutual authentication, including Kerberos-related content. Status: Patch Available (was: Open) Document mutual authentication between HBase and Zookeeper using SASL - Key: HBASE-4960 URL: https://issues.apache.org/jira/browse/HBASE-4960 Project: HBase Issue Type: Sub-task Components: documentation, security Reporter: Eugene Koontz Assignee: Eugene Koontz Labels: documentation, security Provide documentation for the work done in HBASE-2418 (add support for ZooKeeper authentication). -- 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-4960) Document mutual authentication between HBase and Zookeeper using SASL
[ https://issues.apache.org/jira/browse/HBASE-4960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eugene Koontz updated HBASE-4960: - Attachment: HBASE-4960.patch Document mutual authentication between HBase and Zookeeper using SASL - Key: HBASE-4960 URL: https://issues.apache.org/jira/browse/HBASE-4960 Project: HBase Issue Type: Sub-task Components: documentation, security Reporter: Eugene Koontz Assignee: Eugene Koontz Labels: documentation, security Attachments: HBASE-4960.patch Provide documentation for the work done in HBASE-2418 (add support for ZooKeeper authentication). -- 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-4960) Document mutual authentication between HBase and Zookeeper using SASL
[ https://issues.apache.org/jira/browse/HBASE-4960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eugene Koontz updated HBASE-4960: - Attachment: HBASE-4960.patch Fix two typos, and add new 'Configuration from scratch' section addresses cached_classpath issue, and add 'Future Improvements' section. Document mutual authentication between HBase and Zookeeper using SASL - Key: HBASE-4960 URL: https://issues.apache.org/jira/browse/HBASE-4960 Project: HBase Issue Type: Sub-task Components: documentation, security Reporter: Eugene Koontz Assignee: Eugene Koontz Labels: documentation, security Attachments: HBASE-4960.patch, HBASE-4960.patch Provide documentation for the work done in HBASE-2418 (add support for ZooKeeper authentication). -- 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-4791) Allow Secure Zookeeper JAAS configuration to be programmatically set (rather than only by reading JAAS configuration file)
[ https://issues.apache.org/jira/browse/HBASE-4791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eugene Koontz updated HBASE-4791: - Issue Type: Improvement (was: Bug) Allow Secure Zookeeper JAAS configuration to be programmatically set (rather than only by reading JAAS configuration file) -- Key: HBASE-4791 URL: https://issues.apache.org/jira/browse/HBASE-4791 Project: HBase Issue Type: Improvement Reporter: Eugene Koontz Assignee: Eugene Koontz Labels: security, zookeeper In the currently proposed fix for HBASE-2418, there must be a JAAS file specified in System.setProperty(java.security.auth.login.config). However, it might be preferable to construct a JAAS configuration programmatically, as is done with secure Hadoop (see https://github.com/apache/hadoop-common/blob/a48eceb62c9b5c1a5d71ee2945d9eea2ed62527b/src/java/org/apache/hadoop/security/UserGroupInformation.java#L175). This would have the benefit of avoiding a usage of a system property setting, and allow instead an HBase-local configuration setting. -- 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-4832) TestRegionServerCoprocessorExceptionWithAbort fails if the region server stops too fast
[
https://issues.apache.org/jira/browse/HBASE-4832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eugene Koontz updated HBASE-4832:
-
Attachment: HBASE-4832.patch
-Removes (timeout=3) from @Test per nkeywal's suggestion.
-Add LOG.debug() concerning where interrupt occurs.
TestRegionServerCoprocessorExceptionWithAbort fails if the region server
stops too fast
---
Key: HBASE-4832
URL: https://issues.apache.org/jira/browse/HBASE-4832
Project: HBase
Issue Type: Bug
Components: coprocessors, test
Affects Versions: 0.94.0
Reporter: nkeywal
Assignee: Eugene Koontz
Priority: Minor
Attachments: 4832-timeout.txt, 4832_trunk_hregionserver.patch,
HBASE-4832.patch, HBASE-4832.patch, HBASE-4832.patch
The current implementation of HRegionServer#stop is
{noformat}
public void stop(final String msg) {
this.stopped = true;
LOG.info(STOPPED: + msg);
synchronized (this) {
// Wakes run() if it is sleeping
notifyAll(); // FindBugs NN_NAKED_NOTIFY
}
}
{noformat}
The notification is sent on the wrong object and does nothing. As a
consequence, the region server continues to sleep instead of waking up and
stopping immediately. A correct implementation is:
{noformat}
public void stop(final String msg) {
this.stopped = true;
LOG.info(STOPPED: + msg);
// Wakes run() if it is sleeping
sleeper.skipSleepCycle();
}
{noformat}
Then the region server stops immediately. This makes the region server stops
0,5s faster on average, which is quite useful for unit tests.
However, with this fix, TestRegionServerCoprocessorExceptionWithAbort does
not work.
It likely because the code does no expect the region server to stop that fast.
The exception is:
{noformat}
testExceptionFromCoprocessorDuringPut(org.apache.hadoop.hbase.coprocessor.TestRegionServerCoprocessorExceptionWithAbort)
Time elapsed: 30.06 sec ERROR!
java.lang.Exception: test timed out after 3 milliseconds
at java.lang.Throwable.fillInStackTrace(Native Method)
at java.lang.Throwable.init(Throwable.java:196)
at java.lang.Exception.init(Exception.java:41)
at java.lang.InterruptedException.init(InterruptedException.java:48)
at java.lang.Thread.sleep(Native Method)
at
org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.locateRegionInMeta(HConnectionManager.java:1019)
at
org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.locateRegion(HConnectionManager.java:804)
at
org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.relocateRegion(HConnectionManager.java:778)
at
org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.getRegionLocation(HConnectionManager.java:697)
at
org.apache.hadoop.hbase.client.ServerCallable.connect(ServerCallable.java:75)
at
org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.getRegionServerWithRetries(HConnectionManager.java:1280)
at org.apache.hadoop.hbase.client.HTable.getRowOrBefore(HTable.java:585)
at
org.apache.hadoop.hbase.client.MetaScanner.metaScan(MetaScanner.java:154)
at
org.apache.hadoop.hbase.client.MetaScanner.access$000(MetaScanner.java:52)
at
org.apache.hadoop.hbase.client.MetaScanner$1.connect(MetaScanner.java:130)
at
org.apache.hadoop.hbase.client.MetaScanner$1.connect(MetaScanner.java:127)
at
org.apache.hadoop.hbase.client.HConnectionManager.execute(HConnectionManager.java:357)
at
org.apache.hadoop.hbase.client.MetaScanner.metaScan(MetaScanner.java:127)
at
org.apache.hadoop.hbase.client.MetaScanner.metaScan(MetaScanner.java:103)
at
org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.prefetchRegionCache(HConnectionManager.java:866)
at
org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.locateRegionInMeta(HConnectionManager.java:920)
at
org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.locateRegion(HConnectionManager.java:808)
at
org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.processBatchCallback(HConnectionManager.java:1469)
at
org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.processBatch(HConnectionManager.java:1354)
at org.apache.hadoop.hbase.client.HTable.flushCommits(HTable.java:892)
at org.apache.hadoop.hbase.client.HTable.doPut(HTable.java:750)
at org.apache.hadoop.hbase.client.HTable.put(HTable.java:725)
at
[jira] [Updated] (HBASE-4832) TestRegionServerCoprocessorExceptionWithAbort fails if the region server stops too fast
[
https://issues.apache.org/jira/browse/HBASE-4832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eugene Koontz updated HBASE-4832:
-
Attachment: HBASE-4832.patch
git diff --no-prefix
TestRegionServerCoprocessorExceptionWithAbort fails if the region server
stops too fast
---
Key: HBASE-4832
URL: https://issues.apache.org/jira/browse/HBASE-4832
Project: HBase
Issue Type: Bug
Components: coprocessors, test
Affects Versions: 0.94.0
Reporter: nkeywal
Assignee: Eugene Koontz
Priority: Minor
Attachments: 4832-timeout.txt, 4832_trunk_hregionserver.patch,
HBASE-4832.patch, HBASE-4832.patch, HBASE-4832.patch, HBASE-4832.patch
The current implementation of HRegionServer#stop is
{noformat}
public void stop(final String msg) {
this.stopped = true;
LOG.info(STOPPED: + msg);
synchronized (this) {
// Wakes run() if it is sleeping
notifyAll(); // FindBugs NN_NAKED_NOTIFY
}
}
{noformat}
The notification is sent on the wrong object and does nothing. As a
consequence, the region server continues to sleep instead of waking up and
stopping immediately. A correct implementation is:
{noformat}
public void stop(final String msg) {
this.stopped = true;
LOG.info(STOPPED: + msg);
// Wakes run() if it is sleeping
sleeper.skipSleepCycle();
}
{noformat}
Then the region server stops immediately. This makes the region server stops
0,5s faster on average, which is quite useful for unit tests.
However, with this fix, TestRegionServerCoprocessorExceptionWithAbort does
not work.
It likely because the code does no expect the region server to stop that fast.
The exception is:
{noformat}
testExceptionFromCoprocessorDuringPut(org.apache.hadoop.hbase.coprocessor.TestRegionServerCoprocessorExceptionWithAbort)
Time elapsed: 30.06 sec ERROR!
java.lang.Exception: test timed out after 3 milliseconds
at java.lang.Throwable.fillInStackTrace(Native Method)
at java.lang.Throwable.init(Throwable.java:196)
at java.lang.Exception.init(Exception.java:41)
at java.lang.InterruptedException.init(InterruptedException.java:48)
at java.lang.Thread.sleep(Native Method)
at
org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.locateRegionInMeta(HConnectionManager.java:1019)
at
org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.locateRegion(HConnectionManager.java:804)
at
org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.relocateRegion(HConnectionManager.java:778)
at
org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.getRegionLocation(HConnectionManager.java:697)
at
org.apache.hadoop.hbase.client.ServerCallable.connect(ServerCallable.java:75)
at
org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.getRegionServerWithRetries(HConnectionManager.java:1280)
at org.apache.hadoop.hbase.client.HTable.getRowOrBefore(HTable.java:585)
at
org.apache.hadoop.hbase.client.MetaScanner.metaScan(MetaScanner.java:154)
at
org.apache.hadoop.hbase.client.MetaScanner.access$000(MetaScanner.java:52)
at
org.apache.hadoop.hbase.client.MetaScanner$1.connect(MetaScanner.java:130)
at
org.apache.hadoop.hbase.client.MetaScanner$1.connect(MetaScanner.java:127)
at
org.apache.hadoop.hbase.client.HConnectionManager.execute(HConnectionManager.java:357)
at
org.apache.hadoop.hbase.client.MetaScanner.metaScan(MetaScanner.java:127)
at
org.apache.hadoop.hbase.client.MetaScanner.metaScan(MetaScanner.java:103)
at
org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.prefetchRegionCache(HConnectionManager.java:866)
at
org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.locateRegionInMeta(HConnectionManager.java:920)
at
org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.locateRegion(HConnectionManager.java:808)
at
org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.processBatchCallback(HConnectionManager.java:1469)
at
org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.processBatch(HConnectionManager.java:1354)
at org.apache.hadoop.hbase.client.HTable.flushCommits(HTable.java:892)
at org.apache.hadoop.hbase.client.HTable.doPut(HTable.java:750)
at org.apache.hadoop.hbase.client.HTable.put(HTable.java:725)
at
[jira] [Updated] (HBASE-4832) TestRegionServerCoprocessorExceptionWithAbort fails if the region server stops too fast
[
https://issues.apache.org/jira/browse/HBASE-4832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eugene Koontz updated HBASE-4832:
-
Release Note:
This incorporates nkeywal's earlier patch to this JIRA, and allows
TestRegionServerCoprocessortWithAbort() to work with it. It changes the test to
use a Zookeeper watcher in a separate thread to watch for the regionserver to
abort. (This is also what is currently done with
TestMasterCoprocessorWithAbort()).
In my testing, repeated iterations (30+) of
TestRegionServerCoprocessortWithAbort() succeed.
Status: Patch Available (was: Open)
TestRegionServerCoprocessorExceptionWithAbort fails if the region server
stops too fast
---
Key: HBASE-4832
URL: https://issues.apache.org/jira/browse/HBASE-4832
Project: HBase
Issue Type: Bug
Components: coprocessors, test
Affects Versions: 0.94.0
Reporter: nkeywal
Assignee: Eugene Koontz
Priority: Minor
Attachments: 4832_trunk_hregionserver.patch
The current implementation of HRegionServer#stop is
{noformat}
public void stop(final String msg) {
this.stopped = true;
LOG.info(STOPPED: + msg);
synchronized (this) {
// Wakes run() if it is sleeping
notifyAll(); // FindBugs NN_NAKED_NOTIFY
}
}
{noformat}
The notification is sent on the wrong object and does nothing. As a
consequence, the region server continues to sleep instead of waking up and
stopping immediately. A correct implementation is:
{noformat}
public void stop(final String msg) {
this.stopped = true;
LOG.info(STOPPED: + msg);
// Wakes run() if it is sleeping
sleeper.skipSleepCycle();
}
{noformat}
Then the region server stops immediately. This makes the region server stops
0,5s faster on average, which is quite useful for unit tests.
However, with this fix, TestRegionServerCoprocessorExceptionWithAbort does
not work.
It likely because the code does no expect the region server to stop that fast.
The exception is:
{noformat}
testExceptionFromCoprocessorDuringPut(org.apache.hadoop.hbase.coprocessor.TestRegionServerCoprocessorExceptionWithAbort)
Time elapsed: 30.06 sec ERROR!
java.lang.Exception: test timed out after 3 milliseconds
at java.lang.Throwable.fillInStackTrace(Native Method)
at java.lang.Throwable.init(Throwable.java:196)
at java.lang.Exception.init(Exception.java:41)
at java.lang.InterruptedException.init(InterruptedException.java:48)
at java.lang.Thread.sleep(Native Method)
at
org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.locateRegionInMeta(HConnectionManager.java:1019)
at
org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.locateRegion(HConnectionManager.java:804)
at
org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.relocateRegion(HConnectionManager.java:778)
at
org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.getRegionLocation(HConnectionManager.java:697)
at
org.apache.hadoop.hbase.client.ServerCallable.connect(ServerCallable.java:75)
at
org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.getRegionServerWithRetries(HConnectionManager.java:1280)
at org.apache.hadoop.hbase.client.HTable.getRowOrBefore(HTable.java:585)
at
org.apache.hadoop.hbase.client.MetaScanner.metaScan(MetaScanner.java:154)
at
org.apache.hadoop.hbase.client.MetaScanner.access$000(MetaScanner.java:52)
at
org.apache.hadoop.hbase.client.MetaScanner$1.connect(MetaScanner.java:130)
at
org.apache.hadoop.hbase.client.MetaScanner$1.connect(MetaScanner.java:127)
at
org.apache.hadoop.hbase.client.HConnectionManager.execute(HConnectionManager.java:357)
at
org.apache.hadoop.hbase.client.MetaScanner.metaScan(MetaScanner.java:127)
at
org.apache.hadoop.hbase.client.MetaScanner.metaScan(MetaScanner.java:103)
at
org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.prefetchRegionCache(HConnectionManager.java:866)
at
org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.locateRegionInMeta(HConnectionManager.java:920)
at
org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.locateRegion(HConnectionManager.java:808)
at
org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.processBatchCallback(HConnectionManager.java:1469)
at
org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.processBatch(HConnectionManager.java:1354)
at
[jira] [Updated] (HBASE-4832) TestRegionServerCoprocessorExceptionWithAbort fails if the region server stops too fast
[
https://issues.apache.org/jira/browse/HBASE-4832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eugene Koontz updated HBASE-4832:
-
Attachment: HBASE-4832.patch
TestRegionServerCoprocessorExceptionWithAbort fails if the region server
stops too fast
---
Key: HBASE-4832
URL: https://issues.apache.org/jira/browse/HBASE-4832
Project: HBase
Issue Type: Bug
Components: coprocessors, test
Affects Versions: 0.94.0
Reporter: nkeywal
Assignee: Eugene Koontz
Priority: Minor
Attachments: 4832_trunk_hregionserver.patch, HBASE-4832.patch
The current implementation of HRegionServer#stop is
{noformat}
public void stop(final String msg) {
this.stopped = true;
LOG.info(STOPPED: + msg);
synchronized (this) {
// Wakes run() if it is sleeping
notifyAll(); // FindBugs NN_NAKED_NOTIFY
}
}
{noformat}
The notification is sent on the wrong object and does nothing. As a
consequence, the region server continues to sleep instead of waking up and
stopping immediately. A correct implementation is:
{noformat}
public void stop(final String msg) {
this.stopped = true;
LOG.info(STOPPED: + msg);
// Wakes run() if it is sleeping
sleeper.skipSleepCycle();
}
{noformat}
Then the region server stops immediately. This makes the region server stops
0,5s faster on average, which is quite useful for unit tests.
However, with this fix, TestRegionServerCoprocessorExceptionWithAbort does
not work.
It likely because the code does no expect the region server to stop that fast.
The exception is:
{noformat}
testExceptionFromCoprocessorDuringPut(org.apache.hadoop.hbase.coprocessor.TestRegionServerCoprocessorExceptionWithAbort)
Time elapsed: 30.06 sec ERROR!
java.lang.Exception: test timed out after 3 milliseconds
at java.lang.Throwable.fillInStackTrace(Native Method)
at java.lang.Throwable.init(Throwable.java:196)
at java.lang.Exception.init(Exception.java:41)
at java.lang.InterruptedException.init(InterruptedException.java:48)
at java.lang.Thread.sleep(Native Method)
at
org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.locateRegionInMeta(HConnectionManager.java:1019)
at
org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.locateRegion(HConnectionManager.java:804)
at
org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.relocateRegion(HConnectionManager.java:778)
at
org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.getRegionLocation(HConnectionManager.java:697)
at
org.apache.hadoop.hbase.client.ServerCallable.connect(ServerCallable.java:75)
at
org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.getRegionServerWithRetries(HConnectionManager.java:1280)
at org.apache.hadoop.hbase.client.HTable.getRowOrBefore(HTable.java:585)
at
org.apache.hadoop.hbase.client.MetaScanner.metaScan(MetaScanner.java:154)
at
org.apache.hadoop.hbase.client.MetaScanner.access$000(MetaScanner.java:52)
at
org.apache.hadoop.hbase.client.MetaScanner$1.connect(MetaScanner.java:130)
at
org.apache.hadoop.hbase.client.MetaScanner$1.connect(MetaScanner.java:127)
at
org.apache.hadoop.hbase.client.HConnectionManager.execute(HConnectionManager.java:357)
at
org.apache.hadoop.hbase.client.MetaScanner.metaScan(MetaScanner.java:127)
at
org.apache.hadoop.hbase.client.MetaScanner.metaScan(MetaScanner.java:103)
at
org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.prefetchRegionCache(HConnectionManager.java:866)
at
org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.locateRegionInMeta(HConnectionManager.java:920)
at
org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.locateRegion(HConnectionManager.java:808)
at
org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.processBatchCallback(HConnectionManager.java:1469)
at
org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.processBatch(HConnectionManager.java:1354)
at org.apache.hadoop.hbase.client.HTable.flushCommits(HTable.java:892)
at org.apache.hadoop.hbase.client.HTable.doPut(HTable.java:750)
at org.apache.hadoop.hbase.client.HTable.put(HTable.java:725)
at
org.apache.hadoop.hbase.coprocessor.TestRegionServerCoprocessorExceptionWithAbort.testExceptionFromCoprocessorDuringPut(TestRegionServerCoprocessorExceptionWithAbort.java:84)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
[jira] [Updated] (HBASE-4832) TestRegionServerCoprocessorExceptionWithAbort fails if the region server stops too fast
[
https://issues.apache.org/jira/browse/HBASE-4832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eugene Koontz updated HBASE-4832:
-
Attachment: HBASE-4832.patch
New version of the patch: parameterize test timeout (thanks to Ted Yu) and use
this timeout amount in Thread.sleep() near end of
testExceptionFromCoprocessorDuringPut().
TestRegionServerCoprocessorExceptionWithAbort fails if the region server
stops too fast
---
Key: HBASE-4832
URL: https://issues.apache.org/jira/browse/HBASE-4832
Project: HBase
Issue Type: Bug
Components: coprocessors, test
Affects Versions: 0.94.0
Reporter: nkeywal
Assignee: Eugene Koontz
Priority: Minor
Attachments: 4832-timeout.txt, 4832_trunk_hregionserver.patch,
HBASE-4832.patch, HBASE-4832.patch
The current implementation of HRegionServer#stop is
{noformat}
public void stop(final String msg) {
this.stopped = true;
LOG.info(STOPPED: + msg);
synchronized (this) {
// Wakes run() if it is sleeping
notifyAll(); // FindBugs NN_NAKED_NOTIFY
}
}
{noformat}
The notification is sent on the wrong object and does nothing. As a
consequence, the region server continues to sleep instead of waking up and
stopping immediately. A correct implementation is:
{noformat}
public void stop(final String msg) {
this.stopped = true;
LOG.info(STOPPED: + msg);
// Wakes run() if it is sleeping
sleeper.skipSleepCycle();
}
{noformat}
Then the region server stops immediately. This makes the region server stops
0,5s faster on average, which is quite useful for unit tests.
However, with this fix, TestRegionServerCoprocessorExceptionWithAbort does
not work.
It likely because the code does no expect the region server to stop that fast.
The exception is:
{noformat}
testExceptionFromCoprocessorDuringPut(org.apache.hadoop.hbase.coprocessor.TestRegionServerCoprocessorExceptionWithAbort)
Time elapsed: 30.06 sec ERROR!
java.lang.Exception: test timed out after 3 milliseconds
at java.lang.Throwable.fillInStackTrace(Native Method)
at java.lang.Throwable.init(Throwable.java:196)
at java.lang.Exception.init(Exception.java:41)
at java.lang.InterruptedException.init(InterruptedException.java:48)
at java.lang.Thread.sleep(Native Method)
at
org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.locateRegionInMeta(HConnectionManager.java:1019)
at
org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.locateRegion(HConnectionManager.java:804)
at
org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.relocateRegion(HConnectionManager.java:778)
at
org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.getRegionLocation(HConnectionManager.java:697)
at
org.apache.hadoop.hbase.client.ServerCallable.connect(ServerCallable.java:75)
at
org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.getRegionServerWithRetries(HConnectionManager.java:1280)
at org.apache.hadoop.hbase.client.HTable.getRowOrBefore(HTable.java:585)
at
org.apache.hadoop.hbase.client.MetaScanner.metaScan(MetaScanner.java:154)
at
org.apache.hadoop.hbase.client.MetaScanner.access$000(MetaScanner.java:52)
at
org.apache.hadoop.hbase.client.MetaScanner$1.connect(MetaScanner.java:130)
at
org.apache.hadoop.hbase.client.MetaScanner$1.connect(MetaScanner.java:127)
at
org.apache.hadoop.hbase.client.HConnectionManager.execute(HConnectionManager.java:357)
at
org.apache.hadoop.hbase.client.MetaScanner.metaScan(MetaScanner.java:127)
at
org.apache.hadoop.hbase.client.MetaScanner.metaScan(MetaScanner.java:103)
at
org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.prefetchRegionCache(HConnectionManager.java:866)
at
org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.locateRegionInMeta(HConnectionManager.java:920)
at
org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.locateRegion(HConnectionManager.java:808)
at
org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.processBatchCallback(HConnectionManager.java:1469)
at
org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.processBatch(HConnectionManager.java:1354)
at org.apache.hadoop.hbase.client.HTable.flushCommits(HTable.java:892)
at org.apache.hadoop.hbase.client.HTable.doPut(HTable.java:750)
at org.apache.hadoop.hbase.client.HTable.put(HTable.java:725)
at
[jira] [Updated] (HBASE-4690) Intermittent TestRegionServerCoprocessorExceptionWithAbort#testExceptionFromCoprocessorDuringPut failure
[ https://issues.apache.org/jira/browse/HBASE-4690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eugene Koontz updated HBASE-4690: - Summary: Intermittent TestRegionServerCoprocessorExceptionWithAbort#testExceptionFromCoprocessorDuringPut failure (was: Intermittent TestRegionServerCoprocessorExceptionWithRemove#testExceptionFromCoprocessorDuringPut failure) Intermittent TestRegionServerCoprocessorExceptionWithAbort#testExceptionFromCoprocessorDuringPut failure Key: HBASE-4690 URL: https://issues.apache.org/jira/browse/HBASE-4690 Project: HBase Issue Type: Test Affects Versions: 0.92.0 Reporter: Ted Yu Assignee: Eugene Koontz Fix For: 0.92.0 See https://builds.apache.org/view/G-L/view/HBase/job/HBase-0.92/83/testReport/junit/org.apache.hadoop.hbase.coprocessor/TestRegionServerCoprocessorExceptionWithAbort/testExceptionFromCoprocessorDuringPut/ Somehow getRSForFirstRegionInTable() wasn't able to retrieve the region server. One fix for this issue is to spin up MiniCluster with 1 region server so that we don't need to search for the region server where first region is hosted. -- 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-4690) Intermittent TestRegionServerCoprocessorExceptionWithRemove#testExceptionFromCoprocessorDuringPut failure
[ https://issues.apache.org/jira/browse/HBASE-4690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eugene Koontz updated HBASE-4690: - Doing git bisect, it seems that both TestRegionServerCoprocessorExceptionWithRemove and TestRegionServerCoprocessorExceptionWithAbort stop working at : 306ab94... HBASE-4300 Start of new-version master fails if old master's znode is hanging around Intermittent TestRegionServerCoprocessorExceptionWithRemove#testExceptionFromCoprocessorDuringPut failure - Key: HBASE-4690 URL: https://issues.apache.org/jira/browse/HBASE-4690 Project: HBase Issue Type: Test Affects Versions: 0.92.0 Reporter: Ted Yu Assignee: Eugene Koontz Fix For: 0.92.0 See https://builds.apache.org/view/G-L/view/HBase/job/HBase-0.92/83/testReport/junit/org.apache.hadoop.hbase.coprocessor/TestRegionServerCoprocessorExceptionWithAbort/testExceptionFromCoprocessorDuringPut/ Somehow getRSForFirstRegionInTable() wasn't able to retrieve the region server. One fix for this issue is to spin up MiniCluster with 1 region server so that we don't need to search for the region server where first region is hosted. -- 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-4693) Consolidate TestRegionServerCoprocessorExceptionWithRemove and TestRegionServerCoprocessorExceptionWithAbort into a single cluster spin-up
[ https://issues.apache.org/jira/browse/HBASE-4693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eugene Koontz updated HBASE-4693: - Summary: Consolidate TestRegionServerCoprocessorExceptionWithRemove and TestRegionServerCoprocessorExceptionWithAbort into a single cluster spin-up (was: Consolidate TestRegionServerCoprocessorExceptionWithRemove and TestRegionServerCoprocessorExceptionWithRemove into a single cluster spin-up) Consolidate TestRegionServerCoprocessorExceptionWithRemove and TestRegionServerCoprocessorExceptionWithAbort into a single cluster spin-up -- Key: HBASE-4693 URL: https://issues.apache.org/jira/browse/HBASE-4693 Project: HBase Issue Type: Improvement Reporter: Eugene Koontz Assignee: Eugene Koontz -- 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-4693) Consolidate TestRegionServerCoprocessorExceptionWithRemove and TestRegionServerCoprocessorExceptionWithAbort into a single cluster spin-up
[ https://issues.apache.org/jira/browse/HBASE-4693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eugene Koontz updated HBASE-4693: - Release Note: Rather than spinning up a cluster per test, instead create one test with: 1. start cluster 2. load buggy coprocessor on one regionserserver with hbase.coprocessor.abortonerror=false (this is the default configuration). 3. trigger coprocessor's NPE and assert that the RS doesn't abort and that the RS removes the coprocessor. 4. restart the RS with a modified configuration with hbase.coprocessor.abortonerror=true. 5. trigger coprocessor's NPE and assert that the RS aborts as expected. was: Rather than spinning up a cluster per test, instead create one test that could be test could be: 1. start cluster 2. load buggy coprocessor on one regionserserver with hbase.coprocessor.abortonerror=false (this is the default configuration). 3. trigger coprocessor's NPE and test that the RS doesn't abort and that the RS removes the coprocessor. 4. restart the RS with a modified configuration with hbase.coprocessor.abortonerror=true. 5. trigger coprocessor's NPE and test that the RS aborts as expected. Consolidate TestRegionServerCoprocessorExceptionWithRemove and TestRegionServerCoprocessorExceptionWithAbort into a single cluster spin-up -- Key: HBASE-4693 URL: https://issues.apache.org/jira/browse/HBASE-4693 Project: HBase Issue Type: Improvement Reporter: Eugene Koontz Assignee: Eugene Koontz -- 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-4480) Testing script to simplify local testing
[ https://issues.apache.org/jira/browse/HBASE-4480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eugene Koontz updated HBASE-4480: - Summary: Testing script to simplify local testing (was: Testing script to simplfy local testing) Testing script to simplify local testing Key: HBASE-4480 URL: https://issues.apache.org/jira/browse/HBASE-4480 Project: HBase Issue Type: Improvement Reporter: Jesse Yates Priority: Minor Labels: test Attachments: HBASE-4480.patch, HBASE-4480_v2.patch, HBASE-4480_v3.patch, runtest-no-npe-check.sh, runtest.sh, runtest2.sh As mentioned by http://search-hadoop.com/m/r2Ab624ES3e and http://search-hadoop.com/m/cZjDH1ykGIA it would be nice if we could have a script that would handle more of the finer points of running/checking our test suite. This script should: (1) Allow people to determine which tests are hanging/taking a long time to run (2) Allow rerunning of particular tests to make sure it wasn't an artifact of running the whole suite that caused the failure (3) Allow people to specify to run just unit tests or also integration tests (essentially wrapping calls to 'maven test' and 'maven verify'). This script should just be a convenience script - running tests directly from maven should not be impacted. -- 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-3861) MiniZooKeeperCluster.startup() should refer to hbase.zookeeper.property.maxClientCnxns
[
https://issues.apache.org/jira/browse/HBASE-3861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eugene Koontz updated HBASE-3861:
-
Description:
Currently the number of the client connections is hard-wired to 1000:
{noformat}
standaloneServerFactory = new NIOServerCnxnFactory();
standaloneServerFactory.configure(new
InetSocketAddress(clientPort),1000);
} catch (BindException e) {
{noformat}
This should be set according to the test environment's hbase configuration. The
property in
question is : hbase.zookeeper.property.maxClientCnxns.
Currently some tests such as org.apache.hadoop.hbase.client.TestHCM fail
because the number of connections used by the HBase client exceeds 1000.
Recently MAX_CACHED_HBASE_INSTANCES increased from 31 to 2000 on 0.90 branch:
http://svn.apache.org/viewvc/hbase/branches/0.90/src/main/java/org/apache/hadoop/hbase/client/HConnectionManager.java?p2=%2Fhbase%2Fbranches%2F0.90%2Fsrc%2Fmain%2Fjava%2Forg%2Fapache%2Fhadoop%2Fhbase%2Fclient%2FHConnectionManager.javap1=%2Fhbase%2Fbranches%2F0.90%2Fsrc%2Fmain%2Fjava%2Forg%2Fapache%2Fhadoop%2Fhbase%2Fclient%2FHConnectionManager.javar1=1096818r2=1096817view=diffpathrev=1096818
and correspondingly the hbase config on the Zookeeper server-side also
increased in hbase-default.xml:
http://svn.apache.org/viewvc/hbase/branches/0.90/src/main/resources/hbase-default.xml?p2=%2Fhbase%2Fbranches%2F0.90%2Fsrc%2Fmain%2Fresources%2Fhbase-default.xmlp1=%2Fhbase%2Fbranches%2F0.90%2Fsrc%2Fmain%2Fresources%2Fhbase-default.xmlr1=1091594r2=1091593view=diffpathrev=1091594
So if MiniZKCluster looks at this setting, the test won't have this failure.
was:
Currently the number of the client connections is hard-wired to 1000:
{{{
standaloneServerFactory = new NIOServerCnxnFactory();
standaloneServerFactory.configure(new
InetSocketAddress(clientPort),1000);
} catch (BindException e) {
}}}
This should be set according to the test environment's hbase configuration. The
property in
question is : hbase.zookeeper.property.maxClientCnxns.
Currently some tests such as org.apache.hadoop.hbase.client.TestHCM fail
because the number of connections used by the HBase client exceeds 1000.
Recently MAX_CACHED_HBASE_INSTANCES increased from 31 to 2000 on 0.90 branch:
http://svn.apache.org/viewvc/hbase/branches/0.90/src/main/java/org/apache/hadoop/hbase/client/HConnectionManager.java?p2=%2Fhbase%2Fbranches%2F0.90%2Fsrc%2Fmain%2Fjava%2Forg%2Fapache%2Fhadoop%2Fhbase%2Fclient%2FHConnectionManager.javap1=%2Fhbase%2Fbranches%2F0.90%2Fsrc%2Fmain%2Fjava%2Forg%2Fapache%2Fhadoop%2Fhbase%2Fclient%2FHConnectionManager.javar1=1096818r2=1096817view=diffpathrev=1096818
and correspondingly the hbase config on the Zookeeper server-side also
increased in hbase-default.xml:
http://svn.apache.org/viewvc/hbase/branches/0.90/src/main/resources/hbase-default.xml?p2=%2Fhbase%2Fbranches%2F0.90%2Fsrc%2Fmain%2Fresources%2Fhbase-default.xmlp1=%2Fhbase%2Fbranches%2F0.90%2Fsrc%2Fmain%2Fresources%2Fhbase-default.xmlr1=1091594r2=1091593view=diffpathrev=1091594
So if MiniZKCluster looks at this setting, the test won't have this failure.
MiniZooKeeperCluster.startup() should refer to
hbase.zookeeper.property.maxClientCnxns
--
Key: HBASE-3861
URL: https://issues.apache.org/jira/browse/HBASE-3861
Project: HBase
Issue Type: Improvement
Affects Versions: 0.90.3
Reporter: Eugene Koontz
Assignee: Eugene Koontz
Attachments: HBASE-3861.patch, HBASE-3861.patch
Original Estimate: 1h
Remaining Estimate: 1h
Currently the number of the client connections is hard-wired to 1000:
{noformat}
standaloneServerFactory = new NIOServerCnxnFactory();
standaloneServerFactory.configure(new
InetSocketAddress(clientPort),1000);
} catch (BindException e) {
{noformat}
This should be set according to the test environment's hbase configuration.
The property in
question is : hbase.zookeeper.property.maxClientCnxns.
Currently some tests such as org.apache.hadoop.hbase.client.TestHCM fail
because the number of connections used by the HBase client exceeds 1000.
Recently MAX_CACHED_HBASE_INSTANCES increased from 31 to 2000 on 0.90 branch:
http://svn.apache.org/viewvc/hbase/branches/0.90/src/main/java/org/apache/hadoop/hbase/client/HConnectionManager.java?p2=%2Fhbase%2Fbranches%2F0.90%2Fsrc%2Fmain%2Fjava%2Forg%2Fapache%2Fhadoop%2Fhbase%2Fclient%2FHConnectionManager.javap1=%2Fhbase%2Fbranches%2F0.90%2Fsrc%2Fmain%2Fjava%2Forg%2Fapache%2Fhadoop%2Fhbase%2Fclient%2FHConnectionManager.javar1=1096818r2=1096817view=diffpathrev=1096818
and correspondingly the hbase config on the Zookeeper server-side also
increased in hbase-default.xml:
[jira] [Updated] (HBASE-4070) [Coprocessors] Improve region server metrics to report loaded coprocessors to master
[ https://issues.apache.org/jira/browse/HBASE-4070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eugene Koontz updated HBASE-4070: - Attachment: HBASE-4070.patch same as https://reviews.apache.org/r/2029/diff/11/ [Coprocessors] Improve region server metrics to report loaded coprocessors to master Key: HBASE-4070 URL: https://issues.apache.org/jira/browse/HBASE-4070 Project: HBase Issue Type: Improvement Affects Versions: 0.90.3 Reporter: Mingjie Lai Assignee: Eugene Koontz Attachments: HBASE-4070.patch, HBASE-4070.patch, HBASE-4070.patch, HBASE-4070.patch, master-web-ui.jpg, rs-status-web-ui.jpg HBASE-3512 is about listing loaded cp classes at shell. To make it more generic, we need a way to report this piece of information from region to master (or just at region server level). So later on, we can display the loaded class names at shell as well as web console. -- 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-3512) Coprocessors: Shell support for listing currently loaded coprocessor set
[ https://issues.apache.org/jira/browse/HBASE-3512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eugene Koontz updated HBASE-3512: - Attachment: HBASE-3512.patch Based on latest HBASE-4070 patch available at https://reviews.apache.org/r/2029/diff/11/ Coprocessors: Shell support for listing currently loaded coprocessor set Key: HBASE-3512 URL: https://issues.apache.org/jira/browse/HBASE-3512 Project: HBase Issue Type: Improvement Components: coprocessors Reporter: Andrew Purtell Assignee: Eugene Koontz Fix For: 0.92.0 Attachments: HBASE-3512-only.patch, HBASE-3512-only.patch, HBASE-3512.patch, HBASE-3512.patch, HBASE-3512.patch, hbase-shell-session.txt Add support to the shell for listing the coprocessors loaded globally on the regionserver and those loaded on a per-table basis. Perhaps by extending the 'status' command. -- 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-3512) Coprocessors: Shell support for listing currently loaded coprocessor set
[ https://issues.apache.org/jira/browse/HBASE-3512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eugene Koontz updated HBASE-3512: - Attachment: HBASE-3512-only.patch patch against trunk+HBASE-4070 patch. Coprocessors: Shell support for listing currently loaded coprocessor set Key: HBASE-3512 URL: https://issues.apache.org/jira/browse/HBASE-3512 Project: HBase Issue Type: Improvement Components: coprocessors Reporter: Andrew Purtell Assignee: Eugene Koontz Fix For: 0.92.0 Attachments: HBASE-3512-only.patch, HBASE-3512-only.patch, HBASE-3512.patch, HBASE-3512.patch, hbase-shell-session.txt Add support to the shell for listing the coprocessors loaded globally on the regionserver and those loaded on a per-table basis. Perhaps by extending the 'status' command. -- 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-3512) Coprocessors: Shell support for listing currently loaded coprocessor set
[ https://issues.apache.org/jira/browse/HBASE-3512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eugene Koontz updated HBASE-3512: - Attachment: HBASE-3512.patch patch against trunk. Coprocessors: Shell support for listing currently loaded coprocessor set Key: HBASE-3512 URL: https://issues.apache.org/jira/browse/HBASE-3512 Project: HBase Issue Type: Improvement Components: coprocessors Reporter: Andrew Purtell Assignee: Eugene Koontz Fix For: 0.92.0 Attachments: HBASE-3512-only.patch, HBASE-3512-only.patch, HBASE-3512.patch, HBASE-3512.patch, hbase-shell-session.txt Add support to the shell for listing the coprocessors loaded globally on the regionserver and those loaded on a per-table basis. Perhaps by extending the 'status' command. -- 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-4070) [Coprocessors] Improve region server metrics to report loaded coprocessors to master
[ https://issues.apache.org/jira/browse/HBASE-4070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eugene Koontz updated HBASE-4070: - Attachment: HBASE-4070.patch Identical to https://reviews.apache.org/r/2029/diff/5/ [Coprocessors] Improve region server metrics to report loaded coprocessors to master Key: HBASE-4070 URL: https://issues.apache.org/jira/browse/HBASE-4070 Project: HBase Issue Type: Improvement Affects Versions: 0.90.3 Reporter: Mingjie Lai Assignee: Eugene Koontz Attachments: HBASE-4070.patch, HBASE-4070.patch, HBASE-4070.patch, master-web-ui.jpg, rs-status-web-ui.jpg HBASE-3512 is about listing loaded cp classes at shell. To make it more generic, we need a way to report this piece of information from region to master (or just at region server level). So later on, we can display the loaded class names at shell as well as web console. -- 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-4070) [Coprocessors] Improve region server metrics to report loaded coprocessors to master
[ https://issues.apache.org/jira/browse/HBASE-4070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eugene Koontz updated HBASE-4070: - Attachment: rs-status-web-ui.jpg Regionserver Web UI, showing loaded coprocessors. [Coprocessors] Improve region server metrics to report loaded coprocessors to master Key: HBASE-4070 URL: https://issues.apache.org/jira/browse/HBASE-4070 Project: HBase Issue Type: Improvement Affects Versions: 0.90.3 Reporter: Mingjie Lai Assignee: Eugene Koontz Attachments: HBASE-4070.patch, master-web-ui.jpg, rs-status-web-ui.jpg HBASE-3512 is about listing loaded cp classes at shell. To make it more generic, we need a way to report this piece of information from region to master (or just at region server level). So later on, we can display the loaded class names at shell as well as web console. -- 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-4070) [Coprocessors] Improve region server metrics to report loaded coprocessors to master
[ https://issues.apache.org/jira/browse/HBASE-4070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eugene Koontz updated HBASE-4070: - Attachment: master-web-ui.jpg HBase Master Web UI, showing master and regionserver coprocessors. [Coprocessors] Improve region server metrics to report loaded coprocessors to master Key: HBASE-4070 URL: https://issues.apache.org/jira/browse/HBASE-4070 Project: HBase Issue Type: Improvement Affects Versions: 0.90.3 Reporter: Mingjie Lai Assignee: Eugene Koontz Attachments: HBASE-4070.patch, master-web-ui.jpg, rs-status-web-ui.jpg HBASE-3512 is about listing loaded cp classes at shell. To make it more generic, we need a way to report this piece of information from region to master (or just at region server level). So later on, we can display the loaded class names at shell as well as web console. -- 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-4070) [Coprocessors] Improve region server metrics to report loaded coprocessors to master
[ https://issues.apache.org/jira/browse/HBASE-4070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eugene Koontz updated HBASE-4070: - Attachment: (was: HBASE-4070.patch) [Coprocessors] Improve region server metrics to report loaded coprocessors to master Key: HBASE-4070 URL: https://issues.apache.org/jira/browse/HBASE-4070 Project: HBase Issue Type: Improvement Affects Versions: 0.90.3 Reporter: Mingjie Lai Assignee: Eugene Koontz Attachments: HBASE-4070.patch, HBASE-4070.patch, master-web-ui.jpg, rs-status-web-ui.jpg HBASE-3512 is about listing loaded cp classes at shell. To make it more generic, we need a way to report this piece of information from region to master (or just at region server level). So later on, we can display the loaded class names at shell as well as web console. -- 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-4070) [Coprocessors] Improve region server metrics to report loaded coprocessors to master
[ https://issues.apache.org/jira/browse/HBASE-4070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eugene Koontz updated HBASE-4070: - Attachment: HBASE-4070.patch Display both master as well as regionserver coprocessors in master Web UI. [Coprocessors] Improve region server metrics to report loaded coprocessors to master Key: HBASE-4070 URL: https://issues.apache.org/jira/browse/HBASE-4070 Project: HBase Issue Type: Improvement Affects Versions: 0.90.3 Reporter: Mingjie Lai Assignee: Eugene Koontz Attachments: HBASE-4070.patch, HBASE-4070.patch, master-web-ui.jpg, rs-status-web-ui.jpg HBASE-3512 is about listing loaded cp classes at shell. To make it more generic, we need a way to report this piece of information from region to master (or just at region server level). So later on, we can display the loaded class names at shell as well as web console. -- 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-3512) Coprocessors: Shell support for listing currently loaded coprocessor set
[ https://issues.apache.org/jira/browse/HBASE-3512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eugene Koontz updated HBASE-3512: - Status: Patch Available (was: Open) Submitting two patches: HBASE-3125.patch : this is a superset of the patch on HBASE-4070. It is against apache trunk as of now. HBASE-3125-only.patch: this patch is on top of HBASE-4070's patch, showing only the differences between HBASE-4070 and HBASE-3125. Coprocessors: Shell support for listing currently loaded coprocessor set Key: HBASE-3512 URL: https://issues.apache.org/jira/browse/HBASE-3512 Project: HBase Issue Type: Improvement Components: coprocessors Reporter: Andrew Purtell Assignee: Eugene Koontz Fix For: 0.92.0 Attachments: HBASE-3512-only.patch, HBASE-3512.patch Add support to the shell for listing the coprocessors loaded globally on the regionserver and those loaded on a per-table basis. Perhaps by extending the 'status' command. -- 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-3512) Coprocessors: Shell support for listing currently loaded coprocessor set
[ https://issues.apache.org/jira/browse/HBASE-3512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eugene Koontz updated HBASE-3512: - Attachment: hbase-shell-session.txt hbase shell session, showing new coprocessor information. Coprocessors: Shell support for listing currently loaded coprocessor set Key: HBASE-3512 URL: https://issues.apache.org/jira/browse/HBASE-3512 Project: HBase Issue Type: Improvement Components: coprocessors Reporter: Andrew Purtell Assignee: Eugene Koontz Fix For: 0.92.0 Attachments: HBASE-3512-only.patch, HBASE-3512.patch, hbase-shell-session.txt Add support to the shell for listing the coprocessors loaded globally on the regionserver and those loaded on a per-table basis. Perhaps by extending the 'status' command. -- 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-3512) Coprocessors: Shell support for listing currently loaded coprocessor set
[ https://issues.apache.org/jira/browse/HBASE-3512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eugene Koontz updated HBASE-3512: - Attachment: HBASE-3512-only.patch HBASE-3512.patch Submitting two patches: HBASE-3125.patch : this is a superset of the patch on HBASE-4070. It is against apache trunk as of now. HBASE-3125-only.patch: this patch is on top of HBASE-4070's patch, showing only the differences between HBASE-4070 and HBASE-3125. Coprocessors: Shell support for listing currently loaded coprocessor set Key: HBASE-3512 URL: https://issues.apache.org/jira/browse/HBASE-3512 Project: HBase Issue Type: Improvement Components: coprocessors Reporter: Andrew Purtell Assignee: Eugene Koontz Fix For: 0.92.0 Attachments: HBASE-3512-only.patch, HBASE-3512.patch Add support to the shell for listing the coprocessors loaded globally on the regionserver and those loaded on a per-table basis. Perhaps by extending the 'status' command. -- 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-4070) [Coprocessors] Improve region server metrics to report loaded coprocessors to master
[ https://issues.apache.org/jira/browse/HBASE-4070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eugene Koontz updated HBASE-4070: - Attachment: HBASE-4070.patch Display both master as well as regionserver coprocessors in master Web UI. [Coprocessors] Improve region server metrics to report loaded coprocessors to master Key: HBASE-4070 URL: https://issues.apache.org/jira/browse/HBASE-4070 Project: HBase Issue Type: Improvement Affects Versions: 0.90.3 Reporter: Mingjie Lai Assignee: Eugene Koontz Attachments: HBASE-4070.patch, HBASE-4070.patch, master-web-ui.jpg, rs-status-web-ui.jpg HBASE-3512 is about listing loaded cp classes at shell. To make it more generic, we need a way to report this piece of information from region to master (or just at region server level). So later on, we can display the loaded class names at shell as well as web console. -- 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
