cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Brown (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-13905) Correctly close netty channels when a stream session ends
Date Fri, 29 Sep 2017 16:37:00 GMT

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

Jason Brown updated CASSANDRA-13905:
------------------------------------
       Resolution: Fixed
    Fix Version/s:     (was: 4.x)
                   4.0
           Status: Resolved  (was: Ready to Commit)

bq. Collectors are the don't be lazy step in streams

Yeah that's where I messed up originally :).

committed as sha {[ebefc96a8fe63aca5f324984f7f3147f10218643}}.

> Correctly close netty channels when a stream session ends
> ---------------------------------------------------------
>
>                 Key: CASSANDRA-13905
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-13905
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Streaming and Messaging
>            Reporter: Jason Brown
>            Assignee: Jason Brown
>             Fix For: 4.0
>
>
> Netty channels in stream sessions were not being closed correctly. TL;DR I was using
a lambda that was not executing as it is lazily evaluated. This was causing a {{RejectedExecutionException}}
at the end of some streaming-related dtests



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org


Mime
View raw message