ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mikhail Cherkasov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-5521) Large near caches lead to cluster instability with metrics enabled
Date Thu, 29 Jun 2017 09:54:00 GMT

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

Mikhail Cherkasov commented on IGNITE-5521:

changeset: https://github.com/apache/ignite/commit/f6cbba3f50668bc5dedd5b3e4b3a98ab94956492

> Large near caches lead to cluster instability with metrics enabled
> ------------------------------------------------------------------
>                 Key: IGNITE-5521
>                 URL: https://issues.apache.org/jira/browse/IGNITE-5521
>             Project: Ignite
>          Issue Type: Bug
>          Components: cache, general
>    Affects Versions: 1.7
>            Reporter: Alexey Goncharuk
>            Assignee: Mikhail Cherkasov
>            Priority: Critical
>              Labels: important
>             Fix For: 2.1
> We have two issues in the way cache metrics are working:
> 1) Near cache size is calculated using full iteration over the near entries. Perhaps,
this is done because of near entries may be invalidated by a primary node change, however,
we should give a less strict metric rather than O(N) cache size time
> 2) Cache metrics are copied in discovery worker threads. This looks a bit risky because
an error like the one described before may stall the whole cluster. We need to make sure that
when the heartbeat message is processed, we already have a metrics snapshot enabled

This message was sent by Atlassian JIRA

View raw message