[jira] [Created] (HBASE-15367) Configuring DisabledWAL provider hangs the RegionServer

["ramkrishna.s.vasudevan (JIRA)" <ji...@apache.org>]

ramkrishna.s.vasudevan created HBASE-15367:
----------------------------------------------

             Summary: Configuring DisabledWAL provider hangs the RegionServer
                 Key: HBASE-15367
                 URL: https://issues.apache.org/jira/browse/HBASE-15367
             Project: HBase
          Issue Type: Bug
            Reporter: ramkrishna.s.vasudevan
            Assignee: ramkrishna.s.vasudevan
            Priority: Minor


DisabledWALProvider is not for production cases. But still configuring one does not allow region opening to work fine and thus hanging create table process.
[code}
  at org.apache.hadoop.hbase.wal.WALKey.getWriteEntry(WALKey.java:106)
        at org.apache.hadoop.hbase.regionserver.wal.WALUtil.writeMarker(WALUtil.java:133)
        at org.apache.hadoop.hbase.regionserver.wal.WALUtil.writeRegionEventMarker(WALUtil.java:88)
        at org.apache.hadoop.hbase.regionserver.HRegion.writeRegionOpenMarker(HRegion.java:1006)
        at org.apache.hadoop.hbase.regionserver.HRegion.openHRegion(HRegion.java:6483)
        at org.apache.hadoop.hbase.regionserver.HRegion.openHRegion(HRegion.java:6433)
        at org.apache.hadoop.hbase.regionserver.HRegion.openHRegion(HRegion.java:6404)
        at org.apache.hadoop.hbase.regionserver.HRegion.openHRegion(HRegion.java:6360)
        at org.apache.hadoop.hbase.regionserver.HRegion.openHRegion(HRegion.java:6311)
        at org.apache.hadoop.hbase.regionserver.handler.OpenRegionHandler.openRegion(OpenRegionHandler.java:282)
        at org.apache.hadoop.hbase.regionserver.handler.OpenRegionHandler.process(OpenRegionHandler.java:107)
        at org.apache.hadoop.hbase.executor.EventHandler.run(EventHandler.java:104)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
{code}
But there is also a clear comment in WALUtil#writeMarker
{code}
 // If you get hung here, is it a real WAL or a mocked WAL? If the latter, you need to
      // trip the latch that is inside in getWriteEntry up in your mock. See down in the append
      // called from onEvent in FSHLog.
{code}
But this is about Mocking but here it is not mocking and still we are not able to use it. The only option is like the client should say SKIP_WAL for every mutation if we really need to avoid WAL.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)