Major Description
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.
