[
https://issues.apache.org/jira/browse/IGNITE-13420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17194968#comment-17194968
]
Konstantin Sirotkin commented on IGNITE-13420:
----------------------------------------------
[Maxim Muzafarov
|file:///jira/secure/ViewProfile.jspa%3fname=mmuzaf]
Initial problem was fixed in
[https://issues.apache.org/jira/browse/IGNITE-12760].
Here I add assertion message for debug in case if assertion will be triggered
by another reason.
> Add assertion message to assert in CachedDeploymentInfo private constructor
> ---------------------------------------------------------------------------
>
> Key: IGNITE-13420
> URL: https://issues.apache.org/jira/browse/IGNITE-13420
> Project: Ignite
> Issue Type: Improvement
> Reporter: Konstantin Sirotkin
> Assignee: Konstantin Sirotkin
> Priority: Minor
> Time Spent: 10m
> Remaining Estimate: 0h
>
> We have an assertion in
> org.apache.ignite.internal.processors.cache.GridCacheDeploymentManager.CachedDeploymentInfo#CachedDeploymentInfo:
>
> {code:java}
> private CachedDeploymentInfo(UUID sndId, IgniteUuid ldrId, String userVer,
> DeploymentMode depMode,
> Map<UUID, IgniteUuid> participants) {
> assert sndId.equals(ldrId.globalId()) || participants != null;
> this.sndId = sndId;
> this.ldrId = ldrId;
> this.userVer = userVer;
> this.depMode = depMode;
> this.participants = participants == null ||
> participants.isEmpty() ? null :
> new ConcurrentLinkedHashMap<>(participants);
> }
> {code}
> Now we can't define assertion reason. We should add assertion message to that
> place.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
