[
https://issues.apache.org/jira/browse/HBASE-23340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
jackylau updated HBASE-23340:
-----------------------------
Description:
hmaster /hbase/replication/rs session expired (hbase replication default value
is true, we don't use ) causes logcleaner can not clean oldWALs, which resulits
in oldWALs too large (more than 2TB).
!Snipaste_2019-11-21_10-39-25.png!
!Snipaste_2019-11-21_14-10-36.png!
we can solve it by following :
1) increase the session timeout(but i think it is not a good idea. because we
do not know how long to set is suitable)
2) close the hbase replication. It is not a good idea too, when our user uses
this feature
3) we need add retry times, for example when it has already happened three
times, we set the ReplicationLogCleaner and SnapShotCleaner stop
that is all my ideas, i do not konw it is suitable, If it is suitable, could i
commit a PR?
Does anynode have a good idea.
was:
hmaster /hbase/replication/rs session expired (hbase replication default value
is true, we don't use ) causes logcleaner can not clean oldWALs, which resulits
in oldWALs too large (more than 2TB).
!Snipaste_2019-11-21_10-39-25.png!
!Snipaste_2019-11-21_14-10-36.png!
> hmaster /hbase/replication/rs session expired (hbase replication default
> value is true, we don't use ) causes logcleaner can not clean oldWALs, which
> resulits in oldWALs too large (more than 2TB)
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: HBASE-23340
> URL: https://issues.apache.org/jira/browse/HBASE-23340
> Project: HBase
> Issue Type: Improvement
> Components: master
> Reporter: jackylau
> Assignee: jackylau
> Priority: Major
> Fix For: master
>
> Attachments: Snipaste_2019-11-21_10-39-25.png,
> Snipaste_2019-11-21_14-10-36.png
>
>
> hmaster /hbase/replication/rs session expired (hbase replication default
> value is true, we don't use ) causes logcleaner can not clean oldWALs, which
> resulits in oldWALs too large (more than 2TB).
> !Snipaste_2019-11-21_10-39-25.png!
>
> !Snipaste_2019-11-21_14-10-36.png!
>
> we can solve it by following :
> 1) increase the session timeout(but i think it is not a good idea. because we
> do not know how long to set is suitable)
> 2) close the hbase replication. It is not a good idea too, when our user uses
> this feature
> 3) we need add retry times, for example when it has already happened three
> times, we set the ReplicationLogCleaner and SnapShotCleaner stop
> that is all my ideas, i do not konw it is suitable, If it is suitable, could
> i commit a PR?
> Does anynode have a good idea.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
