Why does OM Node ID used as SCM Container owner?

[ivandika3]

Related to this discussion #4803. While I was looking at possible contentions between multiple OM HA services, I found that OM passes its Node ID in the allocate block request (e.g. under OMKeyRequest#allocateBlock), this Node ID is then used by SCM's Container Manager to used as the container's owner. The Node ID will subsequently be used to get the matching container within the pipeline (ContainerManagerImpl#getMatchingContainer and ContainerManagerImpl#getMatchingContainer). I have two questions:

1. Single OM HA Service: If OM service HA leadership change, the OM leader's Node ID might change. What will happen on the containers owned by the previous OM leader's Node ID?
   • Is it better to use OM Service ID as container owner instead of OM Node ID (or maybe Service ID + Node ID)?
2. Multiple OM HA Services: Would there be any conflict if two OM HA services share the same container (i.e. there are overlapping Node IDs between the OM HA Services)?

Currently, I setup the configurations of multiple OM HA services to ensure that the OM Node ID is unique across all the OM HA services.

Thank you in advance.

[ivandika3]

Hi @nandakumar131 @bharatviswa504 could you kindly help address this?

[ivandika3]

It's currently being addressed in #4922