Octane ID’s not sequential

Category:
Question ID: 109452
2
0

We are trying to get a better understanding about how Octane sequences ID’s.

In one space, we’ve added several users, and the US_ID values are jumping in increments of 1000 without any obvious trigger for moving to the next 1000. So, we have ID’s from 1001 – 1006, then 2001 – 2019, then 3001 – 3003, then 4001 – 4002, then 5001 – 5006. When we import a set of users, the ID’s are back-to-back within the same “1000” grouping. Sometimes, if we add a user later in the day, it gets added to the same “1000” grouping. Other times, a new “1000” grouping starts.

I’m used to ALM always moving sequentially, so I’m just trying to figure out why Octane is jumping to the next 1000 without using up all the values in the previous 1000. The SEQUENCES table is full of values that are all even 1000’s (see attachment). ALM always holds the value of the last ID for a particular artifact.

This is happening for all items. We imported a group of tests, and they all received sequential TS_ID values (1001 – 1068). Adding more tests over the next few days used TS_ID values 2001 – 2009 before jumping to 3001.

The users are confused about why their Test ID’s are not sequential. The gaps make it look like some tests were deleted, even though they weren’t.

Marked as spam
Posted by (Questions: 91, Answers: 0)
Asked on April 22, 2020 8:15 pm
14 views
Answers (1)
2
Private answer

According to MicroFocus
"ALM Octane assigns each item a unique identifier (ID) as it creates the item."

"ALM Octane generates the IDs according to its own internal algorithm, and the IDs are not necessarily assigned in sequential order."

The IDs are allocated and reserved per node in cluster and every restart of node / cluster range might jump up.

So if one request reaches node 1 in cluster, it will be using one range of ids, but if next request reaches next node in cluster, it will use another range of ids.

This is part of performance optimization which allows each node to create entities independent of another nodes and be sure that they are not using same range of IDs.

Hope this information is useful.

Marked as spam
Posted by (Questions: 0, Answers: 340)
Answered on April 22, 2020 8:16 pm