[jira] [Updated] (CELIX-361) etcd_watcher notifications loss when ETCD transaction rate is high

["Gabriele Ricciardi (JIRA)" <ji...@apache.org>]

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

Gabriele Ricciardi updated CELIX-361:
-------------------------------------
    Attachment: etcd_lost_transactions.patch

> etcd_watcher notifications loss when ETCD transaction rate is high
> ------------------------------------------------------------------
>
>                 Key: CELIX-361
>                 URL: https://issues.apache.org/jira/browse/CELIX-361
>             Project: Celix
>          Issue Type: Bug
>          Components: Remote Service Admin
>            Reporter: Gabriele Ricciardi
>         Attachments: etcd_lost_transactions.patch
>
>
> ETCD, by design, keeps track only of the last 1000 transactions. The transactions counter is globally used. In certain occasions (e.g. during the startup of a wide system using ETCD as information exchange database) the transactions counter increases very fast.
> When the etcd_watcher listening for changes on a certain folder is notified, it gets back the next valid transaction id to use for watching, or an error in case the transaction id increased more than 1000 (such a mechanism is used to notify the watcher of possible history loss).
> The error handling is not implemented in the discovery_etcd.
> Attached a patch that (should) fix the issue by implementing this error handling mechanism.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)