You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@accumulo.apache.org by "Christopher Tubbs (JIRA)" <ji...@apache.org> on 2019/04/16 19:28:00 UTC

[jira] [Resolved] (ACCUMULO-4783) WAL writes should handle IOExceptions vs other exceptions differently

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

Christopher Tubbs resolved ACCUMULO-4783.
-----------------------------------------
       Resolution: Invalid
    Fix Version/s:     (was: 2.0.0)

Lots of new WAL improvements have been made in the 1.9.x releases. This is likely OBE. However, please open a new issue at https://github.com/apache/accumulo/issues  if it continues to be a problem.

> WAL writes should handle IOExceptions vs other exceptions differently
> ---------------------------------------------------------------------
>
>                 Key: ACCUMULO-4783
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-4783
>             Project: Accumulo
>          Issue Type: Bug
>          Components: tserver
>    Affects Versions: 1.7.3, 1.8.1, 2.0.0
>            Reporter: Ivan Bella
>            Priority: Major
>
> The writing of WALs in the TabletServerLogger currently does not distinguish between IOExceptions and other exceptions when backing off and retrying.  I believe IOExceptions can be handled by backing off and retrying.  However other exceptions perhaps should be handled by perhaps halting the tserver as they may denote a coding error instead of some file system error.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)