[CdcService] check lagged follower every time reach max lsn
This commit is contained in:
committed by
ob-robot
parent
36905ed6bc
commit
a623dd4b20
@ -755,7 +755,6 @@ void ObCdcFetcher::handle_when_reach_max_lsn_in_palf_(const ObLSID &ls_id,
|
|||||||
ObCdcLSFetchLogResp &resp)
|
ObCdcLSFetchLogResp &resp)
|
||||||
{
|
{
|
||||||
int ret = OB_SUCCESS;
|
int ret = OB_SUCCESS;
|
||||||
bool is_ls_fall_behind = frt.is_ls_fall_behind();
|
|
||||||
|
|
||||||
// Because we cannot determine whether this LS is a backward standby or a normal LS,
|
// Because we cannot determine whether this LS is a backward standby or a normal LS,
|
||||||
// we can only check the LS.
|
// we can only check the LS.
|
||||||
@ -764,10 +763,8 @@ void ObCdcFetcher::handle_when_reach_max_lsn_in_palf_(const ObLSID &ls_id,
|
|||||||
// 1. Reach max lsn but the progress is behind the upper limit
|
// 1. Reach max lsn but the progress is behind the upper limit
|
||||||
// 2. No logs fetched in this round of RPC
|
// 2. No logs fetched in this round of RPC
|
||||||
// 2. The overall progress is behind
|
// 2. The overall progress is behind
|
||||||
if (fetched_log_count <= 0 && is_ls_fall_behind) {
|
if (OB_FAIL(check_lag_follower_(ls_id, palf_handle_guard, resp))) {
|
||||||
if (OB_FAIL(check_lag_follower_(ls_id, palf_handle_guard, resp))) {
|
LOG_WARN("check_lag_follower_ fail", KR(ret), K(ls_id), K(frt));
|
||||||
LOG_WARN("check_lag_follower_ fail", KR(ret), K(ls_id), K(frt));
|
|
||||||
}
|
|
||||||
}
|
}
|
||||||
}
|
}
|
||||||
|
|
||||||
|
|||||||
@ -348,7 +348,7 @@ public:
|
|||||||
T_DEF_INT_INFT(blacklist_survival_time_sec, OB_CLUSTER_PARAMETER, 30, 1, "blacklist-server surival time in seconds");
|
T_DEF_INT_INFT(blacklist_survival_time_sec, OB_CLUSTER_PARAMETER, 30, 1, "blacklist-server surival time in seconds");
|
||||||
|
|
||||||
// The maximum time the server can be blacklisted, in minutes
|
// The maximum time the server can be blacklisted, in minutes
|
||||||
T_DEF_INT_INFT(blacklist_survival_time_upper_limit_min, OB_CLUSTER_PARAMETER, 4, 1, "blacklist-server survival time upper limit in minute");
|
T_DEF_INT_INFT(blacklist_survival_time_upper_limit_min, OB_CLUSTER_PARAMETER, 1, 1, "blacklist-server survival time upper limit in minute");
|
||||||
|
|
||||||
// The server is blacklisted in the logstream, based on the time of the current server service logstream - to decide whether to penalize the survival time
|
// The server is blacklisted in the logstream, based on the time of the current server service logstream - to decide whether to penalize the survival time
|
||||||
// When the service time is less than a certain interval, a doubling-live-time policy is adopted
|
// When the service time is less than a certain interval, a doubling-live-time policy is adopted
|
||||||
|
|||||||
@ -181,7 +181,7 @@ public:
|
|||||||
T_DEF_INT_INFT(blacklist_survival_time_sec, OB_CLUSTER_PARAMETER, 30, 1, "blacklist-server surival time in seconds");
|
T_DEF_INT_INFT(blacklist_survival_time_sec, OB_CLUSTER_PARAMETER, 30, 1, "blacklist-server surival time in seconds");
|
||||||
|
|
||||||
// The maximum time the server can be blacklisted, in minutes
|
// The maximum time the server can be blacklisted, in minutes
|
||||||
T_DEF_INT_INFT(blacklist_survival_time_upper_limit_min, OB_CLUSTER_PARAMETER, 4, 1, "blacklist-server survival time upper limit in minute");
|
T_DEF_INT_INFT(blacklist_survival_time_upper_limit_min, OB_CLUSTER_PARAMETER, 1, 1, "blacklist-server survival time upper limit in minute");
|
||||||
|
|
||||||
// The server is blacklisted in the logstream, based on the time of the current server service logstream - to decide whether to penalize the survival time
|
// The server is blacklisted in the logstream, based on the time of the current server service logstream - to decide whether to penalize the survival time
|
||||||
// When the service time is less than a certain interval, a doubling-live-time policy is adopted
|
// When the service time is less than a certain interval, a doubling-live-time policy is adopted
|
||||||
|
|||||||
Reference in New Issue
Block a user