[
https://issues.apache.org/jira/browse/IGNITE-4638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-4638:
------------------------------------
Description:
1) Basically there are three operation types which must be shared with joining
node:
- {{COMPLETED}} - shared as snapshot of current schema state;
- {{ACKED}} - shared as operation requests;
- {{INITED}} - shared as operation requests.
2) Completed and acked operations are applied right away.
3) Inited operations are not applied immediately. Instead, joined node sends
{{VERIFY_INIT_OPS}} request to coordinator. Operations are applied only after
coordinator confirmed that they were not rejected on {{INIT}} stage.
It seems that to achieve p.3 nodes will have to keep a kind of history of
rejected operations which is not very desirable, but do we really have other
options?
was:
1) Basically there are three operation types which must be shared with joining
node:
- {{COMPLETED}} - shared as snapshot of current schema state;
- {{ACKED}} - shared as operation requests;
- {{INITED}} - shared as operation requests.
2) Completed and acked operations are applied right away.
3) Inited operations are not applied immediately. Instead, joined node sends
{{VERIFY_INIT_OPS}} request to coordinator. Operations are applied only after
coordinator confirmed that they were not rejected on {{INIT}} stage.
It seems that to achieve p.3 nodes will have to keep a kind of history of
rejected operations which is not desirable.
> Share current DDL schema and pending DDL operations with joining nodes
> ----------------------------------------------------------------------
>
> Key: IGNITE-4638
> URL: https://issues.apache.org/jira/browse/IGNITE-4638
> Project: Ignite
> Issue Type: Sub-task
> Components: SQL
> Reporter: Vladimir Ozerov
> Fix For: 2.0
>
>
> 1) Basically there are three operation types which must be shared with
> joining node:
> - {{COMPLETED}} - shared as snapshot of current schema state;
> - {{ACKED}} - shared as operation requests;
> - {{INITED}} - shared as operation requests.
> 2) Completed and acked operations are applied right away.
> 3) Inited operations are not applied immediately. Instead, joined node sends
> {{VERIFY_INIT_OPS}} request to coordinator. Operations are applied only after
> coordinator confirmed that they were not rejected on {{INIT}} stage.
> It seems that to achieve p.3 nodes will have to keep a kind of history of
> rejected operations which is not very desirable, but do we really have other
> options?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
