[jira] [Work logged] (TRAFODION-3334) Communication IO between monitor processes must use timeouts and retries

["ASF GitHub Bot (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/TRAFODION-3334?focusedWorklogId=383320&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-383320 ]

ASF GitHub Bot logged work on TRAFODION-3334:
---------------------------------------------

                Author: ASF GitHub Bot
            Created on: 07/Feb/20 02:25
            Start Date: 07/Feb/20 02:25
    Worklog Time Spent: 10m 
      Work Description: zcorrea commented on pull request #1869: [TRAFODION-3334] Refactored and re-implemented monitor communication.
URL: https://github.com/apache/trafodion/pull/1869
 
 
   All monitor communication channels managed by a specific object in a thread now use a common
   class inherited by the object managing a specific communication channel. This new
   class provides blocking and non-blocking IO methods.
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Issue Time Tracking
-------------------

            Worklog Id:     (was: 383320)
    Remaining Estimate: 0h
            Time Spent: 10m

> Communication IO between monitor processes must use timeouts and retries
> ------------------------------------------------------------------------
>
>                 Key: TRAFODION-3334
>                 URL: https://issues.apache.org/jira/browse/TRAFODION-3334
>             Project: Apache Trafodion
>          Issue Type: Bug
>          Components: foundation
>    Affects Versions: 2.4
>            Reporter: Gonzalo E Correa
>            Priority: Major
>             Fix For: 2.4
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Most communication channels used by monitor processes to exchange cluster state information and to handle failure detection must be changed to asynchronous IO with timeouts and retries to allow for the removal of a monitor process from the cluster communication. This is to prevent a  'Sync Thread Timeout' failure of the entire cluster instance where a monitor process or it host server becomes unresponsive due to a server or network failure.



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