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, March 23, 2016 at 2:08:10 AM UTC-4, Patrik Nordwall wrote:
>
> 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 Guido Medina <oxy...@gmail.com
> <javascript:>>:
>
>> 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 -DnewVersion=3.10.6.Final -DgenerateBackupPoms=false
>> $ mvn clean install
>>
>> And see if your problem goes away,
>>
>> Guido.
>>
>> On Tuesday, March 22, 2016 at 10:27:26 PM UTC, Benjamin Black wrote:
>>>
>>> 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
>>> in a new version of the netty library.
>>>
>>> On Tuesday, March 22, 2016 at 6:23:14 PM UTC-4, Guido Medina wrote:
>>>>
>>>> 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 doing a rolling restart right? so you need to wait
>>>> for that node with that address to completely leave the cluster (I'm also
>>>> doing that),
>>>> basically you terminate your system when you receive the message
>>>> *MemberRemoved* for *_self_* address.
>>>>
>>>> I think I saw a discussion related to quarantine nodes when they are
>>>> re-joining using the same address, not sure if here or if it is an actual
>>>> Git ticket.
>>>>
>>>> HTH,
>>>>
>>>> Guido.
>>>>
>>> --
>> >>>>>>>>>> Read the docs: http://akka.io/docs/
>> >>>>>>>>>> Check the FAQ:
>> http://doc.akka.io/docs/akka/current/additional/faq.html
>> >>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "Akka User List" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to akka-user+...@googlegroups.com <javascript:>.
>> To post to this group, send email to akka...@googlegroups.com
>> <javascript:>.
>> Visit this group at https://groups.google.com/group/akka-user.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
--
>>>>>>>>>> Read the docs: http://akka.io/docs/
>>>>>>>>>> Check the FAQ:
>>>>>>>>>> http://doc.akka.io/docs/akka/current/additional/faq.html
>>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user
---
You received this message because you are subscribed to the Google Groups "Akka
User List" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to akka-user+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at https://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.
