You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Nick Dimiduk (Jira)" <ji...@apache.org> on 2020/04/01 18:41:00 UTC
[jira] [Commented] (HBASE-24086) Disable output stream capability
enforcement when running in standalone mode
[ https://issues.apache.org/jira/browse/HBASE-24086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17073077#comment-17073077 ]
Nick Dimiduk commented on HBASE-24086:
--------------------------------------
bq. Just curious, did you set the following config in hdfs-site and it still doesn't work?
[~bharathv] no, I was not aware that we expect standalone mode to be broken out of the box.
This was not the case before bumping the minimum hadoop version to 2.10, because before that, stream capability was not exposed in the HDFS api, and thus we'd proceed without. The patch I've posted removes the requirement of manual configuration.
> Disable output stream capability enforcement when running in standalone mode
> ----------------------------------------------------------------------------
>
> Key: HBASE-24086
> URL: https://issues.apache.org/jira/browse/HBASE-24086
> Project: HBase
> Issue Type: Bug
> Components: master
> Affects Versions: 3.0.0, 2.3.0
> Reporter: Nick Dimiduk
> Priority: Major
>
> {noformat}
> $ JAVA_HOME=/Library/Java/JavaVirtualMachines/adoptopenjdk-8.jdk/Contents/Home mvn clean install -DskipTests
> $ JAVA_HOME=/Library/Java/JavaVirtualMachines/adoptopenjdk-8.jdk/Contents/Home ./bin/hbase master start
> {noformat}
> gives
> {noformat}
> 2020-03-30 17:12:43,857 ERROR [master/192.168.111.13:16000:becomeActiveMaster] master.HMaster: Failed to become active master
> java.io.IOException: cannot get log writer
> at org.apache.hadoop.hbase.wal.AsyncFSWALProvider.createAsyncWriter(AsyncFSWALProvider.java:118)
> at org.apache.hadoop.hbase.regionserver.wal.AsyncFSWAL.createAsyncWriter(AsyncFSWAL.java:704)
> at org.apache.hadoop.hbase.regionserver.wal.AsyncFSWAL.createWriterInstance(AsyncFSWAL.java:710)
> at org.apache.hadoop.hbase.regionserver.wal.AsyncFSWAL.createWriterInstance(AsyncFSWAL.java:128)
> at org.apache.hadoop.hbase.regionserver.wal.AbstractFSWAL.rollWriter(AbstractFSWAL.java:839)
> at org.apache.hadoop.hbase.regionserver.wal.AbstractFSWAL.rollWriter(AbstractFSWAL.java:549)
> at org.apache.hadoop.hbase.regionserver.wal.AbstractFSWAL.init(AbstractFSWAL.java:490)
> at org.apache.hadoop.hbase.wal.AbstractFSWALProvider.getWAL(AbstractFSWALProvider.java:156)
> at org.apache.hadoop.hbase.wal.AbstractFSWALProvider.getWAL(AbstractFSWALProvider.java:61)
> at org.apache.hadoop.hbase.wal.WALFactory.getWAL(WALFactory.java:297)
> at org.apache.hadoop.hbase.procedure2.store.region.RegionProcedureStore.createWAL(RegionProcedureStore.java:256)
> at org.apache.hadoop.hbase.procedure2.store.region.RegionProcedureStore.bootstrap(RegionProcedureStore.java:273)
> at org.apache.hadoop.hbase.procedure2.store.region.RegionProcedureStore.recoverLease(RegionProcedureStore.java:482)
> at org.apache.hadoop.hbase.procedure2.ProcedureExecutor.init(ProcedureExecutor.java:587)
> at org.apache.hadoop.hbase.master.HMaster.createProcedureExecutor(HMaster.java:1575)
> at org.apache.hadoop.hbase.master.HMaster.finishActiveMasterInitialization(HMaster.java:961)
> at org.apache.hadoop.hbase.master.HMaster.startActiveMasterManager(HMaster.java:2231)
> at org.apache.hadoop.hbase.master.HMaster.lambda$run$0(HMaster.java:621)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: org.apache.hadoop.hbase.util.CommonFSUtils$StreamLacksCapabilityException: hflush
> at org.apache.hadoop.hbase.io.asyncfs.AsyncFSOutputHelper.createOutput(AsyncFSOutputHelper.java:71)
> at org.apache.hadoop.hbase.regionserver.wal.AsyncProtobufLogWriter.initOutput(AsyncProtobufLogWriter.java:169)
> at org.apache.hadoop.hbase.regionserver.wal.AbstractProtobufLogWriter.init(AbstractProtobufLogWriter.java:166)
> at org.apache.hadoop.hbase.wal.AsyncFSWALProvider.createAsyncWriter(AsyncFSWALProvider.java:105)
> ... 18 more
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)