That is thrown when the ActorSystem has terminated (scheduler stopped).
Perhaps a Play reload?
/Patrik
fre 5 maj 2017 kl. 12:27 skrev Praveen Yadav :
> Forgot to mention, we are using play 2.4.3
>
> Thanks
>
>
> On Friday, May 5, 2017 at 3:41:33 PM UTC+5:30, Praveen Yadav
First, don't use java serialization for performance and security reasons.
Secondly, actor messages should be small (a few 100kB at most). Otherwise
they will prevent other messages to get through, such as cluster heartbeat
messages. Split the large message into smaller messages, or transfer it on
I think that config means that you are adding the self address as the first
entry in the seed-nodes list, and therefore each node joins itself. Read
the documentation on how to join cluster.
/Patrik
fre 5 maj 2017 kl. 20:55 skrev Kilic Ali-Firat :
> I'm running my two
t of closed issues for Akka Typed since 2.5.0 can be found
on the 2.5.99-TYPED-M1 <https://github.com/akka/akka/milestone/114?closed=1>
milestone on github.
--
Patrik Nordwall
Akka Tech Lead
Lightbend <http://www.lightbend.com/> - Reactive apps on the JVM
Twitter: @patriknw
--
>&
nce 2.4.17.
The complete list of closed issues can be found on the 2.4.18
<https://github.com/akka/akka/milestone/105?closed=1> milestone on github.
For this release we had the help of 16 committers – thank you all very much!
commits added removed
15 1669 335 Johan Andrén
t; 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
> >>>
>From a test like that I'd use unique names for top level actors, and if
that is not possible I'd use awaitAssert to retry creating the actor until
the name is free.
/Patrik
tors 27 apr. 2017 kl. 17:19 skrev Konrad Malawski <
konrad.malaw...@lightbend.com>:
> In other words, only the *parent*
How many lines of code would such an backoff supervisor actor be if it only
did exactly the one and only thing that you want?
As Johan suggests inheritance is not the best api from an Akka maintance
perspective, we have strong obligations to keep binary compatibility but
still be able to evolve
/Debug2 objects ?
>
> and yes, definitely missed that logger .
>
> Thanks
>
> On Friday, April 21, 2017 at 1:13:13 PM UTC+3, Patrik Nordwall wrote:
>>
>> Doesn't the first picture indicate that you create many actors that are
>> never stopped?
>
ge 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.
> Visi
eck 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"
That is a simple and good solution. If the entity ids are known you can do
the heartbeating from an actor running on each node, or from a Cluster
Singleton, instead of from the clients.
I know something similar is used in Lagom for keeping the read side
processors alive.
/Patrik
ons 19 apr. 2017
; >>>>>>>>>> Read the docs: http://akka.io/docs/
> >>>>>>>>>> Check the FAQ: http://doc.akka.io/docs/akka/
> current/additional/faq.html
> >>>>>>>>>> Search the archives:
y, April 15, 2017 at 11:28:11 AM UTC-4, Patrik Nordwall wrote:
>
>> The problem is not some wrong translation.
>> Are you sure that the destination actor is running at the given path?
>>
>> You can enable more logging:
>> http://doc.akka.io/docs/akka/2.5/scala/loggin
Which Akka version?
Perhaps you see the issue with serialize-messages=on, which we have an
improvement in progress for https://github.com/akka/akka/pull/22682
Try with serialize-messages=off
/Patrik
lör 15 apr. 2017 kl. 19:16 skrev Ashish Soni :
> Hi All ,
>
> Below is
There is no buffer. Perhaps you send before cluster membership is
established?
/Patrik
fre 14 apr. 2017 kl. 00:17 skrev Alexander Lukyanchikov <
alexanderlukyanchi...@gmail.com>:
> Small observation - messages start deliver to the "processor" node only
> when I send a lot of them (like ~ 20 per
The problem is not some wrong translation.
Are you sure that the destination actor is running at the given path?
You can enable more logging:
http://doc.akka.io/docs/akka/2.5/scala/logging.html#Auxiliary_remote_logging_options
/Patrik
fre 14 apr. 2017 kl. 15:06 skrev Joseph Mansigian <
Yes, that is safe (as long as you subscribe to the local pubsub, and it
doesn't make sense to subscribe to a remote pubsub).
/Patrik
fre 14 apr. 2017 kl. 19:39 skrev Giovanni Alberto Caporaletti <
paradi...@gmail.com>:
> Hi all, a simple question:
> is an actor guaranteed to be forever
sing the remote actor. Looking at
>>> the log, all the information needed is there but how can I access it?
>>>
>>
>> I think you can subscribe to association errors using
>> http://doc.akka.io/docs/akka/current/scala/remoting.html#Remote_Events
>>
>>
If this is missing or unclear in docs it would be great with an improvement
PR.
fre 14 apr. 2017 kl. 17:54 skrev ahjohannessen :
> I am correct, try it out. We do something like this:
>
> def processEvents(events: Seq[DomainEvent], cm: CommandMessage)
>
What persistence (journal/snapshot) plugin do you use?
ons 12 apr. 2017 kl. 06:43 skrev Arnout Engelen <
arnout.enge...@lightbend.com>:
> Hello Serg,
>
> '2' is actually working as designed: if the actor does not crash, the
> shard has no way of knowing whether to expect a response (and when).
>
system1 doesn't crash, that is just a harmless log message, or do you see
anything that actually doesn't work in system1 after that?
/Patrik
sön 9 apr. 2017 kl. 13:25 skrev David :
> Hello,
>
> I am using Akka remote 2.4.17 with Scala 2.12.1
>
> I have two actor systems:
Such parameters must be read from config, i.e. you don't need different
mailbox classes, but have to have different configs for each one.
/Patrik
sön 26 mars 2017 kl. 08:50 skrev Sihan Li :
> Hi group,
>
> I have implemented a customized mailbox following this official
Looks like you are still mixing Akka 2.3 and 2.4. That is not possible when
using Distributed PubSub. It was experimental in contrib in 2.3, and then
moved to cluster-tools in 2.4.
Note: Unimplemented deserialization of message with manifest
awaitAssert retries the block until it doesn't throw (or timeout)
/Patrik
fre 31 mars 2017 kl. 15:50 skrev Kilic Ali-Firat :
> Hi Akka Team,
>
> It's again me about the multi-nodes test that I'm doing to validate my
> cluster. I solve my issues about Master-Worker
1) resume supervisor strategy
2) Make receive final in the general EndpointActor and impl the
try-catch-reply there, and delegate the actual message processing to an
abstract method. That breaks down if using become, but otherwise it's fine.
/Patrik
lör 1 apr. 2017 kl. 21:17 skrev kraythe
ot; 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-
> 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:
gt;>>>>>>> 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-us
On Tuesday, 4 April 2017 16:09:49 UTC+5:30, Patrik Nordwall wrote:
>>
>> No, there is no majority decision here. Perhaps you don't join the right
>> node. You should have both in seed-nodes and in same order. It should be
>> clear from info level logging what is going on.
>
previous incarnation.
>
>
> On Tuesday, 4 April 2017 15:17:45 UTC+5:30, Patrik Nordwall wrote:
>
> One way of downing is to join again with same host:port. That will trigger
> downing of previous incarnation and when removal is done the new
> incarnation can join by trying to join
One way of downing is to join again with same host:port. That will trigger
downing of previous incarnation and when removal is done the new
incarnation can join by trying to join again. The seed-nodes joining will
retry the joining automatically.
However, sooner or later you will need a real
Fork Join Pool will not pre-allocate threads. It will also stop threads
when they are not used. That configuration is correct, it will allocate up
to 50 threads (possibly more if you use some special Scala constructs).
If the reason for 50 threads is that you are doing blocking I strongly
advice
This is correct. Is this a suggestion for documentation improvement? PR is
welcome.
/Patrik
mån 3 apr. 2017 kl. 18:59 skrev Justin du coeur :
> Hmm. Could be. I suspect they'd welcome a PR to that effect...
>
> On Mon, Apr 3, 2017 at 11:56 AM, Mushtaq Ahmed
You must use the same version for all Akka artifacts, e.g. 2.12_2.4.17 for
everything. Cluster-metrics exists for that version.
Akka 2.4.x is released for Scala 2.11 and 2.12 but you have to pick one and
don't mix.
/Patrik
mån 3 apr. 2017 kl. 20:33 skrev Mark McShane :
> I'm
There is a scheduled timeout in PersistentActor. That might be the reason
and you could try increase the timeout (look in reference.conf in
akka-persistence).
In general, it can be difficult to do breakpoint debugging with actors,
since so many things may happen concurrently and might depend on
requests. This settings is on remote.netty.tcp.
>
> Measuring the time delay between sending and receiving the message helped
> up to figure out and optimize it.
>
> Regards,
> Jasim
>
> On Saturday, March 25, 2017 at 7:34:16 PM UTC+7, Patrik Nordwall wrote:
>>
>>
n updating from Akka 2.4.
Credits
For this release (since 2.5.0.RC1) we had the help of 12 committers – thank
you all very much!
commits added removed
5 22 37 Sebastian Harko
4272 59 Patrik Nordwall
3802 256 Jan `gosubpl` Pustelnik
2 204
;>>> Unmesh
>>>>
>>> --
> >>>>>>>>>> Read the docs: http://akka.io/docs/
> >>>>>>>>>> Check the FAQ: http://doc.akka.io/docs/akka/
> current/additional/faq.html
> >>>>>>>>>> Search
ing local to local it's
> not same jvm. I run two jvm apps and connect each other with remoting (on
> localhost)
>
> I was thinking serialisation still is happening in this case or am I wrong?
>
> Cheers,
> Fatih
>
> On Sat, Mar 25, 2017 at 5:59 PM, Patrik Nordwall
batches I put some
> delay (500ms).
>
> Cheers,
> Fatih
>
> 24 Mart 2017 Cuma 23:03:09 UTC+7 tarihinde Patrik Nordwall yazdı:
>
> 256 req/s doesn't sound like much.
>
> What serialization do you use. Could that be the bottleneck?
>
> What kind of flow control
message to one of his routees mailbox
> only?
>
> Thanks,
> Marco
>
>
> On Sunday, March 19, 2017 at 1:30:52 PM UTC, Patrik Nordwall wrote:
>
> Not sure I understand what you mean. Each message is routed to only one
> routee. That you see only 2 routees in use might be t
oogle 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 http
>>>>> 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
&
a good practice ?*
>
> Le lundi 13 mars 2017 15:50:44 UTC+1, Patrik Nordwall a écrit :
>
>
>
> On Mon, Mar 13, 2017 at 1:13 PM, Ronan Michaux <ronan@gmail.com>
> wrote:
>
> Thank you !
>
> Multi-Jvm Akka-Cluster tests are hard to understand.
>
>
Not sure I understand what you mean. Each message is routed to only one
routee. That you see only 2 routees in use might be that there is not much
load and by chance it happens to use only two of them.
/Patrik
ons 15 mars 2017 kl. 16:57 skrev :
> I'm trying to use
Perhaps use mapAsync and complete the future after the backoff timeout?
http://doc.akka.io/docs/akka/2.4/scala/futures.html#After
/Patrik
tors 16 mars 2017 kl. 10:32 skrev Vishal John :
>
> Hello all,
>
>
> I have a application which reads a stream of "request" messages,
Isn't the difference that with Kryo you don't have to write the tedious
mapping code between the domain classes and the protobuf classes?
For the Akka internal classes we see that mapping as an advantage because
it gives us full control but I can understand that in a large system that
code can be
You could leave it running without downing, but you must still have a
strategy for downing/removing crashed or stopped nodes. Also note that a
crash, cpu overload or a long GC are indistinguishable from a network
partition.
/Patrik
fre 17 mars 2017 kl. 19:24 skrev kant kodali
Could it be the null (Void)? Try some other element type there.
fre 17 mars 2017 kl. 19:00 skrev Guofeng Zhang :
> Hi,
>
> Here is my code:
>
> Source missedProductSource =
> Source.from(missedProducts) ;
> final RunnableGraph missedTo =
>
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...@googlegrou
What persistenceIds would you like to use in the end?
Based on a counter? PO-1, PO-2, ... increasing for each routee?
Would be strange in a long running system when worker nodes are added and
removed over time.
Why not use Cluster Sharding instead? Wouldn't it be more natural to have a
separate
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
= ...
>
>
>
They have gown organically and I agree that a cleanup and extraction of
common utilities would be desired. Perhaps even create a specific cluster
testkit. Help with this from the community would be great.
/Patrik
>
>
> Le samedi 11 mars 2017 15:50:28 UTC+1, Patrik Nordwall a
Tal describes it very well. In the future we'll hopefully be able to get
notifications from Cassandra when something has changed instead of using
the primitive poll approach. There is already Change Data Capture (CDC) in
Cassandra but it's an extremely low level api so far. Improvement
suggestions
quot;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
up.
> 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
Hi Alifirat,
Have you tried to use Group router instead? Then you would not have the
problem with remote deployment and serializable parameters.
If you need something even more dynamic you can use Distributed PubSub as a
router.
Regards,
Patrik
fre 10 mars 2017 kl. 23:33 skrev Kilic Ali-Firat
e another actor (at least one) on each
> node that is always alive and subscribes to pubsub and delegates to the
> ShardRegion.
>
> So no straightforward way to broadcast to all instances of an aggregate?
>
>
> On Thu, Mar 9, 2017 at 10:52 PM, Patrik Nordwall
opagated ?
>
> Cheers,
> Francesco
>
> --
> >>>>>>>>>> Read the docs: http://akka.io/docs/
> >>>>>>>>>> Check the FAQ: http://doc.akka.io/docs/akka/
> current/additional/faq.html
> >>>>>>&
uot; 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 op
cribe.
>> To unsubscribe from this group and all its topics, 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.
>> Fo
>>>>> 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
> ---
s/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 fr
p/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,
Hi JM,
You are throwing out some insulting comments that I will not accept. Can
you instead explain what you are having trouble with in a constructive way
and I'm sure someone will try to help or understand the need for
improvements.
Regards,
Patrik
tis 28 feb. 2017 kl. 10:18 skrev Jun Ma
Well, as the error message says you must make sure that the native libs are
in the directory specified by java.library.path (google to see how to do
that). But I'm not sure, because we run tests without specifying such path.
It could also be that the directory name contains spaces. Recipe for
I'm surprised that you say that it works with 2 ActorSystem and not with 1.
I would expect the problem to be opposite.
Passing an ActorRef owned by one ActorSystem to the other like you do in
your RunWithSeparateActorSystem can be problematic. Instead you should
acquire the ref with
You should use the BackoffSupervisor to handle such thing. Immediate
restart is typically not desired in case of persist failures.
/Patrik
fre 24 feb. 2017 kl. 10:42 skrev Andrey Onistchuk :
> Hello, guys!
>
> Recently I've came across the situation when my persisted cluster
5-M2
<https://github.com/akka/akka/milestone/104?closed=1> milestone on github.
For this release we had the help of 35 contributors – thank you all very
much!
Credits:
commits added removed
23 5676 2076 Patrik Nordwall
12 1547 862 Johan Andrén
10162 55 Johannes Rud
er
> ---
> 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 emai
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/g
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.
>
--
Patrik Nordwall
Akka Tech Lead
Lightben
/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...@googleg
DistributedData replicates everything to all nodes, so that can be the
reason. You have to use cluster node roles there also.
/Patrik
tis 21 feb. 2017 kl. 22:16 skrev Steve Winfield <
mail.stevewinfi...@gmail.com>:
> Well, I'm using Akka Distributed Data on both the player and room service
>
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.
>
--
bscribe 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://gr
I mean, if you change configuration to akka.actor.allow-java-
serialization=off
On Thu, Feb 16, 2017 at 11:46 AM, Patrik Nordwall <patrik.nordw...@gmail.com
> wrote:
> We have not changed any defaults in 2.4.17, i.e. it is wire compatible
> with 2.4.16. It will not be wire compa
t 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
> >>>>>>>>
gt;>>>>>>>> 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 ema
cribe 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 http
roups
> "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/gro
many you'd use as an
> experienced akka developper
>
> On Saturday, February 11, 2017 at 2:37:47 PM UTC-5, Patrik Nordwall wrote:
>>
>> There is no major disadvantage of having many seed nodes. It will try to
>> send an message to all of them at startup so keepin
Might be because of hostname=0.0.0.0
Try with a specific ip address.
tors 9 feb. 2017 kl. 15:03 skrev :
> Hi Gang,
>
> disassociation usually means some kind of connection error. Unfortunately,
> akka currently doesn't say anything about why a connection was
There is no major disadvantage of having many seed nodes. It will try to
send an message to all of them at startup so keeping it <= 10 might make
sense but I think it will work fine with 100 also (but maybe not 1000).
Seed nodes are only used in the joining process, otherwise they are equal
to
were closed since 2.4.16.
The complete list of closed issues can be found on the 2.4.17
<https://github.com/akka/akka/milestone/101?closed=1> milestones on github.
For this release we had the help of 9 committers – thank you all very much!
Credits:
commits added removed
7
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.
> F
re 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 htt
e 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...@go
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
rsistence id should be unique across all the shard regions. My question
>>>> is would it better to keep the same programming model with/without
>>>> persistence? What's the reason not just to have persistence id only unique
>>>> within the context of a shard regio
; On Tuesday, February 7, 2017 at 1:26:45 AM UTC-8, Patrik Nordwall wrote:
>>
>> How have you defined the persistenceId in ActorA and ActorB? It must be
>> unique for each persistent actor instance.
>>
>> On Tue, Feb 7, 2017 at 8:39 AM, Qing Zheng <qzhe...
onal/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 em
quot;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-u
a/c
>>> urrent/additional/faq.html
>>> >>>>>>>>>> Search the archives: https://groups.google.com/grou
>>> p/akka-user
>>> ---
>>> You received this message because you are subscribed to the Google
>>> Groups "Akka User Lis
age 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@googl
You mean rolling upgrade? Stop a few nodes add new nodes, stop some more,
and so on?
It's possible with Cluster.leave and such in Akka 2.4 but we have done
major improvements in this area for upcoming 2.5. You can try 2.5-M1.
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@googlegrou
s: https://groups.google.com/grou
>>>>>>>>>>> p/akka-user
>>>>>>>>>>>
>>>>>>>>>> --- You received this message because you are subscribed to the
> Google Groups "Akka User List" group.
> To unsu
Hopefully we can have a release candidate of 2.5.0 out within a month. The
more people that help out with the remaining tasks the quicker we can get
it done. See issues on github milestone 2.5.0. We can also release another
milestone if needed.
/Patrik
tors 2 feb. 2017 kl. 06:07 skrev Vadim
201 - 300 of 1676 matches
Mail list logo