[
https://issues.apache.org/jira/browse/KUDU-1078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16769585#comment-16769585
]
Adar Dembo commented on KUDU-1078:
----------------------------------
Hi [~Simon_Zhang],
In and of itself, this log message is not a sign that anything has gone wrong.
In fact, for Kudu 1.9.0, we've downgraded the message's severity from ERROR to
INFO. You can see the commit responsible for that and the justification for it
[here|https://github.com/apache/kudu/commit/6103f8786358df1766ba41c8d8dc2feb9c8c6f53].
> Under heavy load, log cache reads return "Op in future"
> -------------------------------------------------------
>
> Key: KUDU-1078
> URL: https://issues.apache.org/jira/browse/KUDU-1078
> Project: Kudu
> Issue Type: Improvement
> Components: consensus
> Affects Versions: Private Beta
> Reporter: Todd Lipcon
> Assignee: Todd Lipcon
> Priority: Major
> Fix For: 1.6.0
>
>
> JD accidentally configured botl80 so that all nodes were writing to a single
> tablet (talk about a stress test!) I see the following warning occasionally
> in the leader logs:
> W0827 11:34:04.051275 55950 consensus_queue.cc:272] T
> d6ff74fb04454712873abd0d2328e59b P 668314723deb4a818cc9a43eba51073c [LEADER]:
> The logs necessary to catch up peer 600e62435ca24425b29c00d9726b78be have
> been garbage collected. The follower will never be able to catch up (Not
> found: op in future). Instructing remote peer to remotely bootstrap.
> Calling this a blocker because, if we couple this with the "automatically
> re-bootstrap nodes if they fall behind", we'll be accidentally deleting
> tablets when this happens (no good!)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
