[JBoss JIRA] (ISPN-3691) Make client side Connection refused error TRACE
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/ISPN-3691?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on ISPN-3691:
-----------------------------------------------
Dave Stahl <dstahl(a)redhat.com> changed the Status of [bug 1028411|https://bugzilla.redhat.com/show_bug.cgi?id=1028411] from MODIFIED to ON_QA
> Make client side Connection refused error TRACE
> -----------------------------------------------
>
> Key: ISPN-3691
> URL: https://issues.jboss.org/browse/ISPN-3691
> Project: Infinispan
> Issue Type: Feature Request
> Components: Remote Protocols
> Affects Versions: 6.0.0.CR1, 6.0.0.Final
> Reporter: Michal Linhard
> Assignee: Galder Zamarreño
> Priority: Minor
> Fix For: 7.0.0.Final
>
>
> After solving ISPN-3454, it seems that only remaining client-side error during node crashes is "Connection refused":
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JDG/view/RESILIENCE...
> This has been reported before as ISPN-1794 or ISPN-1119, but actually it seems like it reappeared in different place.
> Sorry for not reporting sooner, I got used to ignoring some of the long-open cosmetic low-prio log message issues, that I forgot about this one...
> The issue here is that these "Connection refused" problems are retry-able, so the client log shouldn't contain error.
> Maybe only some info level message about failing over to different node. But that's actually already reported by the INFO level messages about the topology changes
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 12 months
[JBoss JIRA] (ISPN-2183) Add the ability to fetch a set of keys at once (getAll)
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/ISPN-2183?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on ISPN-2183:
-----------------------------------------------
Dave Stahl <dstahl(a)redhat.com> changed the Status of [bug 1213367|https://bugzilla.redhat.com/show_bug.cgi?id=1213367] from MODIFIED to ON_QA
> Add the ability to fetch a set of keys at once (getAll)
> -------------------------------------------------------
>
> Key: ISPN-2183
> URL: https://issues.jboss.org/browse/ISPN-2183
> Project: Infinispan
> Issue Type: Feature Request
> Components: Core
> Reporter: Mircea Markus
> Assignee: William Burns
> Priority: Minor
> Fix For: 7.2.0.CR1
>
>
> When a transaction knows in advance about the set of keys it needs to read, this cache.getAll(k1,k2,..kn) method can bring a some performance improvement:
> 1. all the keys can be fetched from remote nodes in parallel
> 2. keys that map to the same node can be grouped and fetched in the same RPC request
>
> Note that 1. can be be achieved even at this time by using Cache.getAsync(K) method - that's not as elegant though as it requires the user to write the code the code that waits on the Future objects that are returned.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 12 months