[
https://issues.apache.org/jira/browse/KUDU-803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grant Henke updated KUDU-803:
-----------------------------
Target Version/s: 1.8.0 (was: 1.5.0)
> "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
> Priority: Major
>
> 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
(v7.6.3#76005)
