[jira] Updated: (CHUKWA-369) proposed reliability mechanism

["Ari Rabkin (JIRA)" <ji...@apache.org>]

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

Ari Rabkin updated CHUKWA-369:
------------------------------

    Attachment: delayedAcks.patch

Okay. I have this coded up and working locally. Users are able to choose between this new mechanism, and the existing ones. I will test at Berkeley and report my performance results.  I needed to do some fairly major refactoring of the Sender and Connector code, but I think it's a win in general.

I am not yet proposing to commit this and the patch, as yet, is not intended for inclusion.  Rather, I'm posting it to get comments on the overall structure and to clarify what I intended.

> proposed reliability mechanism
> ------------------------------
>
>                 Key: CHUKWA-369
>                 URL: https://issues.apache.org/jira/browse/CHUKWA-369
>             Project: Hadoop Chukwa
>          Issue Type: New Feature
>          Components: data collection
>    Affects Versions: 0.3.0
>            Reporter: Ari Rabkin
>            Assignee: Ari Rabkin
>             Fix For: 0.3.0
>
>         Attachments: delayedAcks.patch
>
>
> We like to say that Chukwa is a system for reliable log collection. It isn't, quite, since we don't handle collector crashes.  Here's a proposed reliability mechanism.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.