Home | About | Sematext search-lucene.com search-hadoop.com
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB
 Search Hadoop and all its subprojects:

Switch to Threaded View
HBase >> mail # dev >> workaround to remove a warning stack in the test logs


Copy link to this message
-
Re: workaround to remove a warning stack in the test logs
I think we can do the following until someone finds out the root cause.

Thanks Nicolas.

On Nov 23, 2012, at 10:43 AM, Nicolas Liochon <[EMAIL PROTECTED]> wrote:

> Hi,
>
> We have this well known stack everytime we launch a minicluster:
>
> 12/04/05 16:56:07 WARN util.MBeans:
> Hadoop:service=DataNode,name=MetricsSystem,sub=Control
> javax.management.InstanceAlreadyExistsException: MXBean already
> registered with name
> Hadoop:service=NameNode,name=MetricsSystem,sub=Control
>    at com.sun.jmx.mbeanserver.MXBeanLookup.addReference(MXBeanLookup.java:120)
>    at com.sun.jmx.mbeanserver.MXBeanSupport.register(MXBeanSupport.java:143)
>    at com.sun.jmx.mbeanserver.MBeanSupport.preRegister2(MBeanSupport.java:183)
>
>
> That's HBASE-4709.
>
> It could be removed by adding this in HBaseTestingUtility:
>
>  static {
> org.apache.log4j.Logger.getLogger(org.apache.hadoop.metrics2.util.MBeans.class).
>        setLevel(org.apache.log4j.Level.ERROR);
>  }
>
> This would hide all the warnings from this class, which is acceptable imho.
>
> Is it an issue for anyone if I do it (in trunk) ?
>
> The other solution is to understand the problem and fix it, but it could
> take me hours, I don't really have them for this :-)
>
>
> Cheers,
>
> Nicolas
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB