[jira] [Commented] (ZOOKEEPER-2824) `FileChannel#size` info should be added to `FileTxnLog#commit` to solve the confuse that reason is too large log or too busy disk I/O

[ASF GitHub Bot (JIRA)]

    [ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16301030#comment-16301030
 ] 

ASF GitHub Bot commented on ZOOKEEPER-2824:
-------------------------------------------

Github user asdf2014 commented on the issue:

    https://github.com/apache/zookeeper/pull/296
  
    @afine Could you approve this PR?
    @phunt @anmolnar PTAL.
    
    
    Just recently, i experienced this situation again, this time due to the bad 
disk rather than the huge WAL file. But i still cannot get the root cause from 
Zookeeper log...
    
![image](https://user-images.githubusercontent.com/8108788/34287956-6a946230-e725-11e7-865f-2b4c140868e6.png)
    
    
    



> `FileChannel#size` info should be added to `FileTxnLog#commit` to solve the 
> confuse that reason is too large log or too busy disk I/O
> -------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: ZOOKEEPER-2824
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2824
>             Project: ZooKeeper
>          Issue Type: Improvement
>          Components: server
>    Affects Versions: 3.5.3
>            Reporter: Benedict Jin
>            Assignee: Benedict Jin
>            Priority: Minor
>              Labels: logging
>             Fix For: 3.5.4, 3.6.0
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> `FileChannel#size` info should be added to `FileTxnLog#commit` to solve the 
> confuse that reason is too large log or too busy disk I/O



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)