[ https://issues.apache.org/jira/browse/HBASE-24713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
ramkrishna.s.vasudevan resolved HBASE-24713. -------------------------------------------- Fix Version/s: 2.2.6 2.3.1 3.0.0-alpha-1 Hadoop Flags: Reviewed Resolution: Fixed Pushed to branch-2.2, branch-2.3 and master. Thanks for all the reviews. > RS startup with FSHLog throws NPE after HBASE-21751 > --------------------------------------------------- > > Key: HBASE-24713 > URL: https://issues.apache.org/jira/browse/HBASE-24713 > Project: HBase > Issue Type: Bug > Components: wal > Affects Versions: 2.1.6 > Reporter: ramkrishna.s.vasudevan > Assignee: Gaurav Kanade > Priority: Minor > Fix For: 3.0.0-alpha-1, 2.3.1, 2.2.6 > > > Every RS startup creates this NPE > {code} > [sync.1] wal.FSHLog: UNEXPECTED > java.lang.NullPointerException > at > org.apache.hadoop.hbase.regionserver.wal.FSHLog$SyncRunner.run(FSHLog.java:582) > at java.lang.Thread.run(Thread.java:748) > 2020-07-07 10:51:23,208 WARN [regionserver/xxxxx:16020] wal.FSHLog: Failed > sync-before-close but no outstanding appends; closing > WALjava.lang.NullPointerException > {code} > the reason is that the Disruptor frameworks starts the Syncrunner thread but > the init of the writer happens after that. A simple null check in the > Syncrunner will help here . > No major damage happens though since we handle Throwable Exception. It will > good to solve this. -- This message was sent by Atlassian Jira (v8.3.4#803005)