You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Yuki Morishita (Created) (JIRA)" <ji...@apache.org> on 2012/01/31 01:03:10 UTC

[jira] [Created] (CASSANDRA-3817) Add failure callback interface to streaming

Add failure callback interface to streaming
-------------------------------------------

                 Key: CASSANDRA-3817
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-3817
             Project: Cassandra
          Issue Type: Improvement
          Components: Core
            Reporter: Yuki Morishita
            Priority: Minor


There are several issues (CASSANDRA-3730, CASSANDRA-3776 and such) reported where streaming failure needs to be handled, but currently there is no place to hook the code to handle failure.

This issue is just for adding callback interface to stream sessions for future fixes.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Updated] (CASSANDRA-3817) Add failure callback interface to streaming

Posted by "Yuki Morishita (Updated) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CASSANDRA-3817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Yuki Morishita updated CASSANDRA-3817:
--------------------------------------

    Attachment: 3817.txt

Although there is ongoing discussion on whether to use FailureDetector for detecting streaming failure (CASSANDRA-3569), I assembled the patch to add callback interface, based on Sylvain's CASSANDRA-3112 patch.

Any feedback is appreciated.
                
> Add failure callback interface to streaming
> -------------------------------------------
>
>                 Key: CASSANDRA-3817
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-3817
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Yuki Morishita
>            Priority: Minor
>              Labels: streaming
>         Attachments: 3817.txt
>
>
> There are several issues (CASSANDRA-3730, CASSANDRA-3776 and such) reported where streaming failure needs to be handled, but currently there is no place to hook the code to handle failure.
> This issue is just for adding callback interface to stream sessions for future fixes.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Resolved] (CASSANDRA-3817) Add failure callback interface to streaming

Posted by "Yuki Morishita (Resolved) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CASSANDRA-3817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Yuki Morishita resolved CASSANDRA-3817.
---------------------------------------

    Resolution: Duplicate

Closing as Duplicate since attached patch was committed as  part of CASSANDRA-4051
                
> Add failure callback interface to streaming
> -------------------------------------------
>
>                 Key: CASSANDRA-3817
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-3817
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Yuki Morishita
>            Priority: Minor
>              Labels: streaming
>         Attachments: 3817.txt
>
>
> There are several issues (CASSANDRA-3730, CASSANDRA-3776 and such) reported where streaming failure needs to be handled, but currently there is no place to hook the code to handle failure.
> This issue is just for adding callback interface to stream sessions for future fixes.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira