Hello!
I have a task to develop a http balance loader for my 2 servers. Here is my
qucik and very dirty implementation
https://gist.github.com/zergood/e705cd6ce4cfec47c0a5. The main problem with
it is performance, this solution is slower than my single server.
What is the reason of
Hi Roland,
On Wednesday, 27 May 2015 08:18:09 UTC+1, rkuhn wrote:
For this venture you need no HTTP documentation
Actually I'd like to go futher than akka-http and see documentation that
allows me to use WebSockets with akka-io directly, bypassing the
Streaming API.
The historic limitation has
Hi,
At the current point the aim of streams 1.0 was to reach a desired
functionality level. Basically there is zero performance work done at this
point. We will improve performance in later versions though.
We basically refactored streams API in roughly every second release, so we
are currently
Yes, that works, Thanks!
I think that this should probably be mentioned in the docs somewhere.
On Wednesday, 27 May 2015 08:21:37 UTC+1, Giovanni Alberto Caporaletti
wrote:
You need both an implicit FlowMaterializer and an implicit
ExecutionContext in scope. I haven't followed the chain to
Hi to all,
I have something strange that I cannot understand.
I have this test that worked very well
give online status NeverLogged for never logged user in new WithUsersData() {
val auth = createAndAuthenticateUser
val user1 = auth._1
val sid1 = auth._2
val tp1 =
I've done little benchmarks to compare spray and akka-http performance. I
use default jvm and akka settings. So you can see that there is
an significant performance difference between it.
code:
spray https://gist.github.com/zergood/18bae0adc2e774c31233.
akka-http
Hello, I have an Actor system that implements a polling functionality
(every x minutes an Actor is woken up and it creates a bunch of other
actors that do something and then get killed). However, over a few days
of running I get GC Out of Memory errors. What tools are out there to
instrument
Hi,
Instead of Http.request, you should use the Flow returned by
Http.superPool() (see
http://doc.akka.io/docs/akka-stream-and-http-experimental/1.0-RC3/scala/http/client-side/request-level.html).
That flattens out the Futures and you get responses instead. That also
makes Balance actually aware
On Wed, May 27, 2015 at 2:01 PM, Endre Varga endre.va...@typesafe.com
wrote:
Hi,
Instead of Http.request, you should use the Flow returned by
Http.superPool() (see
http://doc.akka.io/docs/akka-stream-and-http-experimental/1.0-RC3/scala/http/client-side/request-level.html).
That flattens out
Hi Sam,
27 maj 2015 kl. 12:01 skrev Sam Halliday sam.halli...@gmail.com:
Hi Roland,
On Wednesday, 27 May 2015 08:18:09 UTC+1, rkuhn wrote:
For this venture you need no HTTP documentation
Actually I'd like to go futher than akka-http and see documentation that
allows me to use
Ok. I understand. Thank you for your work, good luck.
среда, 27 мая 2015 г., 14:49:10 UTC+3 пользователь drewhk написал:
Hi,
At the current point the aim of streams 1.0 was to reach a desired
functionality level. Basically there is zero performance work done at this
point. We will improve
On Wednesday, 27 May 2015 14:01:46 UTC+1, rkuhn wrote:
Maybe I misunderstand you still, but ConnectionManager is not something
that we have in Akka HTTP
I am referring to the `manager` field in an implementation of
`akka.io.IO.Extension`. The limitation that I'm referring to lies with
Hi Tim,
This looks great - I was just thinking of implementing something like this
myself, so the timing couldn't have been better. ^_^
I do have a couple of questions, though.
From what I see in AsyncAckingConsumer, the default error handling strategy
is to acknowledge the message once the
On Wed, May 27, 2015 at 2:33 PM, Viktor Klang viktor.kl...@gmail.com
wrote:
On Wed, May 27, 2015 at 2:01 PM, Endre Varga endre.va...@typesafe.com
wrote:
Hi,
Instead of Http.request, you should use the Flow returned by
Http.superPool() (see
I will file an issue.
The problem would exist and even be amplified by long-polling GET requests,
as they would be seen as idempotent. Moreover, in Akka it looks like
disabling pipelining (setting it to 1) might not be enough if the
connection is seen as idle, at least it didn't work for me.
I added Http().superPool() to my implementation, but performance is still
low. Performance does not increase after adding third server. It seems
strange to me.
Adam, yeah we have a reason not to use nginx or something similar, because
there will be an additional business logic, not only load
I probably confused the readers with my long explanation so I'll ask the
question straight forward: If I have a cluster with one seed node, how do I
make the cluster reconnect to that seed node if I restart it? Is there any
resilient configuration I'm not aware of that can make the other nodes
I'm working with an akka-http application that takes in a POST request and
needs to convert the body to a java.io.InputStream. Specifically, I need to
go from a Source[akka.util.ByteString, Any] (which is what
request.entity.dataBytes returns) to a java.io.InputStream. I can't seem to
find the
Hi Samuel,
what you describe sounds like a bug, and I think I know how it arises as well.
Would you please file an issue with this log and explanation? Thanks!
Independently, it seems that you are pointing out an overall problematic
relation between pipelining and long-running HTTP/1.1
Hi Shawn,
On Mon, May 25, 2015 at 4:29 PM, Shawn Garner shawndgar...@gmail.com
wrote:
The arbiter sounds like what we would need.
Are there any activator templates or example of someone using an arbiter
in Akka you can point me to?
This way I could demo it to my coworker without having to
Is there a specific reason to not use another piece of software for this?
I'm thinking of something like nginx or haproxy. Both of which are much
more hardened and performant in regards to serving as proxies for HTTP
traffic.
On Wed, May 27, 2015 at 7:34 AM, Viktor Klang viktor.kl...@gmail.com
On 05/23/15 11:40, Mark Joslin wrote:
Hi Michael, thanks for the tips. I believe that would be a bit
overkill for this project though it would seem fun. I've decided to
take a pretty minimalistic approach:
* Start two seed nodes on AWS
* Have all the API servers connect to the cluster via
Hi.
Using Akka HTTP Streams 1.0-RC3 in Scala, I have the impression that a
connection can be used to pipeline another request even if a non-idempotent
request is being executed (vs. a non-idempotent request being completed). I
had the same problem in 1.0-RC2 but took no time to investigate.
The
One way is that in your seed node subscribe to cluster membership changes
and write the current set of nodes to a file. When you restart the seed
node you construct the list of seed nodes from the file, and include your
own address as the first element in the seed-nodes list. Then it will first
Yes, you’re missing InputStreamSink
https://github.com/akka/akka/issues/17338. It is not terribly complicated to
write, I think, but we have not yet gotten around to it.
Regards,
Roland
27 maj 2015 kl. 21:20 skrev Michael Hamrah mham...@gmail.com:
I'm working with an akka-http application
Hi Oliver,
we do not (currently) support distributed materialization of streams.
The reason is that it will require implementing redelivery for stream
messages and a number of related issues which need to be fixed, which has
not happened yet.
Currently we are focusing on getting the 1.0 out the
I'm already using http/streams in a minor component, but since you're
talking about this: do you have a rough idea of when the performance
improvement work will start? Of course I'm not talking about the exact day
but it would be very useful to know if we can expect something by the end
of the
Hi Sam,
it might be better to take a step back before potentially running in the wrong
direction. First off, Akka HTTP offers a complete solution for everything HTTP
(including websockets) within an ActorSystem. Before deciding to combine this
with another tool I recommend that you explore
Frown upon mocks in actor testing, though they do have their place.
This use case is perfect for mocks because the
LogReaderDisruptor main(Array())
is long running process (which will continue to run forever.
To give you some context, LogReaderDisruptor is entry to our current
project
26 maj 2015 kl. 14:54 skrev Sam Halliday sam.halli...@gmail.com:
Hi all,
I need to interface an Actor with an API that requires a Flow.
The actor can receive a sealed trait family of inputs and will only send (a
different) sealed family of outputs to upstream, so I suspect that will
26 maj 2015 kl. 16:02 skrev Sam Halliday sam.halli...@gmail.com:
To maybe try and formalise this a little bit more, and abstract away from
WebSockets (that will only muddy the water).
Lets say we have an Actor already that looks like this
sealed trait Incoming
sealed trait Outgoing
Hi Roland,
I've read the documentation, several times, I've even given you feedback on
the documentation in an earlier milestone phase. Also, the documentation
for WebSockets in Akka is TODO and TODO. The documentation on the routing
directives are extremely sparse. In particular, there are no
Simple question: you have a faucet and a drain and you want to get the water
from one to the other without spilling any, how do you do that? Of course you
connect the two with a hose, and you do so while making sure that everything is
tight. That way the pressure in the faucet will be relieved
Hi,
btw can Stage by stateful? Is R/W from/to this in a PushPullStage thread
safe?
var state : Map[A,Cancellable] = Map.empty
Thanks, Jakub
On Friday, January 23, 2015 at 2:42:11 AM UTC+1, Frank Sauer wrote:
Thanks for the pointers Endre, I’ll explore those ideas.
Frank
On Jan 22,
Hi,
I'm going to use akka.persistence in production. Is it ready? What are more
stable alternatives?
Thanks
Amir
--
Read the docs: http://akka.io/docs/
Check the FAQ:
http://doc.akka.io/docs/akka/current/additional/faq.html
Search the archives:
I need to run a static method on a Java class (provided as a jar
dependency).
I also wanted to be able to write test on that. I created a wrapper class
in Scala that will call this method. It looks like
object CurrentLogProcessor {
}
class CurrentLogProcessor {
def run: Unit =
I have a single Akka node running local to my machine. It seems to join
itself fine. Messages never make it to the sharded actors and I can't tell
if they are created. Code and logs below, thanks in advance.
application.conf:
akka {
actor {
provider = akka.cluster.ClusterActorRefProvider
On May 27, 2015, at 07:47, Tal Pressman kir...@gmail.com wrote:
Hi Tim,
This looks great - I was just thinking of implementing something like this
myself, so the timing couldn't have been better. ^_^
Glad to hear it!
I do have a couple of questions, though.
From what I see in
27 maj 2015 kl. 08:51 skrev Sam Halliday sam.halli...@gmail.com:
Hi Roland,
I've read the documentation, several times, I've even given you feedback on
the documentation in an earlier milestone phase. Also, the documentation for
WebSockets in Akka is TODO and TODO. The documentation on
You need both an implicit FlowMaterializer and an implicit
ExecutionContext in scope. I haven't followed the chain to check why those
are needed but basically I keep adding them (one or the other or both)
wherever I have compilation errors and it works. It should be something
related to
Well, since I'm here, let me ask: all the marshalling code requires an
execution context (I can see that), but why a materializer? I can't find
where the implicit mat is needed anywhere
Thanks
G
On Wednesday, 27 May 2015 09:21:37 UTC+2, Giovanni Alberto Caporaletti
wrote:
You need both an
Got it! Sorry for the spam:
implicit def defaultUrlEncodedFormDataUnmarshaller(implicit fm:
FlowMaterializer): FromEntityUnmarshaller[FormData]
FYI: To find this I had to create fake methods with the implicit parameters
required from the code (e.g. def x()(implicit a: FromEntityUnmarshaller
42 matches
Mail list logo
