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
d. UID is now quarantined and all
messages to this UID will be delivered to dead letters. Remote actorsystem
must be restarted to recover from this situation.
Is there anything abnormal in the logs?
Regards,
Ben
On Wednesday, March 23, 2016 at 9:33:02 AM UTC-4, Benjamin Black wrote:
>
pPoms=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 star
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
have the custom of keeping my libs up to date.
>
> HTH,
>
> Guido.
>
> On Tuesday, March 22, 2016 at 5:34:23 PM UTC, Benjamin Black wrote:
>>
>> Hello,
>>
>> I'm trying to understand the cause of nodes being quarantined and
>> possible solutions to fixi
se only 2 statuses, the draw back is that it will only have to wait
>> for a longer time to react.
>>
>> HTH,
>>
>> Guido.
>>
>> On Thursday, March 17, 2016 at 6:07:48 PM UTC, Benjamin Black wrote:
>>>
>>> Hello,
>>>
>>>
Hello,
I'm adding logic to our service so that when a node is being restarted it
gracefully leaves the cluster using cluster.leave(cluster.selfAddress). In
the cluster specification doc it states:
If a node is unreachable then gossip convergence is not possible and
therefore any leader
I am running a 24 node cluster that is roughly split into two roles:
frontend and backend. There is a streamer actor on the frontend node
talking to a tracker actor on the backend node. There can be many streamer
actors on several frontend nodes talking to one tracker actor. It would
seem that
.
/Patrik
1 jul 2014 kl. 19:57 skrev Benjamin Black benbl...@gmail.com
javascript::
I have a cluster of 15 nodes/boxes. I start the nodes roughly at the same
time. One of the nodes is behaving oddly and continually logging Ignoring
received gossip intended for someone else. However
AM UTC-4, Patrik Nordwall wrote:
On Wed, Jul 2, 2014 at 12:21 AM, Benjamin Black benbl...@gmail.com
javascript: wrote:
I upgraded to Akka 2.3.4 (scala 2.10), but still seeing the same issue.
When I log Cluster(system).selfUniqueAddress I get something
like UniqueAddress(akka.tcp
I have a cluster of 15 nodes/boxes. I start the nodes roughly at the same
time. One of the nodes is behaving oddly and continually logging Ignoring
received gossip intended for someone else. However, the node does seem to
work for a while before being being dropped from the cluster. Basically
I'm creating an application that HTTP streams data that is read from Kafka.
A client can create multiple connections, with the data being evenly
balanced between the connections. I'm using Spray 1.3.1 to handle the HTTP
streaming and Akka 2.3.0. Each client connection creates a streamer actor
:
Hi Benjamin,
your question is hypothetical and without the code and config etc it's
impossible to make a qualified answer.
What does your JVM monitoring tell you?
On Wed, Apr 16, 2014 at 7:47 PM, Benjamin Black
benbl...@gmail.comjavascript:
wrote:
I'm creating an application
13 matches
Mail list logo