he 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"
Trying to collect dropped/lost messages via dead letters will not work
reliably. For example it can be lost when sending from one node to another
if there is a network problem at the same time.
The only way to know that it arrived is to send acknowledgment message
back, and if no acknowledgement a
ubscribe 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
/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 t
That sounds incredibly strange. Please create an issue with a reproducer
that we can run.
/Patrik
ons 31 okt. 2018 kl. 23:04 skrev :
> have a flow with mapAsync stage. This stage should emits its elements in
> the same order they were pushed. I verified (using log printing) that
> events are pus
; + buffer.toString)
> }
> case a @ Accumulate(_) =>
> println("initial antes de stash " + buffer.toString)
> buffer.stash(a)
> println(&qu
The official status is as that note in documentation says. We want to
harden it and input from you like this is very important. Please share
dumps, logs, failure scenarios, whatever that is not working as expected.
Create issues or continue questions/discussions at discuss.akka.io
Thanks,
/Patrik
s.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...
ce, because I have learned that one can import from
>> stable identifiers (e.g. vals) in Scala. Hence I don’t think changing the
>> docs has the necessary effect.
>>
>> How can a final val be „nulled"? Unsafe? Reflection?
>>
>> Cheers
>> Heiko
>&
/blog/news/2018/03/13/discuss.akka.io-
> announced
>
> *
> >>>>>>>>>>
> >>>>>>>>>> Read the docs: http://akka.io/docs/
> >>>
I’m pretty sure that is just a standard terms of service document, and it’s
absolutely not the reason for changing forum.
/Patrik
sön 8 apr. 2018 kl. 15:46 skrev Peter Corlett :
> On Fri, Apr 06, 2018 at 05:17:17PM +0100, Alan Burlison wrote:
> > On 06/04/18 16:55, Patrik Nordw
> "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
t;>>>>>>>>> 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/grou
Other log messages prefixed with “Cluster Node” would probably tell what’s
going on.
I’d suggest that you move the question to the new forum at
http://discuss.akka.io
/Patrik
mån 2 apr. 2018 kl. 08:05 skrev Grace :
> Hi all,
>
> I was running a cluster of four nodes, one client node and three wo
It should probably be changed to Warning level. PR fixing this would be
welcome.
/Patrik
tis 27 mars 2018 kl. 16:31 skrev Zachary Marois :
> If these are harmless, would ignoring any ERRORs from the
> akka.remote.EndpointWriter class be safe? I definitely worry about hiding
> real errors, but I a
When another node with lower address is added. When there is a network
partition (unreachable).
Most often applications are more interested in using Cluster Singleton, and
that is not the same as leader.
If you have more questions I suggest that you post at the new
http://discuss.akka.io/
/Patri
Hi Eric,
You can setup email notifications as described in
https://discuss.lightbend.com/t/how-to-use-the-discuss-forum-as-a-mailing-list/61
/Patrik
fre 16 mars 2018 kl. 22:01 skrev Eric Swenson :
> Konrad,
>
> Will new topics continue to be pushed to the mailing list as they are
> published on
Can’t you use an async http client instead to avoid the blocking
altogether? E.g. Play WS or Akka HTTP.
/Patrik
lör 10 mars 2018 kl. 22:11 skrev Amit Chavan :
> Hello,
>
> I am redesigning a system that takes in messages on zmq and has to make
> certain decisions and return responses. As the sys
d 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.
>
--
Patrik Nordwall
Akk
u 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@
t 6:09:24 AM UTC-8, Patrik Nordwall wrote:
>>
>> It's because when the actor is stopped some of the fields are cleared
>> (yeah, even though they are vals) to "help" the GC in case something (e.g.
>> an local ActorRef) is still referencing the actor instance.
>
√
>>
> --
> >>>>>>>>>> Read the docs: http://akka.io/docs/
> >>>>>>>>>> Check the FAQ: http://doc.akka.io/docs/akka/
> current/additional/faq.html
> >>>>>>>>>> Search the archives: http
Sounds interesting/strange. For investigation it would be good with debug
logging and verbose-heartbeat-logging.
I think it is config akka.cluster.debug.verbose-heartbeat-logging=on, but
check reference.conf
/Patrik
fre 2 mars 2018 kl. 15:47 skrev Manuel Bernhardt :
> How big is your cluster?
>
fferent that nodes' configurations do
> not need to be checked for compatibility?
>
> Thanks, Fred
>
> On Sat, Feb 24, 2018 at 8:27 PM, Patrik Nordwall
> wrote:
> > It’s only part of the joinSeedNodes process. Perhaps that is missing in
> > docs, and contribution f
It’s only part of the joinSeedNodes process. Perhaps that is missing in
docs, and contribution fixing that is welcome.
/Patrik
lör 24 feb. 2018 kl. 18:13 skrev Frederic :
> Hello all,
>
> I've just done a few tests with the new Configuration Compatibility Check
> and noticed that no compatibility
Behaviors.immutable
-
deferred renamed to setup
-
ctx.spawnAdapter replaced by ctx.messageAdapter and ctx.ask
Credits
For this release we had the help of 36 committers – thank you all very much!
commits added removed
38 9046 3376 Patrik Nordwall
32 8484 242
On Thu, Feb 22, 2018 at 12:34 AM, Alan Burlison
wrote:
> On 21/02/18 19:14, Patrik Nordwall wrote:
>
> Search for serialization-bindings in reference.conf, which you find here:
>> https://doc.akka.io/docs/akka/current/general/configuration.
>> html#listing-of-the-re
rrent/additional/faq.html
>>>>>>>>>>> Search the archives: https://groups.google.com/grou
>>>>>>>>>>> p/akka-user
>>>>>>>>>>>
>>>>>>>>>> --- You received this messag
btw, probably easier to use .runWith(TestSink.probe) in that example, or
.runWith(Sink.seq).futureValue
On Mon, Feb 19, 2018 at 12:12 PM, Patrik Nordwall wrote:
> Doc improvement is welcome. If you add request(1) before the
> expectComplete it’s not undefined, then you are supposed to
might break the
> tests unexpectedly ?
>
> Jakub
>
> On Friday, February 16, 2018 at 9:55:45 PM UTC+1, Patrik Nordwall wrote:
>
>> It is allowed to ”delay” delivery of the complete signal when there is no
>> demand. This behavior is undefined, i.e. some stages deliver it
>
The drawback of first sending everything to one single node would be
“single point of bottleneck” and an extra network hop for many messages.
Even though all frontend nodes might not have exactly the same load
information at the same time that should be fine anyway.
Load based routing is always d
It is allowed to ”delay” delivery of the complete signal when there is no
demand. This behavior is undefined, i.e. some stages deliver it
immediately, some only when demand is requested. This is as expected and in
such test you have to request enough to be sure to get the completed signal.
/Patrik
Thanks for the update Jeremey. Is the availability of this already
mentioned in akka-http documentation? Otherwise I think it would be worth
adding that somewhere. Please open an issue and we can work out the details.
regards,
Patrik
ons 31 jan. 2018 kl. 20:32 skrev Philippe Derome :
> never mind
I think you can do that with Akka’s Coordinated Shutdown
https://doc.akka.io/docs/akka/current/actors.html#coordinated-shutdown
Register your task to one of the phases, instead of using jvm shutdown
hook. Coordinated Shutdown will be triggered by jvm exit.
/Patrik
tis 13 feb. 2018 kl. 12:52 skrev
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.
&g
ocs/
> >>>>>>>>>> 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 subscri
the "external ask" API, but it's
> something to think about.
>
>
> (As an aside, the PR also drew my attention to the fact that I was leaking
> adapters, so that's something...)
>
>
> Tal
>
>
>
> On Sunday, January 28, 2018 at 5:49:53 PM UTC+
e prohibitively high? I'm asking because I was
> considering implementing a similar thing (causal reliable broadcast over
> Cassandra) with dynamic topology to handle the intra-DC netsplit scenario,
> so I'd be glad to hear your thoughts.
>
> Thanks
> Igor
>
>
> On
Hi Tal,
Thanks a lot for taking it for a spin and sharing feedback. Comments
inline...
sön 28 jan. 2018 kl. 14:10 skrev Tal Pressman :
> I finally had the chance to use Akka Typed, and wanted to share my
> experience. So basically, I took a small demo project that was based on
> untyped actors,
The signature is
def asyncWriteMessages(messages: immutable.Seq[AtomicWrite]):
Future[immutable.Seq[Try[Unit]]]
If the future is completed with exception it is the failure case, otherwise
it’s possible to reject individual events as documented:
* The journal can also signal that it rejects indiv
Hi Andrey,
The purpose of ”rejected” is when it’s known that the event was not stored.
Typically something that happens before the data store is called, such as
serialization error. ”failed” is more uncertain. It might have been stored,
it might not. E.g. A timeout of a db call.
For rejected the
good overview of the feature, and more details can be found in the
documentation
<https://developer.lightbend.com/docs/akka-commercial-addons/current/persistence-dc/>
.
--
Patrik Nordwall
Akka Tech Lead
Lightbend <http://www.lightbend.com/> - Reactive apps on the JVM
Twitter: @pa
Difficult to say what it can be without knowing what your code looks like.
I suggest that you try to minimize it and share a reproducer or example.
/Patrik
mån 15 jan. 2018 kl. 15:05 skrev Dmitry Golubets :
> One thing I want to add, is that sometimes there is actually one
> difference that I see
A PersistentActor with a given persistenceId can only be active at one
place (single writer principle). Cluster Sharding will help you with that.
/Patrik
fre 12 jan. 2018 kl. 09:08 skrev Martynas Mickevičius <
martynas.mickevic...@lightbend.com>:
> Hi,
>
> are your Cassandra nodes in one cluster?
sharding-state-store-mode
/Patrik
On Wed, Jan 10, 2018 at 9:10 AM, haghard wrote:
> Do you think that this folder somehow relates to rememberEntities
>
> среда, 10 января 2018 г., 0:13:26 UTC+3 пользователь haghard написал:
>
>> yes
>>
>> среда, 10 января 2018 г.
Are you using Cluster Sharding with rememberEntities?
tis 9 jan. 2018 kl. 21:52 skrev haghard :
> Hello Patrik, after updating on 2.5.8 I see a new folder called ddata.
>
> Thanks
>
> вторник, 9 января 2018 г., 22:52:36 UTC+3 пользователь Patrik Nordwall
> написал:
>>
>
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
Lightbend <http://www.lightbend.com/> - Reactive apps on the JVM
Twit
arch 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
>>> 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+unsub
You can get better throughput by using as many worker actors as cpu cores,
if it is cpu bound. ConsistentHashingPool is one way. I don’t think you
should involve pinned dispatcher.
/Patrik
fre 29 dec. 2017 kl. 08:49 skrev Leon Ma :
> Hi,
>
> I have some general questions regarding ConsistentHashi
Hi Tal,
I think it would be possible to grab the scheduler from internal impl, also
for Typed. Please create an issue.
/Patrik
sön 31 dec. 2017 kl. 13:01 skrev Tal Pressman :
> Hi,
>
> In "regular" untyped Akka, using `ask` only requires an implicit `Timeout`
> whereas the typed version also req
It’s fine (and best) to use one single ActorSystem. For the blocking you
have to use a dedicated dispatcher as described in
https://doc.akka.io/docs/akka/current/dispatchers.html#blocking-needs-careful-management
An ActorSystem can have several dispatchers.
/Patrik
ons 13 dec. 2017 kl. 17:14 skrev
Hi Steffen,
As documented Distribute Data has limitations with regards to data size.
Crucial is to split it up to many top level entries. I’d suggest you try
with 1000-1 top level entries.
Even with delta-CRDTs it must sometimes transfer the full state, meaning
that the message size for that
oglegroups.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
Lightbend <http://www.lightbend.com/> - R
4lDCc/WjVB9fJYDYI/AWA/p1wnqvhQ7WkOGSBhvynPo9J9y_q4ed9FwCLcBGAs/s1600/Untitled%2BDiagram%2B%25282%2529.jpg>
>
>
>
>
>
>
>
>
>
>
> On Saturday, December 16, 2017 at 1:09:42 PM UTC+5:30, √ wrote:
>>
>> Also, is serialization/deserialization incl
r having the cluster client setup a death watch on
> the receptionist?
>
> Fred
>
> Le 16 déc. 2017 16:38, "Patrik Nordwall" a
> écrit :
>
> Sounds like an excellent suggestion and contribution is welcome.
> Thanks, Patrik
> lör 16 dec. 2017 kl. 09:15 skre
Sounds like an excellent suggestion and contribution is welcome.
Thanks, Patrik
lör 16 dec. 2017 kl. 09:15 skrev Frederic :
> Hi all,
>
> The ClusterClient is designed to connect to a single ClusterReceptionist.
> When a cluster node running a receptionist gracefully leaves the cluster
> (i.e., be
What are you interested in? Throughput (msg/s) or latency (us)? Remote or
local? What will the results of the benchmarks be used for?
/Patrik
fre 15 dec. 2017 kl. 12:23 skrev Akka Team :
> I think the floodPipe benchmark may do what you want, commented out but
> you could easily uncomment and run
tis 12 dec. 2017 kl. 20:13 skrev Papelucho Nomas :
> Arnout,
>
>
> Short version: it was akka-streams-kafka 0.16.
>
>
> Long version: I had to update "akka-stream-kafka" from "0.16" -> "0.18".
> To keep things straight updated "kafka-clients" to "0.11.0.1" and
> "scalatest-embedded-kafka" from "0.
rch 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...
ons like isolation of nodes
>
> We are using Opendaylight RAFT consensus cluster built atop Akka.
>
> Regards
> Muthu
>
>
> On Tuesday, 5 December 2017 22:35:05 UTC+5:30, Patrik Nordwall wrote:
>>
>>
>>
>> On Mon, Dec 4, 2017 at 5:32 PM, Muthukumaran
;>
>> Regards
>>
>> Muthu
>>
>>
>>
>>
>>
>>
>>
>> --
> >>>>>>>>>> Read the docs: http://akka.io/docs/
> >>>>>>>>>> Check the FAQ: http://doc.akka.io/docs/akka/
> current/add
nd 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/opt
There are Cluster aware routers if these components are within the same
Akka Cluster.
https://doc.akka.io/docs/akka/current/cluster-usage.html#cluster-aware-routers
/Patrik
lör 2 dec. 2017 kl. 21:02 skrev :
> John,
>
> is *Akka Cluster* supporting load-balancer like HA-Proxy etc. ?, for
> examp
Since these are local messages (in same jvm) you can in practice rely on
that they will be delivered.
Akka has this disclaimer of at-most-once also for local messages since you
might be using a bounded mailbox, or the jvm may crash.
In theory you can setup such subscriptions also with remote acto
quot; 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
d 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://gro
s can talk to each
>>> other directly without using the load balancer.
>>>
>>> -- Robert
>>>
>>> On Thursday, November 30, 2017 at 9:15:03 AM UTC-6, rkuhn wrote:
>>>>
>>>> May I suggest serving the large blobs via a different mechanism
One reason could be that you are sending too large messages.
/Patrik
tors 30 nov. 2017 kl. 15:32 skrev kraythe :
> We are constantly getting messages like this in our logs.
>
> 2017-11-30 14:28:31,181 [WARN ] [PhiAccrualFailureDetector]
> (akka.remote.PhiAccrualFailureDetector@808f8ad) - heartbea
Sending 10 MB messages is indeed recipie for trouble.
I’d suggest to split the 10 MB into 100 smaller messages and collect,
reassembe, them on the receiving side.
Perhaps you are fine with loosing such messages since they are periodically
published again. Otherwise you could use DistributedData t
The implementation is pretty much the same. I wouldn’t be worried about
performance for ask, but tell is in general a better fit for actor to actor
communication.
/Patrik
ons 22 nov. 2017 kl. 07:37 skrev Evgeny Veretennikov <
evg.veretenni...@gmail.com>:
> Classic Akka Untyped docs says:
>
> The
s.
Is the performance still better than using the java-serializer?
>
Yes, way better
> Also I have a lots of messages to Serialize, that's bringing lots of
> boilerplate code :/
>
You can look into a more automatic mapping, such as Kryo.
>
> Am Sonntag, 19. N
Serialization is mentioned at the end of this blog post:
https://akka.io/blog/2017/09/28/typed-cluster
It links to the PingSerializer that illustrates how to use the
ActorRefResolver. In the end the ActorRef is represented as a string in the
proto.
A more comprehensive serializer example that is
Hi Iain,
Many things are missing for testing of Akka Typed, but did you check out:
https://github.com/akka/akka/blob/master/akka-typed-testkit/src/main/scala/akka/typed/testkit/scaladsl/TestProbe.scala
/Patrik
fre 17 nov. 2017 kl. 16:28 skrev Iain Hull :
> Hi,
>
> I am been playing with akka ty
tery with TCP
<https://github.com/akka/akka/pull/23828> as an alternative to Aeron. That
could be a fallback plan if Aeron doesn't fit your needs.
>
> Kind regards,
>
> Merlijn
>
>
>
> Op zondag 12 november 2017 18:25:16 UTC+1 schreef Patrik Nordwall:
>>
&
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
76| 61
>>>>> | 13| 75| 57| 76|
>>>>>
>>>>>
>>>>> Round 1
>>>>>
>>>>> | metric | nginx | akka-http | colossus | finagle
>>>>> | http4s| netty
What about doing it on the read side, that could consume all tagged events.
It could keep track of latest event time for each persistenceId and alert
if deadline exceeded.
/Patrik
lör 11 nov. 2017 kl. 16:52 skrev lutzh :
> Hi mailing list,
>
> I was wondering if anyone had some good ideas about
eate a pull request to provide a function, good idea !
>
> Le samedi 11 novembre 2017 03:35:28 UTC-5, Patrik Nordwall a écrit :
>>
>> You could do that by first replacing the various delimiters with one
>> common, in a map stage. That said, if this is typical framing requiremen
To compile and run tests you use:
sbt test
Perhaps start with the Akka Quickstart to get familiar with the basics:
https://akka.io/try-akka/
/Patrik
tors 9 nov. 2017 kl. 23:40 skrev Nagaraju Ajmeera <
ajmeeranagaraj...@gmail.com>:
> I am a newbie to the akka framework. I would like to understan
You could do that by first replacing the various delimiters with one
common, in a map stage. That said, if this is typical framing requirement
we could perhaps add more power to the framing stage, e.g. a funtion
ByteString => Boolean. That would be a good community contribution.
/Patrik
lör 11 no
Isn’t it thrown from PersistentDeviceActor.scala:183 ?
/Patrik
tis 31 okt. 2017 kl. 20:34 skrev :
> Hi Akka gurus,
>
>1. We use Akka in a production setup
>2. We use Cassandra as a back up for akka-persistence.
>3. One of the PersistentActors throwed NullPointerException during
>
Could it be that the materializer is shutting down?
“Abrupt termination”
/Patrik
tors 2 nov. 2017 kl. 04:29 skrev Christopher Hunt :
> Hi there,
>
> I've got a situation where I observe a postStop being called within my
> custom GraphStage prior to when I'd expect. I'm sure Akka is doing the
> ri
t/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 an
If these actors blocking while waiting for postgres you might see a
starvation issue. All threads in the dispatcher are blocked. You should be
able to confirm this with thread dumps, a profiler, or Lightbend’s Thread
Starvation Detector.
/Patrik
mån 30 okt. 2017 kl. 06:56 skrev :
> Hi Team,
>
> I
time on this!!
>>
>> I'm attaching the code fixed with your comments.
>>
>> Many thanks for your time on this. It was not clear for me that the role
>> was mandatory. I supposed that a non-role means any. My fault.
>>
>> Happy Halloween and thanks agai
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 th
gt; "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/grou
ssing")
case Some(entry) =>
if (entry.name == newName) Left("old and new names are equal")
else Right(Event.EntryRenamed(id, newName))
}
}
}
>
>
> On Friday, October 27, 2017 at 12:09:40 PM UTC+2, Patrik
me: String) extends Event
> }
> }
>
>
>
> So for instance after validating command we already have target state, and
> as we are using the same code for applying event and validating command, we
> don't need to perform it twice, no need in second sanity check after even
On Fri, Oct 20, 2017 at 5:29 PM, Yaroslav Klymko wrote:
>
> On Friday, October 20, 2017 at 4:44:35 PM UTC+2, Patrik Nordwall wrote:
>>
>>
>>
>> On Thu, Oct 19, 2017 at 2:52 PM, Yaroslav Klymko
>> wrote:
>>
>>>
>>>
>>>
>>
On Thu, Oct 19, 2017 at 2:52 PM, Yaroslav Klymko wrote:
>
>
>
> On Thursday, October 19, 2017 at 9:33:59 PM UTC+2, Patrik Nordwall wrote:
>>
>> Invalid events must not be stored, because then the actor will not be
>> able to recover after a restart (later startup).
;>>> >>>>>>>>>> Check the FAQ: http://doc.akka.io/docs/akka/c
>>>> urrent/additional/faq.html
>>>> >>>>>>>>>> Search the archives: https://groups.google.com/grou
>>>> p/akka-user
>>>> ---
ibed 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://group
Wouldn’t it be easier to implement that as an ordinary Actor, instead of a
router?
/Patrik
tis 17 okt. 2017 kl. 08:16 skrev 김태현 :
> Hi,
>
> I created a custom Group Router (see below), which routes messages based
> on the session established on any one of the Routees with fall-back to
> Round-Rob
Might be some misunderstanding of terminology here. The quote from the
documentation is about Distributed Data. In last post I read it as you talk
about an actor tree. Anyway, in distributed Data you would use many
ORCounterMap as top level entries, and each such map would hold a number of
named co
a/akka/persistence/cassandra/query/
> EventsByTagPublisher.scala#L141 but just want to double check it does
> what I assume it does...
>
yes
>
> Regards,
> Lutz
>
>
>
> On Tuesday, 10 October 2017 13:46:11 UTC+2, Patrik Nordwall wrote:
>>
>> Hi Lutz,
>
;>>> 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
If node B is downed and removed from cluster then the coordinator will stop
using B and will allocate shards to other nodes. The coordinator is a
cluster singleton and if that node is removed a new coordinator will be
started elsewhere with same state.
/Patrik
tors 5 okt. 2017 kl. 17:01 skrev Seba
That is currently not supported but you could contribute that feature to
the leveldb plugin. We could use Long.MaxValue as the signal to remove
everything.
/Patrik
fre 6 okt. 2017 kl. 10:44 skrev Ole Hjalmar Herje :
> Hi, is it possible to delete persistent actors completely from the
> persistent
1 - 100 of 2005 matches
Mail list logo
