MCS provides several timeout values that work together to allow you to more safely reclaim allocated IDs that are no longer in use but which have not been released by the client. Use caution when reclaiming allocated IDs; if you're not absolutely sure that an ID is no longer in use, there is some risk that duplicate IDs will be issued.
At the pool level, MCS provides two timeout options: Inactivity Timeout and Lease Timeout. These are pool properties. At the global level, MCS provides a Communication Timeout and a Quarantine Timeout. These are general properties.
You can change the timeout values at any time but allocated IDs continue to use the previous values until they are released.
The inactivity timeout period and the lease timeout period (if implemented) are used together to determine whether an ID should be quarantined. For clients that don't implement those options, or for pools where those values have been omitted or set to zero (0), the communication timeout period performs a similar function.
When the quarantine timeout period elapses, the ID is eligible to be reclaimed. Quarantined IDs can be automatically reclaimed by MCS or they can be manually reclaimed on a case-by-case basis, using one of the following procedures. When an ID is reclaimed, it is made available to be allocated to another client.
|To set global options for automatically reclaiming IDs|
|To manually reclaim an ID|
|Managing Host Access IDs, Overview|
|Configuring ID Pools|