IGNITE-28770 : Introduce a operation context attributes registry v2#13243
IGNITE-28770 : Introduce a operation context attributes registry v2#13243Vladsz83 wants to merge 32 commits into
Conversation
…-attributes-registry
…-attributes-registry
…-attributes-registry_v2
…-attributes-registry_v2
|
It's also worth adding meaningful comments describing the purpose of DistributedOperationContextManager and its methods. What is DistributedOperationContextMessage and why was it decided to use a bitmap. |
| "join request (consider increasing 'joinTimeout' configuration property) " + | ||
| "[joinTimeout=" + spi.joinTimeout + ", sock=" + currSock + ']')); | ||
|
|
||
| if (msg instanceof TcpDiscoveryAbstractMessage msg0 && msg0.opCtxMsg != null) { |
There was a problem hiding this comment.
Let's just leave the method as is, but wrap all of its code in a try-with-resource block.
There was a problem hiding this comment.
I cannot wrap entire code because there would not be a message yet.
There was a problem hiding this comment.
Obviously, that's not what I meant. Let's wrap the code related to processing of the message from the moment it is polled from the queue, but not move anything to other new methods.
In the current state of the code, moving the message handling logic into a separate method seems awkward. It's better to refactor this later in a separate ticket.
There was a problem hiding this comment.
We've already moved message processing in a dedicated methods in same manner at other places. Message is a Object here, not even a Message. I need to check its type first. An if is required. That is why I introduce a method or did the processing in the part of code before.
No description provided.