[
https://issues.apache.org/jira/browse/IGNITE-12400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17016920#comment-17016920
]
Ignite TC Bot commented on IGNITE-12400:
----------------------------------------
{panel:title=Branch: [pull/7268/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4934381&buildTypeId=IgniteTests24Java8_RunAll]
> Remove the stopProcess method from the DiscoveryCustomMessage interface
> -----------------------------------------------------------------------
>
> Key: IGNITE-12400
> URL: https://issues.apache.org/jira/browse/IGNITE-12400
> Project: Ignite
> Issue Type: Task
> Reporter: Amelchev Nikita
> Assignee: Amelchev Nikita
> Priority: Minor
> Fix For: 2.9
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently, the {{stopProcess}} method works only if the {{zookeeper
> discovery}} configured. It doesn't work in {{TcpDiscoverySpi}}. There are no
> any usages of this method except tests. I suggest to remove it from the
> discovery custom message interface.
> [Dev-list
> discussion.|http://apache-ignite-developers.2346864.n4.nabble.com/Unclear-to-use-methods-in-the-DiscoverySpiCustomMessage-interface-td44144.html]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
