Jumping in a bit late, but one comment:
On Fri, Jun 19, 2015 at 1:38 PM, Guido Medina oxyg...@gmail.com wrote:
I do agree with Luis, but I wasn't pushing much that approach because
AFAIK you are new to Akka and you have only one server, the concept of
sharding and Akka persistence can be
While I think of it (reminded by the other thread), it occurs to me that
the devs get all the questions and complaints, and all rarely a thank-you.
So: I'd like to compliment the team (I suspect primarily Patrik in this
case) on the Cluster Sharding mechanism. Querki predates it, and I had
built
Thanks Patrik but still it takes the same amount of time. While waiting
I get these in the logs
[INFO] [06/22/2015 19:43:31.255]
[testSystem-akka.actor.default-dispatcher-4]
[akka://testSystem/deadLetters] Message
[akka.cluster.InternalClusterAction$InitJoinNack] from
You seem to confuse failure and termination. Failure happens when an actor
throws an exception, e.g. during handling a message. Then it gets suspended and
its parent needs to decide what to do, e.g. restart. Termination happens when
an actor gets stopped, e.g. by itself, or – in the case of
perhaps the Cluster Usage documentation page should be updated with a
section containing links to external libraries implementing this glue
functionality, similar to how external serializers are mentioned on the
Serialization page:
if you are sure you aren't going to reference the val, then you could do
something like
val fakeSystem = null.asInstanceOf[ActorSystem]
-Michael
On 06/20/15 17:05, Maatary Okouya wrote:
I have a Service class that takes an actor system at construction
time. Some of the method of the service
the current documentation appears to be incorrect, which i believe was
the source of confusion. on line 20 of the code block of the section
Actors and shared mutable state on page
http://doc.akka.io/docs/akka/2.3.11/general/jmm.html#jmm-shared-state it
specifically states:
18 //
You've got your demand condition as 'DemandFromAny', when I think it should
be 'DemandFromAll'. I'm not exactly sure why that would explain your exact
behaviour, but it should help.
If you consciously don't want to wait for demand from both, you could e.g.
have 2 states which are randomly
There’s actually one thing you need to take into account when using
DynamoDB for persistence.
I've been bitten by this a few times when using other Amazon services.
The Java SDK provided by Amazon includes two interfaces: synchronous and
asynchronous.
I imagine you’d prefer to use the
Why deduplicate non-logged events at all?
Doing the substitution but not incurring the IO cost must be worth it?
--
Cheers,
√
On 22 Jun 2015 11:09, Roland Kuhn goo...@rkuhn.info wrote:
It depends on what you want to achieve: not doing the substitution for
non-logged events is an explicit
Hi,
Can you please point me to an example where akka-http is used to process an
incoming JSON object within a POST request?
I want to deserialize the object and send it to an actor to process it.
All I can get out of it is a ByteStream. Do you have to manually
deserialize it?
Best Regards
One problem could be if the string contains placeholders {}.
I would guess that the reason why we used debug({}, message) was to avoid
the toString of the message if the level is not enabled. Checking the level
as you suggest might be enough.
When using LoggingAdapter we materialize it to a
You could try to decrease the interval of these periodic tasks:
akka.cluster.gossip-interval = 500 ms
akka.cluster.leader-actions-interval = 500 ms
On Fri, Jun 19, 2015 at 10:11 PM, 'Konstantinos Kougios' via Akka User List
akka-user@googlegroups.com wrote:
Thanks Patrik, this worked. For me
Ah, it seems that I misunderstood: this filter is not part of the pre-filtering
that is done before even sending to the logger actor. Then disregard my comment
about saving some cycles, within the logger actor it is obviously too late for
that anyway.
Patrik, your comment brought back a dim
I have a scenario where I load the *products* from a *CSV* file and persist
them. The CSV file has hundreds of products. I have few users who upload
the CSV file from the UI. In my current non-actor system, the *ID (Primary
Key)* is generated by the database. The *ID* is not auto-generated.
I
Hello,
Me and my team have successfully managed to bootstrap Akka Cluster with
Docker and Mesos, and we're actually running automated performance tests
against ephemeral clusters using this combination - so it's working *that*
well. The thing that really made it tick (and quickly so - since
On Monday, 22 June 2015 11:30:30 UTC+1, √ wrote:
Why deduplicate non-logged events at all?
Doing the substitution but not incurring the IO cost must be worth it?
Turbo Filters are a well defined concept in Logback land:
http://logback.qos.ch/manual/filters.html#TurboFilter
The only logic
Actually, there is a way to access the materialized value of a graph in the
graph itself, see:
http://doc.akka.io/docs/akka-stream-and-http-experimental/1.0-RC3/scala/stream-graphs.html#Accessing_the_materialized_value_inside_the_Graph
-Endre
On Sun, Jun 21, 2015 at 7:43 PM, Lance Arlaus
Does anyone see any major problems with this workaround? If not, I
recommend it as a patch to the mainline.
package akka.event.slf4j
import akka.actor._
import akka.event.Logging._
/**
* Stock Slf4jLogger actually logs everything as {} with a
* parameter, which is incompatible with much of
Doing the filtering pre-substitution seems like a bug.
--
Cheers,
√
On 22 Jun 2015 01:54, Sam Halliday sam.halli...@gmail.com wrote:
Patrik,
Thanks for investigating! You saved me a few hours off my Monday as I
was going to go through this in detail and put together a minimal test
case :-)
It depends on what you want to achieve: not doing the substitution for
non-logged events is an explicit goal in our infrastructure.
Regards,
Roland
22 jun 2015 kl. 11:02 skrev Viktor Klang viktor.kl...@gmail.com:
Doing the filtering pre-substitution seems like a bug.
--
Cheers,
√
Here you are:
https://github.com/hseeberger/reactive-flows/blob/master/src/main/scala/de/heikoseeberger/reactiveflows/HttpService.scala#L79
https://github.com/hseeberger/reactive-flows/blob/master/src/main/scala/de/heikoseeberger/reactiveflows/HttpService.scala#L79
Cheers
Heiko
--
Heiko
You're welcome! Thank you for the positive feedback. Glad to hear that you
find it useful.
Cheers,
Patrik
mån 22 jun 2015 kl. 19:29 skrev Justin du coeur jduco...@gmail.com:
While I think of it (reminded by the other thread), it occurs to me that
the devs get all the questions and complaints,
Ok, here's what I've discovered. If the route starts emitting to outA, then
it will continue to emit until the route switches to outB, then it stops.
Same thing if it starts with outB, it will continue until it switches to
outA and then it stops. So strange.
On Friday, June 19, 2015 at
Hello
I am learning Remoting and have a question. I am looking at example where
remote actor is created programmatically. As per the typesafe activator
sample, I read
Error handling, i.e. supervision, works exactly in the same way as if the
child actor was a local child actor. In addtion,
1. yes
2. not exactly: it’s not possible to become a parent by looking up an actor,
because each actor gets started by a parent actor (if you use
ActorSystem.actorOf the system actor called guardian will be the parent)
So, one possible solution: Your parent actor watches its children which are
Thanks for the link. It was exactly about what I needed.
On 06/20/2015 04:06 AM, Luis Medina
wrote:
Oops, forgot to post the
link: https://www.parleys.com/tutorial/easy-scalability-akka
(you'll need to register a free account to view the
This question may be a bit vague, but I'm unsure how to make it more
precise.
While using the cluster sharding extension, you have to provide some sort
of persistence journal so that the plugin can store its metadata
(ShardRegionAllocated, etc...).
These metadata are used when new actors are
Dear hakkers,
due to great interest and seeing how it works very well for other communities,
Akka is joining the gitter fold. We have two public chat rooms currently
configured:
akka/akka https://gitter.im/akka/akka is the user chat where all questions
and ideas about using Akka can be
Hi,
has anybody already used akka io with iso 8583 messages?
Tks
--
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 received this message
Hi All,
While using the cluster sharding extension, you have to provide some sort
of persistence journal so that the plugin can store its metadata
(ShardRegionAllocated, etc...).
These metadata are used when new actors are instantiated / moved across
nodes to recover from their frozen state.
ok
Sam, please open an issue.
/Patrik
On Mon, Jun 22, 2015 at 1:57 PM, Roland Kuhn goo...@rkuhn.info wrote:
Ah, it seems that I misunderstood: this filter is not part of the
pre-filtering that is done before even sending to the logger actor. Then
disregard my comment about saving some cycles,
No problem, raised as https://github.com/akka/akka/issues/17801
On Monday, 22 June 2015 13:23:02 UTC+1, Patrik Nordwall wrote:
ok
Sam, please open an issue.
/Patrik
On Mon, Jun 22, 2015 at 1:57 PM, Roland Kuhn goo...@rkuhn.info
javascript: wrote:
Ah, it seems that I misunderstood: this
Any ideas out there? I feel like this is something really stupid, but just
can't see it. Any help is greatly appreciated.
--Eric
On Friday, June 19, 2015 at 3:55:37 PM UTC-6, Eric Nelson wrote:
Hi all. I'm using Akka Streams 1.0-RC3, and am getting some weird behavior
with a custom
34 matches
Mail list logo
