There is a config setting for the 5 seconds timeout, you can try to
increase it.
sön 23 okt. 2016 kl. 16:18 skrev Andrew James Ramirez <
andrewjamesrami...@gmail.com>:
> Try doing
>
> sbt clean update compile
>
>
>
>
> On Thursday, October 20, 2016 at 11:52:48 PM UTC+8, Gerard Vico wrote:
>
>
Hi Philippe,
You can use the cluster node role to use pub-sub on a subset of nodes. You
have to start the extension on all nodes with the given role.
I would be interested in taking a look at the logs from such a "crash". I
would expect that messages would be dropped, but nothing more. I would
ial FSMState where I would
> check whether the persistent state is empty or it was recovered and act on
> that.
>
> Cool, thanks a lot Patrik !
>
>
>
> On Saturday, October 15, 2016 at 8:14:22 AM UTC+2, Patrik Nordwall wrote:
>
> I'm not sure I understand. You wan
I'm not sure I understand. You want to read the old data if the persistent
actor doesn't have any events of its own?
You can check the state when you get RecoveryCompleted. You can also count
the events/snapshot in receiveRecover and act on that when
RecoveryCompleted.
/Patrik
fre 14 okt. 2016
ssing of current message.
>
> On Thu, 13 Oct 2016, 08:01 Patrik Nordwall, <patrik.nordw...@gmail.com>
> wrote:
>
>> The actor's name and persistenceId doesn't have to be the same, but if
>> you need that you must wait until it has been terminated befor
criber-" + self.path.name
>
> On Wed, Oct 12, 2016 at 9:59 PM, Patrik Nordwall <
> patrik.nordw...@gmail.com> wrote:
>
>> You can stop it and start a new actor with the same persistenceId.
>> /Patrik
>> tors 13 okt. 2016 kl. 06:33 skrev Richard
You can stop it and start a new actor with the same persistenceId.
/Patrik
tors 13 okt. 2016 kl. 06:33 skrev Richard Rodseth :
> I've been able to test recovery by using the in-memory journal and sending
> a "bomb" message to the actor, which is handled by throwing an
ply :). If I were not to support rejections, that would
> imply that if a serialization error occurs i would simply fail the entire
> Future correct?
>
>
> yes, right
>
>
> Gapless sequence numbers does indeed sound like a worthy consideration.
>
> Thanks Again,
> Ian Grima
> an email to akka-user+...@googlegroups.com.
>>> To post to this group, send email to akka...@googlegroups.com.
>>> Visit this group at https://groups.google.com/group/akka-user.
>>> For more options, visit https://groups.google.com/d/optout.
>>&g
e numbers does indeed sound like a worthy consideration.
>
> Thanks Again,
> Ian Grima
>
> On Tuesday, 11 October 2016 12:21:38 UTC+2, Patrik Nordwall wrote:
>>
>>
>>
>> On Tue, Oct 11, 2016 at 11:24 AM, Ian Grima <iang...@gmail.com> wrote:
>>
&
> Thanks,
>> Ian Grima
>>
>>
>>
>>
>>
>> --
> >>>>>>>>>> Read the docs: http://akka.io/docs/
> >>>>>>>>>> Check the FAQ: http://doc.akka.io/docs/akka/
> current/additional/faq.html
> >>>
cr...@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.
>
> --
> >>>>>>>>>> Read the docs: htt
It is expected that it detects crashed/stopped nodes as unreachable. When
unreachable have been downed and removed the cluster canmove joining nodes
to Up. I'm not sure I understand the question/problem.
Also, don't change heartbeat-interval. That will not make anything better.
You use noSender in ActorA when sending START. Use self instead.
/Patrik
tors 29 sep. 2016 kl. 19:20 skrev :
> On Wednesday, September 28, 2016 at 1:55:42 PM UTC-7, que...@gmail.com
> wrote:
>>
>> I have one actor that sends a message to another actor. There is a
>> message
You find most of the answers here:
http://doc.akka.io/docs/akka/2.4/intro/deployment-scenarios.html
It will be removed in Akka 2.5, unkown release date.
/Patrik
tors 29 sep. 2016 kl. 22:18 skrev Joseph Mansigian <
joseph.c.mansig...@gmail.com>:
>
> I read that the Microkernal was going away.
On Linux you can use taskset to pin the jmv process to specific cores.
fre 30 sep. 2016 kl. 19:56 skrev Konrad Malawski <
konrad.malaw...@lightbend.com>:
> That's what containers are for though.
> Run your jvm in a container and restrict resources available to that one
>
> On 30 Sep 2016 19:48,
fixing the
problem.
--
Patrik Nordwall
Akka Tech Lead
Lightbend <http://www.lightbend.com/> - Reactive apps on the JVM
Twitter: @patriknw
--
>>>>>>>>>> Read the docs: http://akka.io/docs/
>>>>>>>>>> Check the F
uchaAdm> who
contributed to Artery and Roland Kuhn <https://github.com/rkuhn> who
contributed to Akka Typed.
Credits:
commits added removed
142 224456850 Patrik Nordwall
232573 Johan Andrén
20 11067 807 Endre Sándor Varga
1149781651 Konrad Malaws
There is the API cluster.joinSeedNodes if you don't want to use config. See
docs for details.
/Patrik
lör 24 sep. 2016 kl. 11:43 skrev :
> If all nodes in cluster is normal node, none is seed.
> How to set one of nodes as seed please?
> I can't do this, no new node can
Take a look at MergeHub. It's rather new.
http://doc.akka.io/docs/akka/2.4/scala/stream/stream-dynamic.html
/Patrik
lör 24 sep. 2016 kl. 00:53 skrev oleksiys :
> Hi guys,
>
> I need to merge mutliple sources Seq[Source[A, Mat]] and as an output get
> something like Source[A,
It's fine to create more than one in the same jvm. It can be useful for
tests. Be careful to not pass ActorRef instances in a way that would not be
possible if the ActorSystems were in different jvms. Only pass them with
messages. Locate them initially with actorSelection.
/Patrik
ons 21 sep.
For Lagom I wrote json serializer that is using Jackson. You can look at it
for inspiration. It's stored in Cassandra as bytes, but how it's stored is
less important as far as I can see.
/Patrik
ons 21 sep. 2016 kl. 17:58 skrev Tim Pigden :
> Hi Justin
> Thanks for the
Automatic startup on other node is how it is supposed to work, and we have
tests for it. How do you down the dead node?
/Patrik
mån 19 sep. 2016 kl. 22:00 skrev Ajmal Babu :
> Working on AKKA persistence with cluster sharding and the flag
>
; 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
Akka Tech Lead
Lightbend
The Artery config is not correct, see release announcement for M4
/Patr
ons 14 sep. 2016 kl. 14:12 skrev Guido Medina :
> Hi Silvio,
>
> The following are the only things I can recommend you:
>
>- You have a short time to deliver? Why bother now with Artery if
>that's
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/group/akka-user
> ---
> You
gt; Thanks to you both.
>>
>> On Saturday, September 10, 2016 at 11:34:26 AM UTC-5, √ wrote:
>>>
>>> There's also ConductR + SBR
>>>
>>> --
>>> Cheers,
>>> √
>>>
>>> On Sep 10, 2016 5:09 PM, "Patrik Nordwall" <patr
Are you aware of the importance of the first seed node, the one you have
listed as first element in sees-nodes list? See documentation.
You can get decent behavior if you wait with joining until the list of
discovered nodes stabilize, i.e. not changing within X seconds. Then sort
them to make
next.
Pssst... you can also win a t-shirt.
Happy hakking!
--
Patrik Nordwall
Akka Tech Lead
Lightbend <http://www.lightbend.com/> - Reactive apps on the JVM
Twitter: @patriknw
--
>>>>>>>>>> Read the docs: http://akka.io/docs/
>>>>>&
If it's cpu bound work I would recommend one dispatcher for all with
slightly less threads than cores. Set max to cores - 1. Too many threads
will just make things slower for cpu bound work.
The reason for not using all cores is that it can be good to have some
spare capacity for other manegement
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 received this message becaus
On Thu, Sep 8, 2016 at 8:38 AM, Patrik Nordwall <patrik.nordw...@gmail.com>
wrote:
>
>
> On Thu, Sep 8, 2016 at 12:42 AM, <ques...@gmail.com> wrote:
>
>> On Wednesday, September 7, 2016 at 3:16:57 PM UTC-7, Guido Medina wrote:
>>>
>>> B
---
> 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, se
ead, says the message are sent from the
> same "context". Maybe I'm missing a context other than the pair of actors
> that applies to message ordering.
>
> Kendall
>
> On Wednesday, September 7, 2016 at 5:12:49 AM UTC-7, Patrik Nordwall wrote:
>>
>> I think the
>>>> --
> >>>>>>>>>> Read the docs: http://akka.io/docs/
> >>>>>>>>>> Check the FAQ: http://doc.akka.io/docs/akka/
> current/additional/faq.html
> >>>>>>>>>> Search the archives:
k 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"
Isn't it covered in the documentation?
http://akka.io/docs/
/Patrik
tors 1 sep. 2016 kl. 23:43 skrev Dagny T :
>
> I'd like to find reliable and current information for learning this using
> v2.4.9.
>
> I've posted a reply to someone else's related message; but wanted to
> On Thursday, September 1, 2016 at 8:33:04 PM UTC+2, Patrik Nordwall wrote:
>
>> I think we should handle exceptions from serializer.toBinary as transient.
>> Can you please create an issue. <https://github.com/akka/akka/issues/new> I
>> can understand that the re
The stop signal is that the actor is terminated, i.e. you called
context.stop, so stashing is fine
fre 2 sep. 2016 kl. 16:46 skrev kraythe :
> So if I have an actor that while on a specific state simply stashes any
> message that it doesn't handle, will it ignore the stop
That feature with short names is not released yet. It's in the Artery
branch.
/Patrik
tors 1 sep. 2016 kl. 10:42 skrev Konrad Malawski :
> You can also just set the provider to "remote" (or "cluster").
> It's a bit simpler to not make a typo in those ;)
>
> On Thu, Sep 1,
ka-user.
>>>> For more options, visit https://groups.google.com/d/optout.
>>>>
>>>
>>> --
>>> >>>>>>>>>> Read the docs: http://akka.io/docs/
>>> >>>>>>>>>> Check the FAQ: htt
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, send em
eceiving 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.
>
The commit commands are emitted to the underlying KafkaConsumer in right
order. It is waiting for the results of the commits that are done in
parallel, and will possibly increase total throughput. We observed better
throughput in performance tests.
It would be great to clarify this in docs. You
) with a much
> subtler one (split-brain). IMO, it's time for this misfeature to die, and
> just be replaced with a flat statement in the documentation that "in a real
> cluster, you have to either buy SBR or come up with a downing strategy".
>
> On Fri, Aug 26, 2016 at 7:29 AM, Patrik No
, 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.
>
--
Patrik
PM, Cosmin Marginean <cos.margin...@gmail.com>
wrote:
> Thanks Patrik. I was hoping there would be a more flexible (and less
> hardcoded way to do this)
>
> On 25 Aug 2016, at 18:41, Patrik Nordwall <patrik.nordw...@gmail.com>
> wrote:
>
> Start more worker actors on e
d": "on",
>>>>> "allow-local-routees": "off",
>>>>> "use-role": "worker"
>>>>> }
>>>>> }
>>>>>
>>>>>
>>>>> This wor
That would be a great contribution to the Akka Streams Intregration
initiative, see blog post
http://blog.akka.io/integrations/2016/08/23/intro-alpakka
Please create a pull request in akka-stream-contrib. It should be a
separate sub-project, similar to akka-stream-contib-amqp
Cheers,
Patrik
for serialization. I'm using akka provided
>> cluster message Serializer
>>
>>
>> serializers {
>> akka-cluster = "akka.cluster.protobuf.ClusterMessageSerializer"
>> }
>> serialization-bindings {
>> "akka.cluster.ClusterMessage" = akka-
orkJoinPool.java:1253)
>
> at scala.concurrent.forkjoin.ForkJoinPool$WorkQueue.
> runTask(ForkJoinPool.java:1346)
>
> at scala.concurrent.forkjoin.ForkJoinPool.runWorker(
> ForkJoinPool.java:1979)
>
> at scala.concurrent.forkjoin.ForkJoinWorkerThr
ve and dumb, and must *never* be used in production. Auto-downing
>>> is always likely to cause cluster disasters, and having such a short
>>> auto-down timeout essentially guarantees it.
>>>
>>> Basically, you're getting split-brain -- you need to replace auto-
> 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+u
extra logic so that it completes when it has delivered
>> item N (and not wait for N+1, which may be a long time coming).
>>
>> On Aug 21, 2016 6:50 AM, "Patrik Nordwall" <patrik.nordw...@gmail.com>
>> wrote:
>>
>> I think it makes se
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..
It can sometimes be difficult to setup loading of the native sigar library.
Several alternatives are listed in docs
http://doc.akka.io/docs/akka/2.4/java/cluster-metrics.html#Hyperic_Sigar_Provisioning
You should see warnings/errors in the log.
/Patrik
lör 20 aug. 2016 kl. 17:10 skrev Chris Van
It's also worth noting that for the "leader" concept there is no election.
It's simply the node with the lowest address with some additional rules
around membership status and unreachability. That means that there can be
more than one "leader" at the same time, e.g. one for each side of a
network
By the way, we can continue design discussion in the ticket
https://github.com/akka/akka/issues/13938
On Tue, Aug 16, 2016 at 9:51 AM, Patrik Nordwall <patrik.nordw...@gmail.com>
wrote:
> Here is a link to the recovery logic: https://github.com/
> akka/akka/blob/master/akka-persiste
;>>>>> 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 subscribed to the Google Groups
> &q
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.
>
hives: 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.
What are you trying to solve?
/Patrik
tors 11 aug. 2016 kl. 13:46 skrev Yutao Shuai :
> Does the leader will down himself or another node will become leader?
> Where is the code about this in the source files. Thanks much for your
> help!
>
> --
> >> Read the docs:
No, config is immutable and not changed after startup.
I see no reason for doing that in your example. Use default, 5.
/Patrik
fre 12 aug. 2016 kl. 03:56 skrev Yutao Shuai :
> Is there a way to reload configuration at run time?
>
> For example:
> I defined failure detect
I have not looked at the logs but you find answer to your last question in
http://doc.akka.io/docs/akka/2.4/scala/cluster-usage.html#How_To_Cleanup_when_Member_is_Removed
/Patrik
fre 5 aug. 2016 kl. 22:31 skrev Eric Swenson :
> One more clue as to the cluster daemon's shutting
The milestone of an issue is no guarantee that it will be released in that
version, until the issue is closed. We can't do that kind of planning.
This would be a great feature for community contibution. Queries are there
now.
/Patrik
ons 10 aug. 2016 kl. 07:04 skrev Muthukumaran Kothandaraman <
I agree with Ryan that it's generally not recommended.
I would like to add that the cluster membership and distributed data will
work pretty fine across DC thanks to their gossip based protocols, but
there are other tools, such as cluster sharding, that are not a good fit
for it.
Cluster downing
Take a look at Endre's streaming xml parser, for inspiration:
https://github.com/drewhk/akka-xml-stream/pull/1
ons 10 aug. 2016 kl. 19:57 skrev JY :
> Nobody can help me to read 5GB of upload data with akka-http, and without
> crashing my VM with OutOfMemoryException ?
>
>
; 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
ou 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@g
parameter. Yet, these were,
> indeed, logged as errors not warnings. -- Eric
>
> On Monday, August 8, 2016 at 11:28:33 PM UTC-7, Patrik Nordwall wrote:
>>
>>
>>
>> On Mon, Aug 8, 2016 at 10:06 PM, Eric Swenson <er...@swenson.org> wrote:
>>
>>
;
>>
>>>
>>> That's why I'm using that semi-hacky way to force the underlying journal
>>> plugin to start.
>>>
>>> Thanks.
>>>
>>> WBR,
>>> Alexey
>>>
>>> On Sunday, August 7, 2016 at 8:40:19 AM UTC-7
> 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 subscribed to the Google Groups
> "Akka User Lis
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
why I'm using that semi-hacky way to force the underlying journal
> plugin to start.
>
> Thanks.
>
> WBR,
> Alexey
>
> On Sunday, August 7, 2016 at 8:40:19 AM UTC-7, Patrik Nordwall wrote:
>>
>> As far as I can see the PersistencePluginProxy can only be used with t
in this thread
IllegalStateException: Invalid replayed event [1] in buffer from old writer
Then this should be logged at WARNING level and it should have discarded
the event from the "old" writer.
>
> On Aug 7, 2016, at 9:47 AM, Patrik Nordwall <patrik.nordw...@gmail.com>
> wrot
; we'll likely take advantage of Lightbend services and products.
>
> Thanks again. -- Eric
>
>
> On Sunday, August 7, 2016 at 9:48:08 AM UTC-7, Patrik Nordwall wrote:
>
>> It's typically caused by multiple persistent actors with the same
>> persistenceId running at the same
nal/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 emails
.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.
> To post to t
The last link should have been
https://github.com/akka/akka-persistence-cassandra/issues/116
On Sun, Aug 7, 2016 at 6:34 PM, Patrik Nordwall <patrik.nordw...@gmail.com>
wrote:
> This is by design. See discussion in https://github.com/akka/
> akka/issues/18050. It should be done i
ails 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.
>
--
Patrik
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.
>
--
Patrik Nord
Yes, that is documented behavior. The reason for the special first seed
node is also documented. What is your question?
Regards,
Patrik
tors 4 aug. 2016 kl. 04:33 skrev Yutao Shuai :
> In a 3-node cluster, all of nodes are seed nodes, if first node start
> failed, the whole
That is documented behavior.
reference.conf have substitutions resolved first, without application.conf
in the stack, so the reference stack has to be self-contained.
One way to solve it is to do the concatenation of the base url and the
method suffix in code instead.
/Patrik
tors 4 aug. 2016
You're welcome
tis 2 aug. 2016 kl. 19:40 skrev Dagny T :
>
> Thank you, Jim and Patrik for your responses!
>
> Looking into the VersionVector.scala.
> Always amazed at what a good source of learning it is to see
> well-structured, code-reviewed Open Source(!)
>
> THANKS
There is a public version vector implementation in akka-distributed-data,
if that is what you are looking for.
https://github.com/akka/akka/blob/master/akka-distributed-data/src/main/scala/akka/cluster/ddata/VersionVector.scala
/Patrik
fre 29 juli 2016 kl. 05:08 skrev Jim Hazen
Have you tried version 0.17 with the compat flag described in the readme?
https://github.com/akka/akka-persistence-cassandra/blob/master/README.md
/Patrik
lör 30 juli 2016 kl. 16:56 skrev Justin du coeur :
> I see you got things working, which is great. I just wanted to
It's one of Lightbend's commercial offerings. Contact Lightbend for more
information and pricing https://www.lightbend.com/contact
lör 23 juli 2016 kl. 06:26 skrev Yutao Shuai <szqs...@gmail.com>:
> Can I use the SBR for free?
>
> 在 2016年7月22日星期五 UTC+8下午10:02:13,Patrik Nordwa
Yes, it exists for 2.3.x
fre 22 juli 2016 kl. 13:01 skrev Yutao Shuai :
> Can I use split brain resolver in version 2.3.10 ?
>
> 在 2016年7月22日星期五 UTC+8下午6:08:22,Akka Team写道:
>>
>> Hi Yutao,
>>
>> Please refer to the documentation page Patrik has linked. It explains the
>>
The leveldb store is shared by second node in the cluster through NFS
> mount. When primary is down, cann't we start the "SharedLeveldbStore" in
> the second node on receipt of "MemberRemoved/MemberExited" cluster events?
>
> Thanks,
> Manoj
>
>
> On W
SharedLeveldbJournal is not resillient. It's a single point of failure
since it is only running on one node. It's only intended for demo examples.
Please use a real distributed jounal, such as akka-persistence-cassandra
/Patrik
tors 21 juli 2016 kl. 01:24 skrev Manoj Santhakumaran
Akka Streams is an excellent choice for this use case. I would even say
that it is the canonical use case for Akka Streams. We have probably not
highlighted that enough, yet.
Cheers,
Patrik
tors 14 juli 2016 kl. 13:22 skrev James Matlik :
> Using Akka streams for ETL is
find our sprint plans at akka/akka-meta
<https://github.com/akka/akka-meta/issues>. The goal is to complete Artery
in end of August and September and then release it in a 2.4.x version of
Akka as an optional transport.
Happy hakking!
--
Patrik Nordwall
Akka Tech Lead
Lightbend <http:
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
luster? Do we have a API for that?
>
> Regards,
> Rajesh
>
>
>
>
> On Monday, July 4, 2016 at 12:08:38 PM UTC+5:30, Patrik Nordwall wrote:
>
>> Normally you would use the ClusterSingletonProxy, but if you want to
>> subscribe to the membership events and sort
rding related messages just like cluster
> messages? That might help me figure out what's happening.
>
You can enable debug level logging. Cluster Sharding logs things in great
detail.
akka.loglevel = DEBUG
/Patrik
>
> On Friday, 1 July 2016 15:16:00 UTC+1, Patrik Nordwall wro
> >>>>>>>>>> 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 su
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://groups.goog
akka-sample-cluster-scala to see what you're doing differently there..
>
>
> On Sunday, July 3, 2016 at 8:45:25 PM UTC+2, Raymond Roestenburg wrote:
>>
>> Thanks Patrik, I'll try that.
>>
>> On Friday, July 1, 2016 at 8:32:27 AM UTC+2, Patrik Nordwall wrote:
>
CPU is high because of serialization.
>
> In your test of 700.000 does this include a response from the server (or
> remote peer or whatever)?
>
No, that's one-way between two JVMs. Flow control is handled by one ack per
batch of 1000 messages (several of these batches in flight).
echo). Sorry, I
> was not precise on that. We call it transaction becase we make a kind of
> commit in ram but in this case it is not relevant.
>
> On Mon, Jul 4, 2016 at 8:51 AM, Patrik Nordwall <patrik.nordw...@gmail.com
> > wrote:
>
>> Are you talking about 1.000
401 - 500 of 1676 matches
Mail list logo