[jira] [Updated] (IGNITE-21098) Increase additional wait after DDL by MaxClockSkew
[ https://issues.apache.org/jira/browse/IGNITE-21098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman Puchkovskiy updated IGNITE-21098: --- Description: When executing an RO transaction, readTimestamp has to be determined. If MaxObservableTimestamp is not available (which is currently true after a DDL), then TxManagerImpl takes readTimestamp as HLC.now() - idleSafeTimePropagationPeriod - MaxClockSkew. In IGNITE-20668, an additional wait after a DDL operation was added to make sure that a readTimestamp calculated in this way does not look before the DDL (otherwise, the RO would see the previous schema). But in IGNITE-20668, only idleSafeTimePropagationPeriod was added after a DDL, and MaxClockSkew component was forgotten. We must add MaxClockSkew to the wait. was:When executing an RO transaction, readTimestamp has to be determined. If MaxObservableTimestamp is not available (which is currently true after a DDL), then TxManagerImpl takes readTimestamp as HLC.now() - idleSafeTimePropagationPeriod - MaxClockSkew. > Increase additional wait after DDL by MaxClockSkew > -- > > Key: IGNITE-21098 > URL: https://issues.apache.org/jira/browse/IGNITE-21098 > Project: Ignite > Issue Type: Improvement >Reporter: Roman Puchkovskiy >Assignee: Roman Puchkovskiy >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > Time Spent: 10m > Remaining Estimate: 0h > > When executing an RO transaction, readTimestamp has to be determined. If > MaxObservableTimestamp is not available (which is currently true after a > DDL), then TxManagerImpl takes readTimestamp as HLC.now() - > idleSafeTimePropagationPeriod - MaxClockSkew. > In IGNITE-20668, an additional wait after a DDL operation was added to make > sure that a readTimestamp calculated in this way does not look before the DDL > (otherwise, the RO would see the previous schema). But in IGNITE-20668, only > idleSafeTimePropagationPeriod was added after a DDL, and MaxClockSkew > component was forgotten. > We must add MaxClockSkew to the wait. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21098) Increase additional wait after DDL by MaxClockSkew
[ https://issues.apache.org/jira/browse/IGNITE-21098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman Puchkovskiy updated IGNITE-21098: --- Description: When executing an RO transaction, readTimestamp has to be determined. If MaxObservableTimestamp is not available (which is currently true after a DDL), then TxManagerImpl takes readTimestamp as HLC.now() - idleSafeTimePropagationPeriod - MaxClockSkew. (was: When executing an RO transaction, readTimestamp has to be determined. If MaxObservableTimestamp is not available...) > Increase additional wait after DDL by MaxClockSkew > -- > > Key: IGNITE-21098 > URL: https://issues.apache.org/jira/browse/IGNITE-21098 > Project: Ignite > Issue Type: Improvement >Reporter: Roman Puchkovskiy >Assignee: Roman Puchkovskiy >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > Time Spent: 10m > Remaining Estimate: 0h > > When executing an RO transaction, readTimestamp has to be determined. If > MaxObservableTimestamp is not available (which is currently true after a > DDL), then TxManagerImpl takes readTimestamp as HLC.now() - > idleSafeTimePropagationPeriod - MaxClockSkew. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21098) Increase additional wait after DDL by MaxClockSkew
[ https://issues.apache.org/jira/browse/IGNITE-21098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman Puchkovskiy updated IGNITE-21098: --- Description: When executing an RO transaction, readTimestamp has to be determined. If MaxObservableTimestamp is not available... > Increase additional wait after DDL by MaxClockSkew > -- > > Key: IGNITE-21098 > URL: https://issues.apache.org/jira/browse/IGNITE-21098 > Project: Ignite > Issue Type: Improvement >Reporter: Roman Puchkovskiy >Assignee: Roman Puchkovskiy >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > > When executing an RO transaction, readTimestamp has to be determined. If > MaxObservableTimestamp is not available... -- This message was sent by Atlassian Jira (v8.20.10#820010)
