[
https://issues.apache.org/jira/browse/IGNITE-28987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18104711#comment-18104711
]
Ignite TC Bot commented on IGNITE-28987:
----------------------------------------
{panel:title=Branch: [pull/13478/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/13478/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=9280873&buildTypeId=IgniteTests24Java8_RunAll]
{color:#ffffff}tcbot-analysis-comment chainBuildId=9280873
rerunBuildIds=none{color}
> ContinousRoutineLocalInfo should use same marshaller as
> ContinousRoutineDiscoveryDataItem
> -----------------------------------------------------------------------------------------
>
> Key: IGNITE-28987
> URL: https://issues.apache.org/jira/browse/IGNITE-28987
> Project: Ignite
> Issue Type: Improvement
> Reporter: Vladimir Steshin
> Priority: Major
>
> `ContinousRoutineLocalInfo` ate marshalled in a discovery thread. Like
> `ContinousRoutineDiscoveryDataItem`, is shoudn't use `BinaryMarshaller` to
> avoid possible deadlocks. Currently, we use `JDKMarshaller` in `Discvoery`.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
