Vladimir Steshin created IGNITE-28964:
-----------------------------------------
Summary: Investigate usage of GridJobSiblingImpl
Key: IGNITE-28964
URL: https://issues.apache.org/jira/browse/IGNITE-28964
Project: Ignite
Issue Type: Task
Reporter: Vladimir Steshin
The questions are:
* Why `{_}ComputeJobSibling#cancel(){_}` is used only in tests.
* Why we serialize both `{_}GridJobSiblingImpl#jobId{_}` and
`{_}GridJobSiblingImpl#sesId{_}`{_}.{_} Do we need `{_}sesId{_}`?
* Why `{_}GridJobSiblingImpl#sesId{_}` cannot be null (the assert in the
constructor)?
* Why we use entyre `{_}ComputeJobSibling{_}` / `{_}GridJobSiblingImpl{_}` in
`{_}GridJobExecuteRequest{_}`? Looks like we need only sibling jobs ids
* Do we need sibling sessions ids in `{_}GridJobExecuteRequest{_}`?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
