You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Sergey Chugunov (Jira)" <ji...@apache.org> on 2020/08/06 14:25:00 UTC

[jira] [Commented] (IGNITE-13292) Remove unneeded ZkPinger from ZookeeperDiscovery

    [ https://issues.apache.org/jira/browse/IGNITE-13292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17172408#comment-17172408 ] 

Sergey Chugunov commented on IGNITE-13292:
------------------------------------------

[~ivandasch], patch looks good to me, I merged it to master branch in commit *ee7d1369e4008c346c06bad46cb4c2261dc976df*.

Thank you for contribution!

> Remove unneeded ZkPinger from ZookeeperDiscovery
> ------------------------------------------------
>
>                 Key: IGNITE-13292
>                 URL: https://issues.apache.org/jira/browse/IGNITE-13292
>             Project: Ignite
>          Issue Type: Improvement
>          Components: zookeeper
>    Affects Versions: 2.9
>            Reporter: Ivan Daschinskiy
>            Assignee: Ivan Daschinskiy
>            Priority: Trivial
>             Fix For: 2.10
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> We need remove uneeded {{ZkPinger}} from our codebase, introduced in [IGNITE-9683|https://issues.apache.org/jira/browse/IGNITE-9683]. 
> This pinger was introduced to solve issues with server nodes segmentation when cluster is deactivated. The main reason of that is the strange all thread freeze when huge amount of memory is deallocated with {{Unsafe.freeMemory}}, such freeze can last for a minute and more. So this pinger doesn't solve problem at all and this is proved. The working solution to this problem is introduced in [IGNITE-9658|https://issues.apache.org/jira/browse/IGNITE-9658]
> So we should remove this code from our codebase.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)