On Sat, Feb 24, 2018 at 8:27 PM, Patrik Nordwall
<patrik.nordw...@gmail.com> wrote:
> 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 <frederica...
Hello all,
I've just done a few tests with the new Configuration Compatibility Check
and noticed that no compatibility check is performed (aka checks are
ignored) when joining the cluster manually using
Cluster(system).join(address). Is that expected?
I didn't find any documentation
t;
> lör 16 dec. 2017 kl. 11:38 skrev frederic arno <frederica...@gmail.com>:
>>
>> Thanks Patrick.
>>
>> What do you think would be the best way to do it, what I described in my
>> original message or rather having the cluster client setup a death watch on
ike an excellent suggestion and contribution is welcome.
Thanks, Patrik
lör 16 dec. 2017 kl. 09:15 skrev Frederic <frederica...@gmail.com>:
> Hi all,
>
> The ClusterClient is designed to connect to a single ClusterReceptionist.
> When a cluster node running a receptionist gr
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., because the node is shutting down), the cluster clients connected to
that receptionist will keep sending message to it until the
Hello,
>From what I read about it in the docs
(http://doc.akka.io/docs/akka/2.4.1/scala/cluster-sharding.html), "The
shard saves persistent snapshots after this number of persistent events.
Snapshots are used to reduce recovery times."
They seem to be created after a certain number of events
Hi,
First I would like to say I'm a big fan of akka-http. It's really a great
framework and I'd like to thank you all for making such a great product.
In akka-http documentation there's a big caution I'm experimenting :
Caution: When you receive a non-strict message from a connection then
>
Hi everybody,
I have a strange IllegalUriException with akka-http :
My app is quite simple : a logging proxy
I have configured my network to use this proxy for all http requests.
what the proxy does :
val route: Route =
logging {
{
forward
}
}
at 8:25 PM, Endre Varga endre...@typesafe.com
javascript: wrote:
On Wed, Jun 24, 2015 at 8:20 PM, Frederic freder...@gmail.com
javascript: wrote:
Yes Michael, you are right. I based my example code on the documentation
you referenced, assuming it was correct.
What would be the correct
:
Hi Frederic,
you violate the first rule of Actors: never call *any* of their methods
from outside of their context of execution. This is true for all of them,
including context() and self(). While the result of calling self() can then
safely be shared afterwards (an ActorRef is thread-safe
Hello,
I found a quite specific case involving Actors, Future callbacks and
exceptions where self becomes deadLetters.
I have the feeling I'm using self the way it is meant to be used, as
described
here: http://doc.akka.io/docs/akka/2.3.11/general/jmm.html#jmm-shared-state
Am I doing
, Frederic wrote:
Hello,
I found a quite specific case involving Actors, Future callbacks and
exceptions where self becomes deadLetters.
I have the feeling I'm using self the way it is meant to be used, as
described here:
http://doc.akka.io/docs/akka/2.3.11/general/jmm.html#jmm-shared
12 matches
Mail list logo
