You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Guanghao Zhang (Jira)" <ji...@apache.org> on 2020/03/10 05:54:00 UTC
[jira] [Resolved] (HBASE-23684) NPE HFilesOutputSink
[ https://issues.apache.org/jira/browse/HBASE-23684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Guanghao Zhang resolved HBASE-23684.
------------------------------------
Resolution: Duplicate
Resolved as duplicate.
> NPE HFilesOutputSink
> --------------------
>
> Key: HBASE-23684
> URL: https://issues.apache.org/jira/browse/HBASE-23684
> Project: HBase
> Issue Type: Bug
> Components: MTTR, wal
> Affects Versions: 2.3.0
> Reporter: Michael Stack
> Assignee: Guanghao Zhang
> Priority: Critical
> Fix For: 3.0.0, 2.3.0
>
>
> Enabling the new split to hfiles feature, HBASE-23286, running branch-2 tip, I see this out on RegionServers:
> {code}
> 2020-01-13 17:37:08,204 INFO org.apache.hadoop.hbase.wal.OutputSink: 3 split writer threads finished
> 2020-01-13 17:37:08,233 INFO org.apache.hadoop.hbase.wal.WALSplitter: Processed 1007 edits across 0 regions cost 284 ms; edits skipped=76; WAL=hdfs://nameservice1/hbase/genie/WALs/hbasedn101.example.org,16020,1578934806382-splitting/hbasedn101.example.org%2C16020%2C1578934806382.1578937008832, size=128.5 M, length=134708720, corrupted=false, progress failed=true
> 2020-01-13 17:37:08,234 WARN org.apache.hadoop.hbase.regionserver.SplitLogWorker: log splitting of WALs/hbasedn101.example.org,16020,1578934806382-splitting/hbasedn101.example.org%2C16020%2C1578934806382.1578937008832 failed, returning error
> java.io.IOException: java.lang.NullPointerException
> at org.apache.hadoop.hbase.wal.BoundedRecoveredHFilesOutputSink.writeRemainingEntryBuffers(BoundedRecoveredHFilesOutputSink.java:173)
> at org.apache.hadoop.hbase.wal.BoundedRecoveredHFilesOutputSink.close(BoundedRecoveredHFilesOutputSink.java:140)
> at org.apache.hadoop.hbase.wal.WALSplitter.splitLogFile(WALSplitter.java:339)
> at org.apache.hadoop.hbase.wal.WALSplitter.splitLogFile(WALSplitter.java:181)
> at org.apache.hadoop.hbase.regionserver.SplitLogWorker.splitLog(SplitLogWorker.java:105)
> at org.apache.hadoop.hbase.regionserver.SplitLogWorker.lambda$new$0(SplitLogWorker.java:84)
> at org.apache.hadoop.hbase.regionserver.handler.WALSplitterHandler.process(WALSplitterHandler.java:70)
> at org.apache.hadoop.hbase.executor.EventHandler.run(EventHandler.java:104)
> at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> at java.base/java.lang.Thread.run(Thread.java:834)
> Caused by: java.lang.NullPointerException
> at org.apache.hadoop.hbase.wal.BoundedRecoveredHFilesOutputSink.configContextForNonMetaWriter(BoundedRecoveredHFilesOutputSink.java:225)
> at org.apache.hadoop.hbase.wal.BoundedRecoveredHFilesOutputSink.createRecoveredHFileWriter(BoundedRecoveredHFilesOutputSink.java:213)
> at org.apache.hadoop.hbase.wal.BoundedRecoveredHFilesOutputSink.append(BoundedRecoveredHFilesOutputSink.java:117)
> at org.apache.hadoop.hbase.wal.BoundedRecoveredHFilesOutputSink.lambda$writeRemainingEntryBuffers$3(BoundedRecoveredHFilesOutputSink.java:155)
> at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
> at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
> at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
> {code}
> It is a bit odd because log says there were zero regions. Not sure what that was about.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)