Hi,
On Wed, Apr 29, 2015 at 7:34 PM, Zhuchen Wang zcx.w...@gmail.com wrote:
Hi Endre,
I didn't understand There is no system message traffic between two Akka
systems by default, to have a system send system messages to another you
either need to use remote deployment or deathwatch on remote
Hi Endre,
I didn't understand There is no system message traffic between two Akka
systems by default, to have a system send system messages to another you
either need to use remote deployment or deathwatch on remote actors very
well.
Does remote deployment means create actors on any remote
On Fri, Jan 23, 2015 at 9:09 PM, Caoyuan dcaoy...@gmail.com wrote:
On Fri, Jan 23, 2015 at 7:06 PM, Patrik Nordwall
patrik.nordw...@gmail.com wrote:
On Fri, Jan 23, 2015 at 10:12 AM, Caoyuan dcaoy...@gmail.com wrote:
As per our experience on spray-socketio project, too many remote
Hi Johannes,
On Fri, Jan 23, 2015 at 8:39 AM, Johannes Berg jberg...@gmail.com wrote:
Thanks for the answers, this really explains a lot. I will go back to my
abyss and rethink some things. See below some answers/comments.
On Thursday, January 22, 2015 at 6:31:01 PM UTC+2, drewhk wrote:
Hi
No problem, I've created an issue in regards to the documentation here:
https://github.com/akka/akka/issues/16717
On Friday, January 23, 2015 at 3:15:03 PM UTC+2, Patrik Nordwall wrote:
Johannes, I think you have some very good points regarding the
documentation. Would you mind creating an
23 jan 2015 kl. 08:39 skrev Johannes Berg jberg...@gmail.com:
Thanks for the answers, this really explains a lot. I will go back to my
abyss and rethink some things. See below some answers/comments.
On Thursday, January 22, 2015 at 6:31:01 PM UTC+2, drewhk wrote:
Hi Johannes,
On Thu,
As per our experience on spray-socketio project, too many remote actor
watching will cause the cluster quarantined very quickly.
The default heartbeat interval for remote watching is:
akka.remote {
watch-failure-detector {
heartbeat-interval = 1 s
threshold = 10.0
Did you forget a NOT there? Did you mean No, the number of heartbeat
messages per seconds are NOT influenced by how many actors you watch.?
Increasing akka.remote.system-message-buffer-size to 1 did solve the
problem for the load I'm pushing at the system now.
On Friday, January 23, 2015
On Fri, Jan 23, 2015 at 12:34 PM, Johannes Berg jberg...@gmail.com wrote:
Did you forget a NOT there? Did you mean No, the number of heartbeat
messages per seconds are NOT influenced by how many actors you watch.?
Indeed, thanks!
Increasing akka.remote.system-message-buffer-size to 1
On Fri, Jan 23, 2015 at 10:12 AM, Caoyuan dcaoy...@gmail.com wrote:
As per our experience on spray-socketio project, too many remote actor
watching will cause the cluster quarantined very quickly.
The default heartbeat interval for remote watching is:
akka.remote {
Endre, could it be due to pending-to-send system message overflow?
On Thu, Jan 22, 2015 at 11:45 AM, Johannes Berg jberg...@gmail.com wrote:
Okay, I increased the load further and now I see the same problem again.
It seems to just have gotten a bit better in that it doesn't happen as
fast,
Without detailed logs I cannot say. If there would be a system message
buffer overflow then it would cry loudly in the logs. Also it says that an
unreachable node is being removed, so there should be events happening
before unreachability. This might be something completely else. The full
config
If it's quarantined it will be removed from cluster. Please include the log
entry that says that it is quarantined, if any.
/Patrik
22 jan 2015 kl. 14:56 skrev Viktor Klang viktor.kl...@gmail.com:
Endre, could it be due to pending-to-send system message overflow?
On Thu, Jan 22, 2015 at
Okay, I increased the load further and now I see the same problem again. It
seems to just have gotten a bit better in that it doesn't happen as fast,
but with enough load it happens.
To re-iterate, I have Akka 2.3.9 on all (8) nodes and
auto-down-unreachable-after = off on all nodes and I
I will try that but it seems that will only help to a certain point and
when I push the load further it will hit it again.
I hit this within a minute after I put on the load which is a bit annoying
to me. I'm fine with it becoming unreachable as long as I can get it back
to reachable when it
Hi Johannes,
On Thu, Jan 22, 2015 at 4:53 PM, Johannes Berg jberg...@gmail.com wrote:
I will try that but it seems that will only help to a certain point and
when I push the load further it will hit it again.
There is no system message traffic between two Akka systems by default, to
have a
Thanks for the tip for what to look for, my logs are huge so it's a bit of
a jungle. Anyway I found this:
10:34:23.701UTC ERROR[system-akka.actor.default-dispatcher-2] Remoting -
Association to [akka.tcp://system@ip2:port2] with UID [-1637388952]
irrecoverably failed. Quarantining address.
You can try to increase akka.remote.system-message-buffer-size config
setting. Default is 1000.
/Patrik
On Thu, Jan 22, 2015 at 3:41 PM, Johannes Berg jberg...@gmail.com wrote:
Thanks for the tip for what to look for, my logs are huge so it's a bit of
a jungle. Anyway I found this:
Thanks for the answers, this really explains a lot. I will go back to my
abyss and rethink some things. See below some answers/comments.
On Thursday, January 22, 2015 at 6:31:01 PM UTC+2, drewhk wrote:
Hi Johannes,
On Thu, Jan 22, 2015 at 4:53 PM, Johannes Berg jber...@gmail.com
Hi Johannes,
See the milestone here:
https://github.com/akka/akka/issues?q=milestone%3A2.3.9+is%3Aclosed
The tickets cross reference the PRs, too, so you can look at the code
changes. The issue that probably hit you is
https://github.com/akka/akka/issues/16623 which manifested as system
message
Upgrading to 2.3.9 does indeed seem to solve my problem. At least I haven't
experienced them yet.
Now I'm curious what the fixes were, is there somewhere a change summary
between versions or where is it listed what bugs have been fixed in which
versions?
On Wednesday, January 21, 2015 at
Hi Johannes,
see the news item: http://akka.io/news/2015/01/19/akka-2.3.9-released.html
On Wed, Jan 21, 2015 at 4:47 PM, Johannes Berg jberg...@gmail.com wrote:
Upgrading to 2.3.9 does indeed seem to solve my problem. At least I
haven't experienced them yet.
Now I'm curious what the fixes
Hi Johannes,
We just released 2.3.9 with important bugfixes. I recommend to update and
see if the problem is still persisting.
-Endre
On Wed, Jan 21, 2015 at 10:29 AM, Johannes Berg jberg...@gmail.com wrote:
Many connections seem to be formed in the case when the node has been
marked down
Many connections seem to be formed in the case when the node has been
marked down for unreachability even though it's still alive and it tries to
connect back into the cluster. The removed node prints:
Address is now gated for 5000 ms, all messages to this address will be
delivered to dead
Hi Johannes,
On 9 December 2014 at 15:29:53, Johannes Berg (jberg...@gmail.com) wrote:
Hi! I'm doing some load tests in our system and getting problems that some of
my nodes are marked as unreachable even though the processes are up. I'm seeing
it going a few times from reachable to
Hi! I'm doing some load tests in our system and getting problems that some
of my nodes are marked as unreachable even though the processes are up. I'm
seeing it going a few times from reachable to unreachable and back a few
times before staying unreachable saying connection gated for 5000ms and
26 matches
Mail list logo
