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

Posted to issues@hbase.apache.org by "chenxu (JIRA)" <ji...@apache.org> on 2018/07/17 06:59:00 UTC

[jira] [Updated] (HBASE-20902) when WAL sync failed, we should bypass the failed DN that previously used

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

chenxu updated HBASE-20902:
---------------------------
    Description: 
in our prod env, there happened to be a slow DN, all WAL#sync with that DN are failed, 

during Log rolling, we should bypass the slow DN that the previously Log used.

  was:
in our prod env, there happened to be a slow DN, all WAL#sync with that DN are failed, 

during Log rolling, we should bypass the slow DN that previously Log used.


> when WAL sync failed, we should bypass the failed DN that previously used
> -------------------------------------------------------------------------
>
>                 Key: HBASE-20902
>                 URL: https://issues.apache.org/jira/browse/HBASE-20902
>             Project: HBase
>          Issue Type: Bug
>          Components: wal
>            Reporter: chenxu
>            Priority: Major
>
> in our prod env, there happened to be a slow DN, all WAL#sync with that DN are failed, 
> during Log rolling, we should bypass the slow DN that the previously Log used.



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