[SLIDER-463] Have each container instance for a role be assigned with a unique integer id starting at 1 up to maximum requested instances

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: Slider 0.50
• Fix Version/s: Slider 0.60
• Component/s: agent-provider
• Labels: feedback
• Sprint: Slider October #2
• Assignee: Sumit Mohanty
• Reporter: Sumit Mohanty
• Created: 29/Sep/14 04:28
• Updated: 24/Oct/14 20:26
• Resolved: 17/Oct/14 16:17

Description

Apps can request a number of instances and the id associated with a container is the container id. However, container ids are not a reliable way to load balance a work load across several instances. This is because container id is not guaranteed to be well-distributed for specific role instances.

A good example of application requiring a id is memcached where clients need to know which memcached daemon instance to connect for specific keys (e..g hash a key to obtain an integer and access the daemon associated with that integer). Alternatively, another example will be an application of peers that select workload based on their id. Say, an application processes 100 data points and component instances can select which sub-range to process based on their id.