You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@geode.apache.org by "Dick Cavender (Jira)" <ji...@apache.org> on 2019/09/10 23:16:00 UTC

[jira] [Updated] (GEODE-5142) new Thread Monitoring Mechanism

     [ https://issues.apache.org/jira/browse/GEODE-5142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dick Cavender updated GEODE-5142:
---------------------------------
    Fix Version/s: 1.10.0

> new Thread Monitoring Mechanism
> -------------------------------
>
>                 Key: GEODE-5142
>                 URL: https://issues.apache.org/jira/browse/GEODE-5142
>             Project: Geode
>          Issue Type: New Feature
>          Components: docs, management
>            Reporter: yossi reginiano
>            Assignee: Joey McAllister
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.10.0
>
>          Time Spent: 6h 40m
>  Remaining Estimate: 0h
>
> One of the most severe issues hitting our real time application is thread stuck for multiple reasons, such as long lasting locks, deadlocks, threads which wait for reply forever in case of packet drop issue etc...
> Such kind of stuck are under Radar of the existing system health check methods. In mission critical applications, this will be resulted as an immediate outage.
> Here we introduce thread monitoring mechanism, to detect threads which are stuck for any reason.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)