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 17:59:00 UTC
[jira] [Updated] (RATIS-1061) Unique ID service in Ratis
[ https://issues.apache.org/jira/browse/RATIS-1061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rui Wang updated RATIS-1061:
----------------------------
Description:
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. The uniqueness should be guaranteed even when facing split-brain case.
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.
was:
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. The uniqueness should be guaranteed even when facing split-brain case.
Currently hadoop-zone has a requirement in SCM HA where it must guarantee generating unique container ID.
Raft might provide a service to serve such common need.
> Unique ID service in Ratis
> ---------------------------
>
> Key: RATIS-1061
> URL: https://issues.apache.org/jira/browse/RATIS-1061
> Project: Ratis
> Issue Type: Task
> Reporter: 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. The uniqueness should be guaranteed even when facing split-brain case.
> 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.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)