[jira] [Updated] (RATIS-352) Persist commit index in Raft log.

2018-10-21 Thread Tsz Wo Nicholas Sze (JIRA)


 [ 
https://issues.apache.org/jira/browse/RATIS-352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tsz Wo Nicholas Sze updated RATIS-352:
--
Attachment: r352_20181022.patch

> Persist commit index in Raft log.
> -
>
> Key: RATIS-352
> URL: https://issues.apache.org/jira/browse/RATIS-352
> Project: Ratis
>  Issue Type: Improvement
>  Components: server
>Reporter: Tsz Wo Nicholas Sze
>Assignee: Tsz Wo Nicholas Sze
>Priority: Major
> Attachments: r352_20181022.patch
>
>
> Current the commit index is not persisted in the Raft log.  When a server 
> restarts, it cannot apply its log until it has joined a Raft group.  There is 
> no problem if there is a Raft group.  
> However, a server cannot recover its data when formatting a Raft group is 
> impossible (e.g. a majority of servers are dead).  Ideally, a server can 
> safely apply the log up to the commit index.  The JIRA is to persist the 
> commit index so that such recovery is possible.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (RATIS-352) Persist commit index in Raft log.

2018-10-21 Thread Tsz Wo Nicholas Sze (JIRA)


 [ 
https://issues.apache.org/jira/browse/RATIS-352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tsz Wo Nicholas Sze updated RATIS-352:
--
Attachment: r352_20181022.patch

> Persist commit index in Raft log.
> -
>
> Key: RATIS-352
> URL: https://issues.apache.org/jira/browse/RATIS-352
> Project: Ratis
>  Issue Type: Improvement
>  Components: server
>Reporter: Tsz Wo Nicholas Sze
>Assignee: Tsz Wo Nicholas Sze
>Priority: Major
> Attachments: r352_20181022b.patch
>
>
> Current the commit index is not persisted in the Raft log.  When a server 
> restarts, it cannot apply its log until it has joined a Raft group.  There is 
> no problem if there is a Raft group.  
> However, a server cannot recover its data when formatting a Raft group is 
> impossible (e.g. a majority of servers are dead).  Ideally, a server can 
> safely apply the log up to the commit index.  The JIRA is to persist the 
> commit index so that such recovery is possible.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (RATIS-352) Persist commit index in Raft log.

2018-10-21 Thread Tsz Wo Nicholas Sze (JIRA)


 [ 
https://issues.apache.org/jira/browse/RATIS-352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tsz Wo Nicholas Sze updated RATIS-352:
--
Attachment: (was: r352_20181022.patch)

> Persist commit index in Raft log.
> -
>
> Key: RATIS-352
> URL: https://issues.apache.org/jira/browse/RATIS-352
> Project: Ratis
>  Issue Type: Improvement
>  Components: server
>Reporter: Tsz Wo Nicholas Sze
>Assignee: Tsz Wo Nicholas Sze
>Priority: Major
> Attachments: r352_20181022b.patch
>
>
> Current the commit index is not persisted in the Raft log.  When a server 
> restarts, it cannot apply its log until it has joined a Raft group.  There is 
> no problem if there is a Raft group.  
> However, a server cannot recover its data when formatting a Raft group is 
> impossible (e.g. a majority of servers are dead).  Ideally, a server can 
> safely apply the log up to the commit index.  The JIRA is to persist the 
> commit index so that such recovery is possible.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (RATIS-352) Persist commit index in Raft log.

2018-10-21 Thread Tsz Wo Nicholas Sze (JIRA)


 [ 
https://issues.apache.org/jira/browse/RATIS-352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tsz Wo Nicholas Sze updated RATIS-352:
--
Attachment: r352_20181022b.patch

> Persist commit index in Raft log.
> -
>
> Key: RATIS-352
> URL: https://issues.apache.org/jira/browse/RATIS-352
> Project: Ratis
>  Issue Type: Improvement
>  Components: server
>Reporter: Tsz Wo Nicholas Sze
>Assignee: Tsz Wo Nicholas Sze
>Priority: Major
> Attachments: r352_20181022b.patch
>
>
> Current the commit index is not persisted in the Raft log.  When a server 
> restarts, it cannot apply its log until it has joined a Raft group.  There is 
> no problem if there is a Raft group.  
> However, a server cannot recover its data when formatting a Raft group is 
> impossible (e.g. a majority of servers are dead).  Ideally, a server can 
> safely apply the log up to the commit index.  The JIRA is to persist the 
> commit index so that such recovery is possible.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (RATIS-352) Persist commit index in Raft log.

2018-10-21 Thread Tsz Wo Nicholas Sze (JIRA)


 [ 
https://issues.apache.org/jira/browse/RATIS-352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tsz Wo Nicholas Sze updated RATIS-352:
--
Attachment: (was: r352_20181022.patch)

> Persist commit index in Raft log.
> -
>
> Key: RATIS-352
> URL: https://issues.apache.org/jira/browse/RATIS-352
> Project: Ratis
>  Issue Type: Improvement
>  Components: server
>Reporter: Tsz Wo Nicholas Sze
>Assignee: Tsz Wo Nicholas Sze
>Priority: Major
> Attachments: r352_20181022b.patch
>
>
> Current the commit index is not persisted in the Raft log.  When a server 
> restarts, it cannot apply its log until it has joined a Raft group.  There is 
> no problem if there is a Raft group.  
> However, a server cannot recover its data when formatting a Raft group is 
> impossible (e.g. a majority of servers are dead).  Ideally, a server can 
> safely apply the log up to the commit index.  The JIRA is to persist the 
> commit index so that such recovery is possible.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (RATIS-352) Persist commit index in Raft log.

2018-10-22 Thread Tsz Wo Nicholas Sze (JIRA)


 [ 
https://issues.apache.org/jira/browse/RATIS-352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tsz Wo Nicholas Sze updated RATIS-352:
--
Attachment: r352_20181022c.patch

> Persist commit index in Raft log.
> -
>
> Key: RATIS-352
> URL: https://issues.apache.org/jira/browse/RATIS-352
> Project: Ratis
>  Issue Type: Improvement
>  Components: server
>Reporter: Tsz Wo Nicholas Sze
>Assignee: Tsz Wo Nicholas Sze
>Priority: Major
> Attachments: r352_20181022c.patch
>
>
> Current the commit index is not persisted in the Raft log.  When a server 
> restarts, it cannot apply its log until it has joined a Raft group.  There is 
> no problem if there is a Raft group.  
> However, a server cannot recover its data when formatting a Raft group is 
> impossible (e.g. a majority of servers are dead).  Ideally, a server can 
> safely apply the log up to the commit index.  The JIRA is to persist the 
> commit index so that such recovery is possible.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (RATIS-352) Persist commit index in Raft log.

2018-10-22 Thread Tsz Wo Nicholas Sze (JIRA)


 [ 
https://issues.apache.org/jira/browse/RATIS-352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tsz Wo Nicholas Sze updated RATIS-352:
--
Attachment: (was: r352_20181022b.patch)

> Persist commit index in Raft log.
> -
>
> Key: RATIS-352
> URL: https://issues.apache.org/jira/browse/RATIS-352
> Project: Ratis
>  Issue Type: Improvement
>  Components: server
>Reporter: Tsz Wo Nicholas Sze
>Assignee: Tsz Wo Nicholas Sze
>Priority: Major
> Attachments: r352_20181022c.patch
>
>
> Current the commit index is not persisted in the Raft log.  When a server 
> restarts, it cannot apply its log until it has joined a Raft group.  There is 
> no problem if there is a Raft group.  
> However, a server cannot recover its data when formatting a Raft group is 
> impossible (e.g. a majority of servers are dead).  Ideally, a server can 
> safely apply the log up to the commit index.  The JIRA is to persist the 
> commit index so that such recovery is possible.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (RATIS-352) Persist commit index in Raft log.

2018-10-22 Thread Tsz Wo Nicholas Sze (JIRA)


 [ 
https://issues.apache.org/jira/browse/RATIS-352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tsz Wo Nicholas Sze updated RATIS-352:
--
Attachment: r352_20181022d.patch

> Persist commit index in Raft log.
> -
>
> Key: RATIS-352
> URL: https://issues.apache.org/jira/browse/RATIS-352
> Project: Ratis
>  Issue Type: Improvement
>  Components: server
>Reporter: Tsz Wo Nicholas Sze
>Assignee: Tsz Wo Nicholas Sze
>Priority: Major
> Attachments: r352_20181022d.patch
>
>
> Current the commit index is not persisted in the Raft log.  When a server 
> restarts, it cannot apply its log until it has joined a Raft group.  There is 
> no problem if there is a Raft group.  
> However, a server cannot recover its data when formatting a Raft group is 
> impossible (e.g. a majority of servers are dead).  Ideally, a server can 
> safely apply the log up to the commit index.  The JIRA is to persist the 
> commit index so that such recovery is possible.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (RATIS-352) Persist commit index in Raft log.

2018-10-22 Thread Tsz Wo Nicholas Sze (JIRA)


 [ 
https://issues.apache.org/jira/browse/RATIS-352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tsz Wo Nicholas Sze updated RATIS-352:
--
Attachment: (was: r352_20181022c.patch)

> Persist commit index in Raft log.
> -
>
> Key: RATIS-352
> URL: https://issues.apache.org/jira/browse/RATIS-352
> Project: Ratis
>  Issue Type: Improvement
>  Components: server
>Reporter: Tsz Wo Nicholas Sze
>Assignee: Tsz Wo Nicholas Sze
>Priority: Major
> Attachments: r352_20181022d.patch
>
>
> Current the commit index is not persisted in the Raft log.  When a server 
> restarts, it cannot apply its log until it has joined a Raft group.  There is 
> no problem if there is a Raft group.  
> However, a server cannot recover its data when formatting a Raft group is 
> impossible (e.g. a majority of servers are dead).  Ideally, a server can 
> safely apply the log up to the commit index.  The JIRA is to persist the 
> commit index so that such recovery is possible.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (RATIS-352) Persist commit index in Raft log.

2018-10-22 Thread Tsz Wo Nicholas Sze (JIRA)


 [ 
https://issues.apache.org/jira/browse/RATIS-352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tsz Wo Nicholas Sze updated RATIS-352:
--
Attachment: r352_20181022d.patch

> Persist commit index in Raft log.
> -
>
> Key: RATIS-352
> URL: https://issues.apache.org/jira/browse/RATIS-352
> Project: Ratis
>  Issue Type: Improvement
>  Components: server
>Reporter: Tsz Wo Nicholas Sze
>Assignee: Tsz Wo Nicholas Sze
>Priority: Major
> Attachments: r352_20181022d.patch
>
>
> Current the commit index is not persisted in the Raft log.  When a server 
> restarts, it cannot apply its log until it has joined a Raft group.  There is 
> no problem if there is a Raft group.  
> However, a server cannot recover its data when formatting a Raft group is 
> impossible (e.g. a majority of servers are dead).  Ideally, a server can 
> safely apply the log up to the commit index.  The JIRA is to persist the 
> commit index so that such recovery is possible.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (RATIS-352) Persist commit index in Raft log.

2018-10-22 Thread Tsz Wo Nicholas Sze (JIRA)


 [ 
https://issues.apache.org/jira/browse/RATIS-352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tsz Wo Nicholas Sze updated RATIS-352:
--
Attachment: (was: r352_20181022d.patch)

> Persist commit index in Raft log.
> -
>
> Key: RATIS-352
> URL: https://issues.apache.org/jira/browse/RATIS-352
> Project: Ratis
>  Issue Type: Improvement
>  Components: server
>Reporter: Tsz Wo Nicholas Sze
>Assignee: Tsz Wo Nicholas Sze
>Priority: Major
> Attachments: r352_20181022d.patch
>
>
> Current the commit index is not persisted in the Raft log.  When a server 
> restarts, it cannot apply its log until it has joined a Raft group.  There is 
> no problem if there is a Raft group.  
> However, a server cannot recover its data when formatting a Raft group is 
> impossible (e.g. a majority of servers are dead).  Ideally, a server can 
> safely apply the log up to the commit index.  The JIRA is to persist the 
> commit index so that such recovery is possible.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (RATIS-352) Persist commit index in Raft log.

2018-10-23 Thread Tsz Wo Nicholas Sze (JIRA)


 [ 
https://issues.apache.org/jira/browse/RATIS-352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tsz Wo Nicholas Sze updated RATIS-352:
--
Attachment: (was: r352_20181022d.patch)

> Persist commit index in Raft log.
> -
>
> Key: RATIS-352
> URL: https://issues.apache.org/jira/browse/RATIS-352
> Project: Ratis
>  Issue Type: Improvement
>  Components: server
>Reporter: Tsz Wo Nicholas Sze
>Assignee: Tsz Wo Nicholas Sze
>Priority: Major
> Attachments: r352_20181023.patch
>
>
> Current the commit index is not persisted in the Raft log.  When a server 
> restarts, it cannot apply its log until it has joined a Raft group.  There is 
> no problem if there is a Raft group.  
> However, a server cannot recover its data when formatting a Raft group is 
> impossible (e.g. a majority of servers are dead).  Ideally, a server can 
> safely apply the log up to the commit index.  The JIRA is to persist the 
> commit index so that such recovery is possible.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (RATIS-352) Persist commit index in Raft log.

2018-10-23 Thread Tsz Wo Nicholas Sze (JIRA)


 [ 
https://issues.apache.org/jira/browse/RATIS-352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tsz Wo Nicholas Sze updated RATIS-352:
--
Attachment: r352_20181023.patch

> Persist commit index in Raft log.
> -
>
> Key: RATIS-352
> URL: https://issues.apache.org/jira/browse/RATIS-352
> Project: Ratis
>  Issue Type: Improvement
>  Components: server
>Reporter: Tsz Wo Nicholas Sze
>Assignee: Tsz Wo Nicholas Sze
>Priority: Major
> Attachments: r352_20181023.patch
>
>
> Current the commit index is not persisted in the Raft log.  When a server 
> restarts, it cannot apply its log until it has joined a Raft group.  There is 
> no problem if there is a Raft group.  
> However, a server cannot recover its data when formatting a Raft group is 
> impossible (e.g. a majority of servers are dead).  Ideally, a server can 
> safely apply the log up to the commit index.  The JIRA is to persist the 
> commit index so that such recovery is possible.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (RATIS-352) Persist commit index in Raft log.

2018-10-23 Thread Tsz Wo Nicholas Sze (JIRA)


 [ 
https://issues.apache.org/jira/browse/RATIS-352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tsz Wo Nicholas Sze updated RATIS-352:
--
Attachment: (was: r352_20181023.patch)

> Persist commit index in Raft log.
> -
>
> Key: RATIS-352
> URL: https://issues.apache.org/jira/browse/RATIS-352
> Project: Ratis
>  Issue Type: Improvement
>  Components: server
>Reporter: Tsz Wo Nicholas Sze
>Assignee: Tsz Wo Nicholas Sze
>Priority: Major
> Attachments: r352_20181023b.patch
>
>
> Current the commit index is not persisted in the Raft log.  When a server 
> restarts, it cannot apply its log until it has joined a Raft group.  There is 
> no problem if there is a Raft group.  
> However, a server cannot recover its data when formatting a Raft group is 
> impossible (e.g. a majority of servers are dead).  Ideally, a server can 
> safely apply the log up to the commit index.  The JIRA is to persist the 
> commit index so that such recovery is possible.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (RATIS-352) Persist commit index in Raft log.

2018-10-23 Thread Tsz Wo Nicholas Sze (JIRA)


 [ 
https://issues.apache.org/jira/browse/RATIS-352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tsz Wo Nicholas Sze updated RATIS-352:
--
Attachment: r352_20181023b.patch

> Persist commit index in Raft log.
> -
>
> Key: RATIS-352
> URL: https://issues.apache.org/jira/browse/RATIS-352
> Project: Ratis
>  Issue Type: Improvement
>  Components: server
>Reporter: Tsz Wo Nicholas Sze
>Assignee: Tsz Wo Nicholas Sze
>Priority: Major
> Attachments: r352_20181023b.patch
>
>
> Current the commit index is not persisted in the Raft log.  When a server 
> restarts, it cannot apply its log until it has joined a Raft group.  There is 
> no problem if there is a Raft group.  
> However, a server cannot recover its data when formatting a Raft group is 
> impossible (e.g. a majority of servers are dead).  Ideally, a server can 
> safely apply the log up to the commit index.  The JIRA is to persist the 
> commit index so that such recovery is possible.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (RATIS-352) Persist commit index in Raft log.

2018-10-24 Thread Tsz Wo Nicholas Sze (JIRA)


 [ 
https://issues.apache.org/jira/browse/RATIS-352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tsz Wo Nicholas Sze updated RATIS-352:
--
Attachment: (was: r352_20181023b.patch)

> Persist commit index in Raft log.
> -
>
> Key: RATIS-352
> URL: https://issues.apache.org/jira/browse/RATIS-352
> Project: Ratis
>  Issue Type: Improvement
>  Components: server
>Reporter: Tsz Wo Nicholas Sze
>Assignee: Tsz Wo Nicholas Sze
>Priority: Major
> Attachments: r352_20181024.patch
>
>
> Current the commit index is not persisted in the Raft log.  When a server 
> restarts, it cannot apply its log until it has joined a Raft group.  There is 
> no problem if there is a Raft group.  
> However, a server cannot recover its data when formatting a Raft group is 
> impossible (e.g. a majority of servers are dead).  Ideally, a server can 
> safely apply the log up to the commit index.  The JIRA is to persist the 
> commit index so that such recovery is possible.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (RATIS-352) Persist commit index in Raft log.

2018-10-24 Thread Tsz Wo Nicholas Sze (JIRA)


 [ 
https://issues.apache.org/jira/browse/RATIS-352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tsz Wo Nicholas Sze updated RATIS-352:
--
Attachment: r352_20181024.patch

> Persist commit index in Raft log.
> -
>
> Key: RATIS-352
> URL: https://issues.apache.org/jira/browse/RATIS-352
> Project: Ratis
>  Issue Type: Improvement
>  Components: server
>Reporter: Tsz Wo Nicholas Sze
>Assignee: Tsz Wo Nicholas Sze
>Priority: Major
> Attachments: r352_20181024.patch
>
>
> Current the commit index is not persisted in the Raft log.  When a server 
> restarts, it cannot apply its log until it has joined a Raft group.  There is 
> no problem if there is a Raft group.  
> However, a server cannot recover its data when formatting a Raft group is 
> impossible (e.g. a majority of servers are dead).  Ideally, a server can 
> safely apply the log up to the commit index.  The JIRA is to persist the 
> commit index so that such recovery is possible.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (RATIS-352) Persist commit index in Raft log.

2018-10-24 Thread Tsz Wo Nicholas Sze (JIRA)


 [ 
https://issues.apache.org/jira/browse/RATIS-352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tsz Wo Nicholas Sze updated RATIS-352:
--
Attachment: r352_20181025.patch

> Persist commit index in Raft log.
> -
>
> Key: RATIS-352
> URL: https://issues.apache.org/jira/browse/RATIS-352
> Project: Ratis
>  Issue Type: Improvement
>  Components: server
>Reporter: Tsz Wo Nicholas Sze
>Assignee: Tsz Wo Nicholas Sze
>Priority: Major
> Attachments: r352_20181025.patch
>
>
> Current the commit index is not persisted in the Raft log.  When a server 
> restarts, it cannot apply its log until it has joined a Raft group.  There is 
> no problem if there is a Raft group.  
> However, a server cannot recover its data when formatting a Raft group is 
> impossible (e.g. a majority of servers are dead).  Ideally, a server can 
> safely apply the log up to the commit index.  The JIRA is to persist the 
> commit index so that such recovery is possible.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (RATIS-352) Persist commit index in Raft log.

2018-10-24 Thread Tsz Wo Nicholas Sze (JIRA)


 [ 
https://issues.apache.org/jira/browse/RATIS-352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tsz Wo Nicholas Sze updated RATIS-352:
--
Attachment: (was: r352_20181024.patch)

> Persist commit index in Raft log.
> -
>
> Key: RATIS-352
> URL: https://issues.apache.org/jira/browse/RATIS-352
> Project: Ratis
>  Issue Type: Improvement
>  Components: server
>Reporter: Tsz Wo Nicholas Sze
>Assignee: Tsz Wo Nicholas Sze
>Priority: Major
> Attachments: r352_20181025.patch
>
>
> Current the commit index is not persisted in the Raft log.  When a server 
> restarts, it cannot apply its log until it has joined a Raft group.  There is 
> no problem if there is a Raft group.  
> However, a server cannot recover its data when formatting a Raft group is 
> impossible (e.g. a majority of servers are dead).  Ideally, a server can 
> safely apply the log up to the commit index.  The JIRA is to persist the 
> commit index so that such recovery is possible.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (RATIS-352) Persist commit index in Raft log.

2018-10-24 Thread Tsz Wo Nicholas Sze (JIRA)


 [ 
https://issues.apache.org/jira/browse/RATIS-352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tsz Wo Nicholas Sze updated RATIS-352:
--
Attachment: (was: r352_20181025.patch)

> Persist commit index in Raft log.
> -
>
> Key: RATIS-352
> URL: https://issues.apache.org/jira/browse/RATIS-352
> Project: Ratis
>  Issue Type: Improvement
>  Components: server
>Reporter: Tsz Wo Nicholas Sze
>Assignee: Tsz Wo Nicholas Sze
>Priority: Major
> Attachments: r352_20181025b.patch
>
>
> Current the commit index is not persisted in the Raft log.  When a server 
> restarts, it cannot apply its log until it has joined a Raft group.  There is 
> no problem if there is a Raft group.  
> However, a server cannot recover its data when formatting a Raft group is 
> impossible (e.g. a majority of servers are dead).  Ideally, a server can 
> safely apply the log up to the commit index.  The JIRA is to persist the 
> commit index so that such recovery is possible.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (RATIS-352) Persist commit index in Raft log.

2018-10-24 Thread Tsz Wo Nicholas Sze (JIRA)


 [ 
https://issues.apache.org/jira/browse/RATIS-352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tsz Wo Nicholas Sze updated RATIS-352:
--
Attachment: r352_20181025b.patch

> Persist commit index in Raft log.
> -
>
> Key: RATIS-352
> URL: https://issues.apache.org/jira/browse/RATIS-352
> Project: Ratis
>  Issue Type: Improvement
>  Components: server
>Reporter: Tsz Wo Nicholas Sze
>Assignee: Tsz Wo Nicholas Sze
>Priority: Major
> Attachments: r352_20181025b.patch
>
>
> Current the commit index is not persisted in the Raft log.  When a server 
> restarts, it cannot apply its log until it has joined a Raft group.  There is 
> no problem if there is a Raft group.  
> However, a server cannot recover its data when formatting a Raft group is 
> impossible (e.g. a majority of servers are dead).  Ideally, a server can 
> safely apply the log up to the commit index.  The JIRA is to persist the 
> commit index so that such recovery is possible.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (RATIS-352) Persist commit index in Raft log.

2018-10-26 Thread Tsz Wo Nicholas Sze (JIRA)


 [ 
https://issues.apache.org/jira/browse/RATIS-352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tsz Wo Nicholas Sze updated RATIS-352:
--
Attachment: r352_20181026.patch

> Persist commit index in Raft log.
> -
>
> Key: RATIS-352
> URL: https://issues.apache.org/jira/browse/RATIS-352
> Project: Ratis
>  Issue Type: Improvement
>  Components: server
>Reporter: Tsz Wo Nicholas Sze
>Assignee: Tsz Wo Nicholas Sze
>Priority: Major
> Attachments: r352_20181026.patch
>
>
> Current the commit index is not persisted in the Raft log.  When a server 
> restarts, it cannot apply its log until it has joined a Raft group.  There is 
> no problem if there is a Raft group.  
> However, a server cannot recover its data when formatting a Raft group is 
> impossible (e.g. a majority of servers are dead).  Ideally, a server can 
> safely apply the log up to the commit index.  The JIRA is to persist the 
> commit index so that such recovery is possible.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (RATIS-352) Persist commit index in Raft log.

2018-10-26 Thread Tsz Wo Nicholas Sze (JIRA)


 [ 
https://issues.apache.org/jira/browse/RATIS-352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tsz Wo Nicholas Sze updated RATIS-352:
--
Attachment: (was: r352_20181025b.patch)

> Persist commit index in Raft log.
> -
>
> Key: RATIS-352
> URL: https://issues.apache.org/jira/browse/RATIS-352
> Project: Ratis
>  Issue Type: Improvement
>  Components: server
>Reporter: Tsz Wo Nicholas Sze
>Assignee: Tsz Wo Nicholas Sze
>Priority: Major
> Attachments: r352_20181026.patch
>
>
> Current the commit index is not persisted in the Raft log.  When a server 
> restarts, it cannot apply its log until it has joined a Raft group.  There is 
> no problem if there is a Raft group.  
> However, a server cannot recover its data when formatting a Raft group is 
> impossible (e.g. a majority of servers are dead).  Ideally, a server can 
> safely apply the log up to the commit index.  The JIRA is to persist the 
> commit index so that such recovery is possible.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (RATIS-352) Persist commit index in Raft log.

2018-10-30 Thread Tsz Wo Nicholas Sze (JIRA)


 [ 
https://issues.apache.org/jira/browse/RATIS-352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tsz Wo Nicholas Sze updated RATIS-352:
--
Attachment: r352_20181030.patch

> Persist commit index in Raft log.
> -
>
> Key: RATIS-352
> URL: https://issues.apache.org/jira/browse/RATIS-352
> Project: Ratis
>  Issue Type: Improvement
>  Components: server
>Reporter: Tsz Wo Nicholas Sze
>Assignee: Tsz Wo Nicholas Sze
>Priority: Major
> Attachments: r352_20181030.patch
>
>
> Current the commit index is not persisted in the Raft log.  When a server 
> restarts, it cannot apply its log until it has joined a Raft group.  There is 
> no problem if there is a Raft group.  
> However, a server cannot recover its data when formatting a Raft group is 
> impossible (e.g. a majority of servers are dead).  Ideally, a server can 
> safely apply the log up to the commit index.  The JIRA is to persist the 
> commit index so that such recovery is possible.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (RATIS-352) Persist commit index in Raft log.

2018-10-30 Thread Tsz Wo Nicholas Sze (JIRA)


 [ 
https://issues.apache.org/jira/browse/RATIS-352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tsz Wo Nicholas Sze updated RATIS-352:
--
Attachment: (was: r352_20181026.patch)

> Persist commit index in Raft log.
> -
>
> Key: RATIS-352
> URL: https://issues.apache.org/jira/browse/RATIS-352
> Project: Ratis
>  Issue Type: Improvement
>  Components: server
>Reporter: Tsz Wo Nicholas Sze
>Assignee: Tsz Wo Nicholas Sze
>Priority: Major
> Attachments: r352_20181030.patch
>
>
> Current the commit index is not persisted in the Raft log.  When a server 
> restarts, it cannot apply its log until it has joined a Raft group.  There is 
> no problem if there is a Raft group.  
> However, a server cannot recover its data when formatting a Raft group is 
> impossible (e.g. a majority of servers are dead).  Ideally, a server can 
> safely apply the log up to the commit index.  The JIRA is to persist the 
> commit index so that such recovery is possible.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (RATIS-352) Persist commit index in Raft log.

2018-11-03 Thread Tsz Wo Nicholas Sze (JIRA)


 [ 
https://issues.apache.org/jira/browse/RATIS-352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tsz Wo Nicholas Sze updated RATIS-352:
--
Attachment: (was: r352_20181030.patch)

> Persist commit index in Raft log.
> -
>
> Key: RATIS-352
> URL: https://issues.apache.org/jira/browse/RATIS-352
> Project: Ratis
>  Issue Type: Improvement
>  Components: server
>Reporter: Tsz Wo Nicholas Sze
>Assignee: Tsz Wo Nicholas Sze
>Priority: Major
> Attachments: r352_20181104.patch
>
>
> Current the commit index is not persisted in the Raft log.  When a server 
> restarts, it cannot apply its log until it has joined a Raft group.  There is 
> no problem if there is a Raft group.  
> However, a server cannot recover its data when formatting a Raft group is 
> impossible (e.g. a majority of servers are dead).  Ideally, a server can 
> safely apply the log up to the commit index.  The JIRA is to persist the 
> commit index so that such recovery is possible.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (RATIS-352) Persist commit index in Raft log.

2018-11-03 Thread Tsz Wo Nicholas Sze (JIRA)


 [ 
https://issues.apache.org/jira/browse/RATIS-352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tsz Wo Nicholas Sze updated RATIS-352:
--
Attachment: r352_20181104.patch

> Persist commit index in Raft log.
> -
>
> Key: RATIS-352
> URL: https://issues.apache.org/jira/browse/RATIS-352
> Project: Ratis
>  Issue Type: Improvement
>  Components: server
>Reporter: Tsz Wo Nicholas Sze
>Assignee: Tsz Wo Nicholas Sze
>Priority: Major
> Attachments: r352_20181104.patch
>
>
> Current the commit index is not persisted in the Raft log.  When a server 
> restarts, it cannot apply its log until it has joined a Raft group.  There is 
> no problem if there is a Raft group.  
> However, a server cannot recover its data when formatting a Raft group is 
> impossible (e.g. a majority of servers are dead).  Ideally, a server can 
> safely apply the log up to the commit index.  The JIRA is to persist the 
> commit index so that such recovery is possible.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (RATIS-352) Persist commit index in Raft log.

2018-11-06 Thread Tsz Wo Nicholas Sze (JIRA)


 [ 
https://issues.apache.org/jira/browse/RATIS-352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tsz Wo Nicholas Sze updated RATIS-352:
--
Attachment: r352_20181106.patch

> Persist commit index in Raft log.
> -
>
> Key: RATIS-352
> URL: https://issues.apache.org/jira/browse/RATIS-352
> Project: Ratis
>  Issue Type: Improvement
>  Components: server
>Reporter: Tsz Wo Nicholas Sze
>Assignee: Tsz Wo Nicholas Sze
>Priority: Major
> Attachments: r352_20181106.patch
>
>
> Current the commit index is not persisted in the Raft log.  When a server 
> restarts, it cannot apply its log until it has joined a Raft group.  There is 
> no problem if there is a Raft group.  
> However, a server cannot recover its data when formatting a Raft group is 
> impossible (e.g. a majority of servers are dead).  Ideally, a server can 
> safely apply the log up to the commit index.  The JIRA is to persist the 
> commit index so that such recovery is possible.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (RATIS-352) Persist commit index in Raft log.

2018-11-06 Thread Tsz Wo Nicholas Sze (JIRA)


 [ 
https://issues.apache.org/jira/browse/RATIS-352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tsz Wo Nicholas Sze updated RATIS-352:
--
Attachment: (was: r352_20181104.patch)

> Persist commit index in Raft log.
> -
>
> Key: RATIS-352
> URL: https://issues.apache.org/jira/browse/RATIS-352
> Project: Ratis
>  Issue Type: Improvement
>  Components: server
>Reporter: Tsz Wo Nicholas Sze
>Assignee: Tsz Wo Nicholas Sze
>Priority: Major
> Attachments: r352_20181106.patch
>
>
> Current the commit index is not persisted in the Raft log.  When a server 
> restarts, it cannot apply its log until it has joined a Raft group.  There is 
> no problem if there is a Raft group.  
> However, a server cannot recover its data when formatting a Raft group is 
> impossible (e.g. a majority of servers are dead).  Ideally, a server can 
> safely apply the log up to the commit index.  The JIRA is to persist the 
> commit index so that such recovery is possible.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (RATIS-352) Persist commit index in Raft log.

2018-11-07 Thread Tsz Wo Nicholas Sze (JIRA)


 [ 
https://issues.apache.org/jira/browse/RATIS-352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tsz Wo Nicholas Sze updated RATIS-352:
--
Attachment: r352_20181107.patch

> Persist commit index in Raft log.
> -
>
> Key: RATIS-352
> URL: https://issues.apache.org/jira/browse/RATIS-352
> Project: Ratis
>  Issue Type: Improvement
>  Components: server
>Reporter: Tsz Wo Nicholas Sze
>Assignee: Tsz Wo Nicholas Sze
>Priority: Major
> Attachments: r352_20181106.patch, r352_20181107.patch
>
>
> Current the commit index is not persisted in the Raft log.  When a server 
> restarts, it cannot apply its log until it has joined a Raft group.  There is 
> no problem if there is a Raft group.  
> However, a server cannot recover its data when formatting a Raft group is 
> impossible (e.g. a majority of servers are dead).  Ideally, a server can 
> safely apply the log up to the commit index.  The JIRA is to persist the 
> commit index so that such recovery is possible.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (RATIS-352) Persist commit index in Raft log.

2018-11-15 Thread Tsz Wo Nicholas Sze (JIRA)


 [ 
https://issues.apache.org/jira/browse/RATIS-352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tsz Wo Nicholas Sze updated RATIS-352:
--
Attachment: r352_20181115.patch

> Persist commit index in Raft log.
> -
>
> Key: RATIS-352
> URL: https://issues.apache.org/jira/browse/RATIS-352
> Project: Ratis
>  Issue Type: Improvement
>  Components: server
>Reporter: Tsz Wo Nicholas Sze
>Assignee: Tsz Wo Nicholas Sze
>Priority: Major
> Attachments: r352_20181106.patch, r352_20181107.patch, 
> r352_20181115.patch
>
>
> Current the commit index is not persisted in the Raft log.  When a server 
> restarts, it cannot apply its log until it has joined a Raft group.  There is 
> no problem if there is a Raft group.  
> However, a server cannot recover its data when formatting a Raft group is 
> impossible (e.g. a majority of servers are dead).  Ideally, a server can 
> safely apply the log up to the commit index.  The JIRA is to persist the 
> commit index so that such recovery is possible.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (RATIS-352) Persist commit index in Raft log.

2018-11-17 Thread Tsz Wo Nicholas Sze (JIRA)


 [ 
https://issues.apache.org/jira/browse/RATIS-352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tsz Wo Nicholas Sze updated RATIS-352:
--
Attachment: r352_20181117.patch

> Persist commit index in Raft log.
> -
>
> Key: RATIS-352
> URL: https://issues.apache.org/jira/browse/RATIS-352
> Project: Ratis
>  Issue Type: Improvement
>  Components: server
>Reporter: Tsz Wo Nicholas Sze
>Assignee: Tsz Wo Nicholas Sze
>Priority: Major
> Attachments: r352_20181106.patch, r352_20181107.patch, 
> r352_20181115.patch, r352_20181117.patch
>
>
> Current the commit index is not persisted in the Raft log.  When a server 
> restarts, it cannot apply its log until it has joined a Raft group.  There is 
> no problem if there is a Raft group.  
> However, a server cannot recover its data when formatting a Raft group is 
> impossible (e.g. a majority of servers are dead).  Ideally, a server can 
> safely apply the log up to the commit index.  The JIRA is to persist the 
> commit index so that such recovery is possible.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (RATIS-352) Persist commit index in Raft log.

2018-11-17 Thread Tsz Wo Nicholas Sze (JIRA)


 [ 
https://issues.apache.org/jira/browse/RATIS-352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tsz Wo Nicholas Sze updated RATIS-352:
--
Attachment: r352_20181117b.patch

> Persist commit index in Raft log.
> -
>
> Key: RATIS-352
> URL: https://issues.apache.org/jira/browse/RATIS-352
> Project: Ratis
>  Issue Type: Improvement
>  Components: server
>Reporter: Tsz Wo Nicholas Sze
>Assignee: Tsz Wo Nicholas Sze
>Priority: Major
> Attachments: r352_20181106.patch, r352_20181107.patch, 
> r352_20181115.patch, r352_20181117.patch, r352_20181117b.patch
>
>
> Current the commit index is not persisted in the Raft log.  When a server 
> restarts, it cannot apply its log until it has joined a Raft group.  There is 
> no problem if there is a Raft group.  
> However, a server cannot recover its data when formatting a Raft group is 
> impossible (e.g. a majority of servers are dead).  Ideally, a server can 
> safely apply the log up to the commit index.  The JIRA is to persist the 
> commit index so that such recovery is possible.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (RATIS-352) Persist commit index in Raft log.

2018-11-18 Thread Tsz Wo Nicholas Sze (JIRA)


 [ 
https://issues.apache.org/jira/browse/RATIS-352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tsz Wo Nicholas Sze updated RATIS-352:
--
Attachment: r352_20181118.patch

> Persist commit index in Raft log.
> -
>
> Key: RATIS-352
> URL: https://issues.apache.org/jira/browse/RATIS-352
> Project: Ratis
>  Issue Type: Improvement
>  Components: server
>Reporter: Tsz Wo Nicholas Sze
>Assignee: Tsz Wo Nicholas Sze
>Priority: Major
> Attachments: r352_20181106.patch, r352_20181107.patch, 
> r352_20181115.patch, r352_20181117.patch, r352_20181117b.patch, 
> r352_20181118.patch
>
>
> Current the commit index is not persisted in the Raft log.  When a server 
> restarts, it cannot apply its log until it has joined a Raft group.  There is 
> no problem if there is a Raft group.  
> However, a server cannot recover its data when formatting a Raft group is 
> impossible (e.g. a majority of servers are dead).  Ideally, a server can 
> safely apply the log up to the commit index.  The JIRA is to persist the 
> commit index so that such recovery is possible.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (RATIS-352) Persist commit index in Raft log.

2018-11-19 Thread Tsz Wo Nicholas Sze (JIRA)


 [ 
https://issues.apache.org/jira/browse/RATIS-352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tsz Wo Nicholas Sze updated RATIS-352:
--
Attachment: r352_20181119.patch

> Persist commit index in Raft log.
> -
>
> Key: RATIS-352
> URL: https://issues.apache.org/jira/browse/RATIS-352
> Project: Ratis
>  Issue Type: Improvement
>  Components: server
>Reporter: Tsz Wo Nicholas Sze
>Assignee: Tsz Wo Nicholas Sze
>Priority: Major
> Attachments: r352_20181106.patch, r352_20181107.patch, 
> r352_20181115.patch, r352_20181117.patch, r352_20181117b.patch, 
> r352_20181118.patch, r352_20181119.patch
>
>
> Current the commit index is not persisted in the Raft log.  When a server 
> restarts, it cannot apply its log until it has joined a Raft group.  There is 
> no problem if there is a Raft group.  
> However, a server cannot recover its data when formatting a Raft group is 
> impossible (e.g. a majority of servers are dead).  Ideally, a server can 
> safely apply the log up to the commit index.  The JIRA is to persist the 
> commit index so that such recovery is possible.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (RATIS-352) Persist commit index in Raft log.

2018-11-20 Thread Tsz Wo Nicholas Sze (JIRA)


 [ 
https://issues.apache.org/jira/browse/RATIS-352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tsz Wo Nicholas Sze updated RATIS-352:
--
Attachment: r352_20181120.patch

> Persist commit index in Raft log.
> -
>
> Key: RATIS-352
> URL: https://issues.apache.org/jira/browse/RATIS-352
> Project: Ratis
>  Issue Type: Improvement
>  Components: server
>Reporter: Tsz Wo Nicholas Sze
>Assignee: Tsz Wo Nicholas Sze
>Priority: Major
> Attachments: r352_20181106.patch, r352_20181107.patch, 
> r352_20181115.patch, r352_20181117.patch, r352_20181117b.patch, 
> r352_20181118.patch, r352_20181119.patch, r352_20181120.patch
>
>
> Current the commit index is not persisted in the Raft log.  When a server 
> restarts, it cannot apply its log until it has joined a Raft group.  There is 
> no problem if there is a Raft group.  
> However, a server cannot recover its data when formatting a Raft group is 
> impossible (e.g. a majority of servers are dead).  Ideally, a server can 
> safely apply the log up to the commit index.  The JIRA is to persist the 
> commit index so that such recovery is possible.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)