Hi Imran, Glad that fixed your XML parsing problem. I haven't used HBaseTestingUtility (we start up a test cluster by extending HBaseClusterTestCase), but I did notice something that looked strange in your logs. You can see that the namenode binds to 127.0.0.1:37523, and ZK also uses 127.0.0.1, but then you see this:
10/10/06 20:53:14 INFO net.NetworkTopology: Adding a new node: /default-rack/223.27.113.138:48680 10/10/06 20:53:14 INFO datanode.DataNode: New storage id DS-517982013-127.0.1.1-48680-1286430794780 is assigned to data-node 223.27.113.138:48680 It looks like the datanode is binding to 223.27.113.138 instead of 127.0.0.1. Then further down: 10/10/06 20:53:15 INFO hdfs.StateChange: BLOCK* NameSystem.allocateBlock: /user/hudson/hbase.version. blk_6520143473758843527_1001 10/10/06 20:53:15 INFO hdfs.DFSClient: Exception in createBlockOutputStream java.net.ConnectException: Connection refused 10/10/06 20:53:15 INFO hdfs.DFSClient: Abandoning block blk_6520143473758843527_1001 10/10/06 20:53:15 INFO hdfs.DFSClient: Excluding datanode 223.27.113.138:48680 10/10/06 20:53:15 WARN namenode.FSNamesystem: Not able to place enough replicas, still in need of 1 When my unit test cluster starts up everything binds to 127.0.0.1. I'm not sure if that's your problem, but it definitely looks like the DFS client can't talk to the datanode for some reason. Maybe someone who is more familiar with HBaseTestingUtility will know what could cause this. Do you have hbase-default.xml and/or hbase-site.xml on your test classpath? If so, what do they contain? -James On Thu, Oct 7, 2010 at 1:59 AM, Imran M Yousuf <[email protected]> wrote: > Just an update - > > The XML parsing problem is solved but the mini-cluster is still not up - > > > http://hudson.smartitengineering.com/hudson/job/imyousuf-smart-cms/com.smartitengineering.smart-cms$smart-cms-client-impl/44/console > > Regards, > > Imran > > On Thu, Oct 7, 2010 at 11:54 AM, Imran M Yousuf <[email protected]> > wrote: > > Thanks James, > > > > Specifying > -DargLine="-Djavax.xml.parsers.DocumentBuilderFactory=com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderFactoryImpl." > > solves the parse related exceptions but it does not solve the cluster > > not getting up. In my local box, the cluster works fine despite the > > exceptions in parsing. > > > > Regards, > > > > Imran > > > > On Thu, Oct 7, 2010 at 11:32 AM, James Baldassari <[email protected]> > wrote: > >> I think I've seen that before too. Try setting > >> > -Djavax.xml.parsers.DocumentBuilderFactory=com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderFactoryImpl. > >> If you're using Maven: > >> > >> <plugin> > >> <groupId>org.apache.maven.plugins</groupId> > >> <artifactId>maven-surefire-plugin</artifactId> > >> <configuration> > >> <systemProperties> > >> <property> > >> <name>javax.xml.parsers.DocumentBuilderFactory</name> > >> > >> > <value>com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderFactoryImpl</value> > >> </property> > >> </configuration> > >> </plugin> > >> > >> > >> On Thu, Oct 7, 2010 at 1:28 AM, Gary Helmling <[email protected]> > wrote: > >> > >>> On Wed, Oct 6, 2010 at 10:14 PM, Stack <[email protected]> wrote: > >>> > >>> > I wonder what JVM that build box is using? Complaint is: > >>> > > >>> > Failed to set setXIncludeAware(true) for parser > >>> > > >>> > Its like the XML parser being used by the JVM to readin the hdfs > >>> > configuration files has no support for setXIncludeAware where > normally > >>> > -- the sun java6 we all know and love -- that feature is present. > >>> > > >>> > > >>> Hi Imran, > >>> > >>> As St.Ack describes, it's a problem with the XML parser being loaded. > I > >>> believe I've run into this problem in the past when an old version of > >>> xerces > >>> was being included in the classpath. If the JDK checks out, look for > >>> xerces > >>> or another XML parser lib in your classpath and try excluding it. > >>> > >>> > >>> Gary > >>> > >> > > > > > > > > -- > > Imran M Yousuf > > Entrepreneur & CEO > > Smart IT Engineering Ltd. > > Dhaka, Bangladesh > > Twitter: @imyousuf - http://twitter.com/imyousuf > > Blog: http://imyousuf-tech.blogs.smartitengineering.com/ > > Mobile: +880-1711402557 > > > > > > -- > Imran M Yousuf > Entrepreneur & CEO > Smart IT Engineering Ltd. > Dhaka, Bangladesh > Twitter: @imyousuf - http://twitter.com/imyousuf > Blog: http://imyousuf-tech.blogs.smartitengineering.com/ > Mobile: +880-1711402557 >
