[ 
https://issues.apache.org/jira/browse/HBASE-28546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Wei-Chiu Chuang resolved HBASE-28546.
-------------------------------------
    Resolution: Fixed

> Make WAL rolling exception clear
> --------------------------------
>
>                 Key: HBASE-28546
>                 URL: https://issues.apache.org/jira/browse/HBASE-28546
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Wei-Chiu Chuang
>            Assignee: Wei-Chiu Chuang
>            Priority: Minor
>              Labels: pull-request-available
>             Fix For: 4.0.0-alpha-1, 3.0.0-beta-2, 2.6.1, 2.5.9
>
>
> Occasionally we see errors like this that doesn't really give much clue what 
> went wrong.
> {noformat}
> 2024-04-22 08:08:02,026 ERROR org.apache.hadoop.hbase.master.HMaster: ***** 
> ABORTING master ccycloud-7.ozn-hb973chf3oz.xyz,22001,1713770648404: Log 
> rolling failed *****
> java.lang.RuntimeException
>         at 
> org.apache.hadoop.hbase.regionserver.wal.AsyncProtobufLogWriter.writeWALMetadata(AsyncProtobufLogWriter.java:217)
>         at 
> org.apache.hadoop.hbase.regionserver.wal.AsyncProtobufLogWriter.writeMagicAndWALHeader(AsyncProtobufLogWriter.java:223)
>         at 
> org.apache.hadoop.hbase.regionserver.wal.AbstractProtobufLogWriter.init(AbstractProtobufLogWriter.java:164)
>         at 
> org.apache.hadoop.hbase.wal.AsyncFSWALProvider.createAsyncWriter(AsyncFSWALProvider.java:116)
>         at 
> org.apache.hadoop.hbase.regionserver.wal.AsyncFSWAL.createWriterInstance(AsyncFSWAL.java:726)
>         at 
> org.apache.hadoop.hbase.regionserver.wal.AsyncFSWAL.createWriterInstance(AsyncFSWAL.java:129)
>         at 
> org.apache.hadoop.hbase.regionserver.wal.AbstractFSWAL.rollWriter(AbstractFSWAL.java:886)
>         at 
> org.apache.hadoop.hbase.wal.AbstractWALRoller$RollController.rollWal(AbstractWALRoller.java:304)
>         at 
> org.apache.hadoop.hbase.wal.AbstractWALRoller.run(AbstractWALRoller.java:211)
> {noformat}
> In this case, it was due to a time out exception. It would be helpful to make 
> the log message more friendly.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to