Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Generate Unique EcChronos ID #678

Closed
3 tasks
VictorCavichioli opened this issue Jun 17, 2024 · 0 comments
Closed
3 tasks

Generate Unique EcChronos ID #678

VictorCavichioli opened this issue Jun 17, 2024 · 0 comments
Assignees
Labels
enhancement New feature or request PoC/Agent Tasks related to new generation of ecchronos as an agent

Comments

@VictorCavichioli
Copy link
Contributor

Story Description:
As the ecchronos_id is the partition key for nodes_sync table, the goal is to find a way to create a unique identification for the instance, so when a node is acquired by that instance the nodes_sync must receive a static value, it must have the same id even if the instance goes down.

Acceptance Criteria:

  • Code designed as described
  • Test cases
  • Documentation updated

Definition of Done:

Code designed as described and approved by maintainers

Notes:

Related to #652 and #672

@VictorCavichioli VictorCavichioli added enhancement New feature or request PoC/Agent Tasks related to new generation of ecchronos as an agent labels Jun 17, 2024
@SajidRiaz138 SajidRiaz138 self-assigned this Sep 16, 2024
SajidRiaz138 pushed a commit to SajidRiaz138/ecchronos that referenced this issue Sep 19, 2024
SajidRiaz138 pushed a commit to SajidRiaz138/ecchronos that referenced this issue Sep 19, 2024
- Generate eccrhonos_Id that should be unique (uuid + host name)
- on start up instance, first check nodes_metadata
table for ecchronosId, if it already exists, use that
one, otherwise generate now one.
- So due to persistence of eccronosId, it would be same
even instance get reinstalled or restart.
- when instance try to acquire nodes then add this
newly ecchronosId into nodes_metadata table with datacenter
and nodeId.
- The new table nodes_metadata schenma, datacenter is partition key
and nodeId is clustering colum and ecchrons_id coulum would hold the
Id.
SajidRiaz138 pushed a commit to SajidRiaz138/ecchronos that referenced this issue Sep 19, 2024
- Generate eccrhonos_Id that should be unique (uuid + host name)
- on start up instance, first check nodes_metadata
table for ecchronosId, if it already exists, use that
one, otherwise generate now one.
- So due to persistence of eccronosId, it would be same
even instance get reinstalled or restart.
- when instance try to acquire nodes then add this
newly ecchronosId into nodes_metadata table with datacenter
and nodeId.
- The new table nodes_metadata schenma, datacenter is partition key
and nodeId is clustering colum and ecchrons_id coulum would hold the
Id.
SajidRiaz138 pushed a commit to SajidRiaz138/ecchronos that referenced this issue Oct 8, 2024
SajidRiaz138 pushed a commit to SajidRiaz138/ecchronos that referenced this issue Oct 8, 2024
- eccrhonos instance name will be
 used as  eccrhonos_Id and configure
in ecc.yml file.
- each eccrhonos instance must have
unique name.
SajidRiaz138 pushed a commit to SajidRiaz138/ecchronos that referenced this issue Oct 9, 2024
- eccrhonos instance name will be
 used as  eccrhonos_Id and configure
in ecc.yml file.
- each eccrhonos instance must have
unique name.
SajidRiaz138 pushed a commit to SajidRiaz138/ecchronos that referenced this issue Oct 9, 2024
- eccrhonos instance name will be
 used as  eccrhonos_Id and configure
in ecc.yml file.
- each eccrhonos instance must have
unique name.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request PoC/Agent Tasks related to new generation of ecchronos as an agent
Projects
None yet
Development

No branches or pull requests

2 participants