Re: [akka-user] Re: Node quarantined

This is the latest version of akka for java 7. On Friday, April 29, 2016 at 3:18:55 PM UTC-4, Patrik Nordwall wrote: > > There can be several reasons, but a good start is to use latest Akka > version. > tors 28 apr. 2016 kl. 21:13 skrev Guido Medina >: > >> Hi Ben, >> >> As

Re: [akka-user] Re: Node quarantined

There can be several reasons, but a good start is to use latest Akka version. tors 28 apr. 2016 kl. 21:13 skrev Guido Medina : > Hi Ben, > > As my experience goes Netty 3 doesn't get much love, issues are barely > fixed, > like I mentioned before I'm running my own Netty 3.10.6

Re: [akka-user] Re: Node quarantined

Hi Ben, As my experience goes Netty 3 doesn't get much love, issues are barely fixed, like I mentioned before I'm running my own Netty 3.10.6 built internally, also; 3.10.0 is not even a good version, if you want force your version to 3.10.5.Final until they release 3.10.6.Final which has nice

Re: [akka-user] Re: Node quarantined

I'm following up on this topic after upgrading to akka 2.3.15. I'm reasonably confident that the issue is the resullt of using akka along with another library that causes the netty dependency to be upgraded from 3.9.2.Final to 3.10.0.Final. For now I have removed the dependency on the newer

Re: [akka-user] Re: Node quarantined

I look forward to trying out the new version. Not totally sure it is the same issue I'm seeing this happen on a cluster where no node is being restarted. I shall continue to investigate what has changed on my side, because I wasn't see this before I upgraded other libraries. On Wednesday,

Re: [akka-user] Re: Node quarantined

*Correction:* Set that only for non-seed nodes. On Wednesday, March 23, 2016 at 9:38:44 AM UTC, Guido Medina wrote: > > Hi Benjamin, > > For what I could understand from the issue, this is happening only to > nodes that rejoined > the cluster under the same address (host and port) so I believe

Re: [akka-user] Re: Node quarantined

Hi Benjamin, For what I could understand from the issue, this is happening only to nodes that rejoined the cluster under the same address (host and port) so I believe that setting akka.remote.netty.tcp.port = 0 should solve the problem in the meantime, Cheers, Guido. -- >>

Re: [akka-user] Re: Node quarantined

We have fixed the issue that is noticed as "Error encountered while processing system message acknowledgement buffer: [-1 {}] ack: ACK[6, {}]" https://github.com/akka/akka/pull/20093 It will be released in 2.4.3 and 2.3.15, probably by end of next week. /Patrik tis 22 mars 2016 kl. 23:39 skrev

[akka-user] Re: Node quarantined

Yeah sorry I thought it was related with rolling restart. As for Netty, I'm using a *non-published yet* Netty with the following fixes: https://github.com/netty/netty/issues?q=milestone%3A3.10.6.Final+is%3Aclosed You can just get it from Git and: $ git checkout 3.10 $ mvn versions:set

[akka-user] Re: Node quarantined

Hi Guido, yes I'm aware of the leaving cluster conversation as I started it :-) This is separate issue. I am observing this behavior whilst the cluster seems stable with no nodes being added/removed. I suspect that this issue was first observed when I upgraded a different library that brought

[akka-user] Re: Node quarantined

Hi Benjamin, You have nodes with predefined ports, one thing I have which eliminates that problem for these nodes is that only my seed node(s) have the port set, the rest will just get a dynamic and available port, making it get a different port when you do a rolling restart. I suspect you are

[akka-user] Re: Node quarantined

Hi Benjamin, You have nodes with predefined ports and addresses, one thing I have which eliminates that problem for these nodes is that only my seed node(s) have the port set, the rest will just get a dynamic and available port, making it get a different port when you do a rolling restart. I

[akka-user] Re: Node quarantined

I see the same issue with 2.3.14. On Tuesday, March 22, 2016 at 2:00:15 PM UTC-4, Guido Medina wrote: > > To eliminate noise please update to 2.3.14 which from 2.3.11 has some > cluster fixes, there are also several fixes on Scala 2.11.8 (not related) > > I don't know, I just have the custom of