You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ratis.apache.org by "Rui Wang (Jira)" <ji...@apache.org> on 2020/09/12 18:28:00 UTC

[jira] [Comment Edited] (RATIS-1061) Accessible state service in Ratis

    [ https://issues.apache.org/jira/browse/RATIS-1061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17194820#comment-17194820 ] 

Rui Wang edited comment on RATIS-1061 at 9/12/20, 6:27 PM:
-----------------------------------------------------------

Assign to me right now to drive the discussion of this topic. Sent an email to dev@ to  try to raise attention on this JIRA.


was (Author: amaliujia):
Assign to me right now to drive the discussion of this topic.

> Accessible state service in Ratis
> ---------------------------------
>
>                 Key: RATIS-1061
>                 URL: https://issues.apache.org/jira/browse/RATIS-1061
>             Project: Ratis
>          Issue Type: Task
>            Reporter: Rui Wang
>            Assignee: Rui Wang
>            Priority: Major
>
> It is not an unusual requirement to generate and maintain a series of monotonic increasing unique numbers in a distributed environment, and provide API like "long getNextUniqueID()", which guarantees uniqueness of the returned number. 
> Currently hadoop-zone has a requirement in SCM HA where it must guarantee generating unique container ID. 
> Ratis might be a place to serve such common need. E.g. Ratis leader might be the place to maintain this state and increase the number and reach the consensus among Ratis ring. 
> To make this functionality more generic, Ratis might allow applications to specify a state and a function to change the state. Ratis will only need to keep agreeing the new state when having API calls.  Ratis shall offer API to access the state.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)