[
https://issues.apache.org/jira/browse/KUDU-1042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15897831#comment-15897831
]
Todd Lipcon commented on KUDU-1042:
-----------------------------------
[~mpercy] [~dralves] is this one still relevant? if we don't have a pressing
need for the change I think we should probably mark it as wontfix (or maybe we
already fixed it?)
> Consider serializing timestamp assignment for non-tablet operations
> -------------------------------------------------------------------
>
> Key: KUDU-1042
> URL: https://issues.apache.org/jira/browse/KUDU-1042
> Project: Kudu
> Issue Type: Improvement
> Components: consensus
> Affects Versions: Feature Complete
> Reporter: Mike Percy
>
> We currently may have non-monotonic timestamp assignment to opids because
> write transaction prepare may run concurrently with change config operations.
> This is the cause of the bootstrap crasher seen in KUDU-1035.
> We don't think it's currently critical (as of public beta) to enforce this
> monotonicity, but we should revisit this when we put more thought into the
> ramifications as it relates to safe time.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
