In the TAC environment, when Lazy Sgmt Drop is performed at a certain point, an Internal Error occurred as Sgmts in use on some Nodes were dropped together.

<Cause 1>
During the Lazy Sgmt Drop process, the Master Node receives the Droppable Sgmt List from each Node and then creates an Intersection List based on Sgmt IDs commonly included.
In this process, the condition for creating the Intersection List was not properly applied, causing the Droppable Sgmt List of a specific Node to be included in the entire Intersection List, resulting in Sgmts in use by other Nodes being dropped and causing an Internal Error.

<Cause 2>
The Slave Node connects the Droppable Sgmt List to the Arg structure, and the Master Node traverses this to create the Intersection List.
In some cases, when two Nodes connect the Sgmt List to Arg simultaneously, the order of reflecting the Sgmt List information temporarily does not match, causing some Nodes’ information to be excluded during Intersection List creation.
As a result, Sgmts in use were dropped, causing an Internal Error.

<Resolution 1>
The logic was revised by reorganizing the condition for Intersection List creation so that the Droppable Sgmt List of all Nodes is accurately reflected.

<Resolution 2>

When connecting the Sgmt List on the Slave Node, a Spin Lock was applied to ensure the order of information reflection.