Hi Rafał,
- sink requests data from you
> - OutletHandler.onPull is invoked on the outlet where the sink is
> connected to
> - you propagate demand outstream by calling pull on any (or all) of your
> Inlets, depending on your logic
> - eventually data becomes available upstream
> -
Yes, a specific entity must have its own stabe persistenceId, which is
unique in the whole system, across the cluster, across entities of
different types.
(Well you can technically use different journal plugins, but let's not
complicate the picture)
mån 24 okt. 2016 kl. 19:33 skrev Ajmal Babu
On Mon, Oct 24, 2016 at 1:33 PM, Ajmal Babu wrote:
> Thanks Patrik, I would change it to the example you mentioned without the
> parent. The uniqueness is still only guaranteed to be within a node. For
> any reason if a restart happens for the actor then the id value will be
Patrik, I take that back it is unique across different incarnation, thanks
for the help.
On Monday, October 24, 2016 at 12:33:16 PM UTC-5, Ajmal Babu wrote:
>
> Thanks Patrik, I would change it to the example you mentioned without the
> parent. The uniqueness is still only guaranteed to be
Hi,
I'm interested in your experiences with trimming Akka persistence journal
in Cassandra. We would generate a fairly large amount of journal data (up
to 2TB or so per month), so we'd like to keep only 2 weeks' worth of data
in Cassandra and archive older data in HDFS.
Is this a
Hi guys,
I'm recently studying the source code of akka-cluster and there's something
that I really cannot understand.
Actually, I was trying to reproduce what akka-cluster document said "If
system messages cannot be delivered to a node it will be quarantined and
then it cannot come back from
It must be unique. I'd recommend something like this
http://doc.akka.io/docs/akka/2.4/scala/cluster-sharding.html#An_Example
instead of complicating it with parent.
I think the template needs an update.
/Patrik
mån 24 okt. 2016 kl. 16:41 skrev Ajmal Babu :
> What is the
What is the right way to define persistenceId in AKKA persistence with
cluster sharding? The activator example provides the below option to create
a persistenceId and I like this option (explained later).
override def persistenceId: String = self.path.parent.name + "-" +
self.path.name
That explains it. Serializer 9 is DistributedPubSubMessageSerializer
Serialization errors are not transient (that is changed in new remoting
Artery). See this ticket for discussion
https://github.com/akka/akka/issues/20641
In your case you have not included the distribute-data jar in the