I have some blocking code (a call to file.mkdirs()) that I am enclosing
inside blocking {} as below.
I have a feeling this may be incorrect. But I don't see a way to use
ActorAttributes in this scenario.
// Is this the way to manage the blocking mkdirs?
import scala.concurrent.blocking
de
It seems that it is not as easy as originally appeared - precisely error
handling and handling failed writes needs some work.
My results for akka-io-remote compared to netty3
I use code posted some time ago on this list (//source
https://gist.github.com/ibalashov/381f323ca976c3364c84) just becau
Isn't a valve just a specialization of a throttle?
Throttle at infinite = open valve
Throttle at 0 = closed valve
As long as you have an out of band way to adjust this throttle (via
materialized value?), you should have your valve already.
--
>> Read the docs: http://akka.io/docs/
Thanks for the reply.I wasn't proposing that the number of groups be
limited, just that the number being fed simultaneously be limited. I
thought that each new element creates a group if it's a distinct key. That
seems orthogonal to backpressure. But I suppose one wouldn't know when each
substream
Hi Michael,
On Mon, Feb 22, 2016 at 4:04 PM, Michi wrote:
> Hi Roland,
>
>
>> I don’t agree: if you write a program that shall have certain security
>> characteristics, then you must certainly test it under the same constraints
>> that you will run it with in production. Otherwise you run someth
Hi Roland,
> I don’t agree: if you write a program that shall have certain security
> characteristics, then you must certainly test it under the same constraints
> that you will run it with in production. Otherwise you run something that
> you have not tested. How would you test the failure s
Hi Alexey,
There is no built-in way to access the configuration, but as you noted, you
can inject it as an element. This is actually safe because configuration in
Akka systems is always immutable. Technically, you can even close over a
val containing the configuration but be careful though because
Hi Chelios,
Isn't the LevelDB plugin enough for your use case then? No fuss, no
connections, no distribution, and it is quite fast.
-Endre
On Tue, Feb 16, 2016 at 12:04 PM, Chelios
wrote:
> Hey Guys,
>
> Sorry didn't get any notifications about your replies in my email. Thank
> you so much for
Hi Arno,
You probably need a combination of the ordinary cluster singleton and some
external tool. It might be completely possible to have your local,
cluster-wise singletons communicating with a Zookeeper instance to
coordinate leadership among the clusters. Since the "meta-leadership" will
chang
Hi,
This is not an easy task, I am not sure how to do it with built-in
combinators (you can do such custom stages but they are quite advanced and
we have not yet openly documented all APIs that is needed for these kind of
stages). But the largest issue will be that Source[A] and Source[B] will
not
Hi Tim,
A quick'n'dirty solution that comes to my mind is to configure the
ActorSystem in that test with an overridden configuration that points to an
invalid port/ip (depending on your journal plugin).
-Endre
On Tue, Feb 9, 2016 at 5:41 PM, Tim Pigden wrote:
> Hi
> I have the following scenar
Hi Richard,
On Fri, Feb 19, 2016 at 11:11 PM, Richard Rodseth
wrote:
> Thought I'd start a new thread for my latest stumbling block, while I
> explore some options that don't feel great.
>
> Short version:
> flatMapMerge has a "breadth" parameter which limits the number of
> substreams in flig
+1 for valve :-)
--
Cheers,
√
On Feb 22, 2016 11:33 AM, "Akka Team" wrote:
> Actually, a controllable version of .throttle called something like .valve
> is not a bad idea. Contributions are welcome :)
>
> -Endre
>
> On Mon, Feb 22, 2016 at 9:53 AM, Viktor Klang
> wrote:
>
>> Depends on what k
I hope we can get finally remoting up on our table again in our new roadmap
(to be decided next week). Stay tuned.
-Endre
On Sun, Feb 21, 2016 at 4:53 PM, Guido Medina wrote:
> Now on another I'll be one of the users that will appreciate a lot your
> effort as I completely relay on akka-remote
Actually, a controllable version of .throttle called something like .valve
is not a bad idea. Contributions are welcome :)
-Endre
On Mon, Feb 22, 2016 at 9:53 AM, Viktor Klang
wrote:
> Depends on what kind of semantics you're looking for: immediate pause,
> controlled rate of inputs, or other?
Depends on what kind of semantics you're looking for: immediate pause,
controlled rate of inputs, or other?
On Mon, Feb 22, 2016 at 8:56 AM, Tal Pressman wrote:
> I don't know of any way to do it out of the box, but you can create your
> own custom GraphStage that handles the pause/resume logic,
16 matches
Mail list logo
