On Wed, Jan 14, 2015 at 6:58 PM, Oleg Mürk wrote:
> Hello!
>
> Thanks for the answers! I have a few more questions/clarifications below,
> if You don't mind.
>
> On Wednesday, January 14, 2015 at 6:02:33 PM UTC+2, Akka Team wrote:
>>
>>
>>> Is it possible to configure Akka Cluster with auto-downi
Hello!
Thanks for the answers! I have a few more questions/clarifications below,
if You don't mind.
On Wednesday, January 14, 2015 at 6:02:33 PM UTC+2, Akka Team wrote:
>
>
>> Is it possible to configure Akka Cluster with auto-downing so that with
>> 100% probability at each moment at most one
Hi thanks
I've been doing some research and concluded that was probably the case
(mileage may vary that is)
On 14 Jan 2015 21:26, "Justin du coeur" wrote:
> Others may have different opinions, but I suspect there's too much "your
> mileage may vary" to answer the question. For example, I'm plan
sorry, the reason is [x.y.Reply$], i.e. full path of the message class
On Wednesday, January 14, 2015 at 4:53:36 PM UTC-5, Nan Zhu wrote:
>
> Hi, all
>
> Here is the overview of my system
>
> (two machines)
>
> ActorSystem1 (RemoteActorRefProvider ) =>
> ActorSystem2(ClusterActorRefProvider)
>
Hi, all
Here is the overview of my system
(two machines)
ActorSystem1 (RemoteActorRefProvider ) =>
ActorSystem2(ClusterActorRefProvider)
actor in ActorSystem1 sent a hello message to actorSystem2 via a
cluster-aware router, and the receiver in the cluster replies a message
"Reply" (defined
Hi,
I guess the correct answer is "it depends" J, but I can describe what we
use right now, as we're also using Akka (and seeing as it's been very
rewarding to do so we do it more and more), but are confined to Java.So
first of all, I would recommend against inheritance.
That route quickly be
Others may have different opinions, but I suspect there's too much "your
mileage may vary" to answer the question. For example, I'm planning for
two months to cluster my app (probably starting in March) -- but that's
about forty thousand lines of code involving several dozen different Actor
types,
Thanks Endre for the prompt reply, and the good news! I look forward to
the next release.
Regards,
Jim
--
>> Read the docs: http://akka.io/docs/
>> Check the FAQ:
>> http://doc.akka.io/docs/akka/current/additional/faq.html
>> Search the archives
Hi
I wonder if anyone has experience or thoughts to share about upgrading
production cluster systems?
I would ideally like to
- upgrade the cluster without downtime/scheduled outage
- not mutate infrastructure, in other words, deploy a new set of nodes
with the new version
- do a
On Wed, Jan 14, 2015 at 5:02 PM, Akka Team wrote:
> Hi Oleg,
> Your understanding of both topics, in the current version of Akka, are
> correct.
> More specifically:
>
> Is it possible to configure Akka Cluster with auto-downing so that with
>> 100% probability at each moment at most one cluster
Hi Oleg,
Your understanding of both topics, in the current version of Akka, are
correct.
More specifically:
Is it possible to configure Akka Cluster with auto-downing so that with
> 100% probability at each moment at most one cluster node thinks that he is
> the leader (or singleton) even in case
Hello there,
Patrik's pub-sub module definitely has been used in larger deployments
already and proved itself to be a valuable tool.
Our plans about the cluster utilities currently in contrib are to promote
them into "akka proper", that is they'll end up in new modules:
akka-cluster-sharding, akka-
Hi Brian,
It seems to me that it is not the stopping that doesn’t work - you can
verify this by putting an override def postStop() = log.info("context.stop
really worked") into the worker actor.
What seems to be happening is the remote watch fails to be established in
time, which is part of the re
On Wed, Jan 14, 2015 at 2:44 PM, Endre Varga
wrote:
>
>
> On Fri, Jan 9, 2015 at 10:02 PM, Viktor Klang
> wrote:
>
>>
>>
>> On Fri, Jan 9, 2015 at 9:40 PM, David Hotham > > wrote:
>>
>>> Of course it's normal and expected that a PriorityQueue returns equal
>>> priority elements in arbitrary orde
On Fri, Jan 9, 2015 at 10:02 PM, Viktor Klang
wrote:
>
>
> On Fri, Jan 9, 2015 at 9:40 PM, David Hotham
> wrote:
>
>> Of course it's normal and expected that a PriorityQueue returns equal
>> priority elements in arbitrary order. That's just how heaps work. However
>> that doesn't imply that a
Awesome contribution David, thanks a lot!
We'll think of a plan on how to include or replace the old impl with your
PR and ping that issue again soon :-)
On Sat, Jan 10, 2015 at 4:08 PM, David Hotham
wrote:
> I've submitted a first stab at an implementation at pull request #16634.
>
> On Friday,
Hello again,
This isn't a bug, and in fact should be asymmetric as is, because this
trait is only really useful for scaja - it is implicit defs that bring in
marshallers into scope - that is not really usable from Java.
The jar is published properly and contains the SprayJsonSupport class as
expect
Hi Gerald,
thanks for noticing this!
It seems that the akka-http-marshallers jar is not even published even.
I opened a ticket to track the investigation on this:
https://github.com/akka/akka/issues/16646
I don't think this was intentional but need to confirm with the team.
On Fri, Jan 9, 2015 at
Hi Jim,
We are aware of the issue, a fix is being prepared:
https://github.com/akka/akka/pull/16640
-Endre
On Wed, Jan 14, 2015 at 2:24 AM, Jim Newsham wrote:
>
> P.S. I've checked the release notes and didn't see anything specifically
> related to ResendUnfulfillableException, although some
19 matches
Mail list logo
