[
https://issues.apache.org/jira/browse/KUDU-803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grant Henke resolved KUDU-803.
------------------------------
Fix Version/s: 1.9.0
Target Version/s: (was: 1.8.0)
Assignee: Alexey Serbin
Resolution: Fixed
Resolved via
https://github.com/apache/kudu/commit/b37f264fbb4f798ee9743ed87e145cd92a7fc63d
> "Could not prepare op" log message is confusing
> -----------------------------------------------
>
> Key: KUDU-803
> URL: https://issues.apache.org/jira/browse/KUDU-803
> Project: Kudu
> Issue Type: Bug
> Components: consensus
> Affects Versions: Private Beta
> Reporter: Todd Lipcon
> Assignee: Alexey Serbin
> Priority: Major
> Fix For: 1.9.0
>
>
> If any op fails to prepare, we then log all a WARNING message for every other
> op in the request, using the failed status of the first message. This is very
> confusing, since it seems to ascribe errors to the later ops when they were
> just skipped because the first couldn't be prepared.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
