-
Type:
Bug
-
Status: Resolved
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: 2.1.6
-
Fix Version/s: 3.0.0-alpha-1, 2.3.1, 2.4.0, 2.2.6
-
Component/s: wal
-
Labels:None
-
Hadoop Flags:Reviewed
Every RS startup creates this NPE
[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
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.