hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sean Busbey <bus...@apache.org>
Subject Re: mini cluster not starting due to unhandled com.lmax.disruptor.dsl.Disruptor.<init> (eclipse only, not in mvn)
Date Mon, 28 Nov 2016 23:17:22 GMT
Can y'all make sure there's a note in our ref guide calling out this
occasional need to refresh the eclipse project files (like e.g. that
it's needed when a dependency version changes)?

A quick look makes me think it should probably be in the section
"144.1.6. Eclipse Known Issues".

On Sun, Nov 27, 2016 at 9:58 PM, Stephen Jiang <syuanjiangdev@gmail.com> wrote:
> Thanks, forget the 'mvn eclipse:eclipse' trick.  After doing this, things
> working again.
>
> Thanks
> Stephen
>
> On Sun, Nov 27, 2016 at 6:51 PM, 张铎 <palomino219@gmail.com> wrote:
>
>> Try mvn eclispe:eclipse again? We upgraded disruptor to 3.3.6 recently.
>>
>> 2016-11-28 10:48 GMT+08:00 Stephen Jiang <syuanjiangdev@gmail.com>:
>>
>> > I had problem to start mini cluster in eclipse in the last few days.  In
>> > master branch (without any additional change), I got the following FATAL
>> > error (running the UT using maven has NO problem):
>> >
>> > 2016-11-27 18:44:58,102 FATAL [M:0;10.10.0.153:59578]
>> > master.HMaster(2241):
>> > Master server abort: loaded coprocessors are: []
>> > 2016-11-27 18:44:58,102 FATAL [M:0;10.10.0.153:59578]
>> > master.HMaster(2244):
>> > Unhandled:
>> > com.lmax.disruptor.dsl.Disruptor.<init>(Lcom/lmax/
>> > disruptor/EventFactory;ILjava/util/concurrent/ThreadFactory;
>> > Lcom/lmax/disruptor/dsl/ProducerType;Lcom/lmax/disruptor/WaitStrategy;)V
>> > java.lang.NoSuchMethodError:
>> > com.lmax.disruptor.dsl.Disruptor.<init>(Lcom/lmax/
>> > disruptor/EventFactory;ILjava/util/concurrent/ThreadFactory;
>> > Lcom/lmax/disruptor/dsl/ProducerType;Lcom/lmax/disruptor/WaitStrategy;)V
>> > at org.apache.hadoop.hbase.regionserver.wal.FSHLog.<init>
>> (FSHLog.java:230)
>> > at
>> > org.apache.hadoop.hbase.wal.FSHLogProvider.createWAL(
>> > FSHLogProvider.java:80)
>> > at
>> > org.apache.hadoop.hbase.wal.FSHLogProvider.createWAL(
>> > FSHLogProvider.java:39)
>> > at
>> > org.apache.hadoop.hbase.wal.AbstractFSWALProvider.getWAL(
>> > AbstractFSWALProvider.java:132)
>> > at
>> > org.apache.hadoop.hbase.wal.AbstractFSWALProvider.getWAL(
>> > AbstractFSWALProvider.java:52)
>> > at org.apache.hadoop.hbase.wal.WALFactory.getWAL(WALFactory.java:242)
>> > at
>> > org.apache.hadoop.hbase.regionserver.HRegionServer.
>> > getWAL(HRegionServer.java:1929)
>> > at
>> > org.apache.hadoop.hbase.regionserver.HRegionServer.
>> > buildServerLoad(HRegionServer.java:1247)
>> > at
>> > org.apache.hadoop.hbase.regionserver.HRegionServer.
>> tryRegionServerReport(
>> > HRegionServer.java:1205)
>> > at
>> > org.apache.hadoop.hbase.regionserver.HRegionServer.
>> > run(HRegionServer.java:1022)
>> > at java.lang.Thread.run(Thread.java:745)
>> >
>>

Mime
View raw message