[ 
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 ops - 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.

  was:
Design considerations:
1) Should be implemented through custom discovery data mechanism. 
2) Probably it makes sense to add version to every DDL change. E.g. (topVer + 
local coordinator ctr). It will help us to avoid duplicated operations in case 
of some unforseen races.


> 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 ops - 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.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to