Styxis
Company
Knowledge

Include newly cloned Doris replicas in a binlog TTL transition

After extending binlog retention, check whether replicas cloned during the transition received the new TTL. Record the policy generation alongside current serving membership to find replicas outside the original completion responses.

Membership changes during transition

A retention-policy transition must cover replicas created after its RPC target list was captured. Truthound Core can compare effective per-replica TTL with the approved policy once the operator supplies membership and configuration generations. [1, 2, 3]

A clone snapshot condition

Doris issue #69079 describes a shared-nothing clone potentially installing an old-TTL snapshot during an extension. Source-review follow-up supports the membership gap but does not establish runtime loss or every release. A CLONE replica must become eligible before a reader consequence can be claimed. [1]

Recheck replica identities

Record config version, replica identities, clone source snapshot, effective TTL, and query eligibility. Recheck membership after the original acknowledgments. An unchanged partition-ID set does not prove that every newly added replica received the target policy. [1, 3]

The 60-to-3600-second policy

The reported policy extends 60 seconds to 3600 seconds. A newly cloned replica at 3600 seconds passes the target-TTL comparison. One still at 60 seconds fails even if all original replicas acknowledged the extension. These are per-replica policy values, not measured lost-event counts. [1, 3]

Compare effective policies only

ColumnPairValidator in Truthound Core Python SDK 3.3.2 can compare non-null effective and target TTL columns in seconds. The operator supplies authoritative policy and current identities. The SDK does not lock cloning, propagate configuration, or recover already expired binlog. [1, 2, 3]

Keep unverified replicas distinct

Review an operational path that revalidates membership and keeps unverified replicas outside the approved retention scope. A configuration generation alone is insufficient when the transition temporarily publishes a new generation with the old TTL. [1, 3]

Advertise the readable window

Only announce the enlarged readable window after the actual serving replica set satisfies it. Matching TTL does not restore events removed before the transition, so preserve event-age and recovery boundaries separately. [1, 3]

Application conditions

Collect effective TTL by configuration generation and current replica identity.

Alternatives

Recheck membership and separate unverified replicas from the approved set.

Limitations

  • Matching TTL neither restores expired binlog nor establishes loss across all replicas.

Evidence

Event checked
Subject checked
Modified