[jira] [Created] (HBASE-5202) NPE in master.AssignmentManager.regionOnline()

2012-01-15 Thread Eugene Koontz (Created) (JIRA)
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


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] [Created] (HBASE-5044) Clarify solution for problem described on http://hbase.apache.org/book/trouble.mapreduce.html

2011-12-15 Thread Eugene Koontz (Created) (JIRA)
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


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] [Created] (HBASE-4975) fix spurious -1's from Hadoop QA

2011-12-07 Thread Eugene Koontz (Created) (JIRA)
fix spurious -1's from Hadoop QA


 Key: HBASE-4975
 URL: https://issues.apache.org/jira/browse/HBASE-4975
 Project: HBase
  Issue Type: Bug
  Components: build
Reporter: Eugene Koontz
Priority: Minor


Hadoop QA generated comments based on patches submitted to JIRAs; for example:

https://issues.apache.org/jira/browse/HBASE-4960?focusedCommentId=13163191page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13163191

There are some spurious -1's given to the patch. The patch only affects 
documentation, not source code, but Hadoop QA says that:
{noformat}
-1 findbugs. The patch appears to introduce 72 new Findbugs (version 1.3.9)
warnings.
{noformat}

Evidently Hadoop QA is not able to recall the set of Findbugs warnings from the 
previous build.

(Of course the Findbugs warnings themselves should be addressed, but this patch 
could not have added to them).

{noformat}
-1 javadoc. The javadoc tool appears to have generated -160 warning
messages.
{noformat}

This should be 160 warning messages, not -160 warning messages.

Thanks to NKeywal for suggesting that the relevant file is 
{{dev-support/test-patch.sh}}.


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] [Created] (HBASE-4960) Document mutual authentication between HBase and Zookeeper using SASL

2011-12-05 Thread Eugene Koontz (Created) (JIRA)
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
Reporter: Eugene Koontz
Assignee: Eugene Koontz


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] [Created] (HBASE-4791) Allow Secure Zookeeper JAAS configuration to be programmatically set (rather than only by reading JAAS configuration file)

2011-11-15 Thread Eugene Koontz (Created) (JIRA)
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: Bug
Reporter: Eugene Koontz


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] [Created] (HBASE-4693) Consolidate TestRegionServerCoprocessorExceptionWithRemove and TestRegionServerCoprocessorExceptionWithRemove into a single cluster spin-up

2011-10-28 Thread Eugene Koontz (Created) (JIRA)
Consolidate TestRegionServerCoprocessorExceptionWithRemove and 
TestRegionServerCoprocessorExceptionWithRemove 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