date:20160730

[akka-user] Re: Microservices Architecture with AKKA Cluster

2016-07-30 Thread Dagny T

Hi Maatary,

Just an update that I had got from the Akka Team on my original stab at an 
implementation for this using those (apparently outdated) Activator 
Templates:

"The tweet publisher is the glue from the eventStream to Akka Streams. As 
you say, there are other ways of doing this. For example passing a 
Source.queue to the TweetActor and let it publish into that instead of 
eventStream -> ActorPublisher. In general I think you should avoid the 
ActorPublisher and ActorSubscriber if you can, and if you can't then a 
custom GraphStage may anyways be a better solution as the APIs look today."

So, I went ahead to create an experimental GraphDSL that does a fan 
out/then merge within a local module (i.e. no cross-network HTTP and 
Websocket calls); and will just proceed with adding the cross-network 
connectivity based on that API.  This is with my general assumption that 
this DSL encapsulates underyling implicit Actors -- thus making 
ActorPublisher and ActorSubscriber creation unnecessary.

Just wanted to make sure that you got this latest information from the Akka 
Team as well; so as not to waste your time!

Cheers!
D

On Friday, July 15, 2016 at 9:03:05 AM UTC-7, Maatary Okouya wrote:
>
> Hi,
>
> given that Longom is not working to Scala anytime soon. I wonder if 
> someone could share with some good content on how build a good microservice 
> architecture with AKKA including Recommendation, best practices, things to 
> avoid and so on. 
>
>
> Or if someone as experiences and want to share it here that would be 
> grate. 
>
>
> For instance what are the layer involves from database up to the REST 
> Layer and so on. 
>
>
>

-- 
>>  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 because you are subscribed to the Google Groups "Akka 
User List" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to akka-user+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at https://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

Re: [akka-user] Get ActorSystem as part of a stream materialization process

2016-07-30 Thread Konrad Malawski

(feel free to copy paste the entire impl and use as-is if you want to btw)

-- 
Konrad `ktoso` Malawski
Akka  @ Lightbend 

On 31 July 2016 at 00:52:56, Konrad Malawski (konrad.malaw...@lightbend.com)
wrote:

I like the idea, this can indeed be very useful!
We'll see what the rest of the team has to say about it.

I took a shot at implementing it actually, so here it is:
https://github.com/akka/akka/pull/21076

No guarantees about bug-free ness, but it seems rather complete ;-)

It also shows of how awesome GraphStage really is, esp. with it's
StageActor feature which we'll blog about more in the near future.
Just yesterday we published a post introducing GraphStage a bit from a
birds view btw:
http://blog.akka.io/streams/2016/07/30/mastering-graph-stage-part-1
Track the blog if you want to learn interesting stuff about internals like
that :-)

Happy hakking!

-- 
Konrad `ktoso` Malawski
Akka  @ Lightbend 

On 30 July 2016 at 23:19:17, Alexey S (kvr...@gmail.com) wrote:

I'm trying to bind stream life-cycle to an actor life-cycle (let's call it
master actor). In a sense that if the stream is destroyed - the master
actor receives some Termination message but stays alive, but if the actor
is destroyed - the stream has to be shut down as well.
When I construct part of the stream flow, that has to be responsible for
the logic above, I have only an ActorRef of the master actor I want bind
the stream life-cycle to.

Originally I wanted to do the following: during stream materialization I
get its KillSwitch and create an aux actor with KillSwitch and master
ActorRef as parameters. The aux actor will create a watch for the master
actor and kill the stream using KillSwitch, once master actor shuts down.

As an alternative I can probably create a branch in the flow, filter off
all the possible events/messages and attach the master actor as a
Sink.actorRef.

WDYT?

Thanks.

WBR,
Alexey

On Sat, Jul 30, 2016 at 1:41 PM, Konrad Malawski <
konrad.malaw...@lightbend.com> wrote:

> Not using safe APIs.
> But instead I'd turn around the question and ask what you're trying to
> achieve?
> Perhaps there's a cleaner way than reaching out to the ActorSystem.
>
> --
> Konrad `ktoso` Malawski
> Akka  @ Lightbend 
>
> On 30 July 2016 at 22:39:47, oleksiys (kvr...@gmail.com) wrote:
>
> Hi,
>
> is it possible to get access to the ActorSystem, that is being used to
> materialize the stream during materialization?
>
> Something like:
>
> Flow[String].viaMat(*ExposeActorSystemMat.instance*).mapMaterializedValue(actorSystem
> => doSomethingWithActorSystem(actorSystem))
>
> Thanks.
>
> WBR,
> Alexey
> --
> >> 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 because you are subscribed to the Google Groups
> "Akka User List" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to akka-user+unsubscr...@googlegroups.com.
> To post to this group, send email to akka-user@googlegroups.com.
> Visit this group at https://groups.google.com/group/akka-user.
> For more options, visit https://groups.google.com/d/optout.
>
>

-- 
>>  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 because you are subscribed to the Google Groups "Akka 
User List" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to akka-user+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at https://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

Re: [akka-user] Get ActorSystem as part of a stream materialization process

2016-07-30 Thread Konrad Malawski

I like the idea, this can indeed be very useful!
We'll see what the rest of the team has to say about it.

I took a shot at implementing it actually, so here it is:
https://github.com/akka/akka/pull/21076

No guarantees about bug-free ness, but it seems rather complete ;-)

It also shows of how awesome GraphStage really is, esp. with it's
StageActor feature which we'll blog about more in the near future.
Just yesterday we published a post introducing GraphStage a bit from a
birds view btw:
http://blog.akka.io/streams/2016/07/30/mastering-graph-stage-part-1
Track the blog if you want to learn interesting stuff about internals like
that :-)

Happy hakking!

-- 
Konrad `ktoso` Malawski
Akka  @ Lightbend 

On 30 July 2016 at 23:19:17, Alexey S (kvr...@gmail.com) wrote:

I'm trying to bind stream life-cycle to an actor life-cycle (let's call it
master actor). In a sense that if the stream is destroyed - the master
actor receives some Termination message but stays alive, but if the actor
is destroyed - the stream has to be shut down as well.
When I construct part of the stream flow, that has to be responsible for
the logic above, I have only an ActorRef of the master actor I want bind
the stream life-cycle to.

Originally I wanted to do the following: during stream materialization I
get its KillSwitch and create an aux actor with KillSwitch and master
ActorRef as parameters. The aux actor will create a watch for the master
actor and kill the stream using KillSwitch, once master actor shuts down.

As an alternative I can probably create a branch in the flow, filter off
all the possible events/messages and attach the master actor as a
Sink.actorRef.

WDYT?

Thanks.

WBR,
Alexey

On Sat, Jul 30, 2016 at 1:41 PM, Konrad Malawski <
konrad.malaw...@lightbend.com> wrote:

> Not using safe APIs.
> But instead I'd turn around the question and ask what you're trying to
> achieve?
> Perhaps there's a cleaner way than reaching out to the ActorSystem.
>
> --
> Konrad `ktoso` Malawski
> Akka  @ Lightbend 
>
> On 30 July 2016 at 22:39:47, oleksiys (kvr...@gmail.com) wrote:
>
> Hi,
>
> is it possible to get access to the ActorSystem, that is being used to
> materialize the stream during materialization?
>
> Something like:
>
> Flow[String].viaMat(*ExposeActorSystemMat.instance*).mapMaterializedValue(actorSystem
> => doSomethingWithActorSystem(actorSystem))
>
> Thanks.
>
> WBR,
> Alexey
> --
> >> 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 because you are subscribed to the Google Groups
> "Akka User List" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to akka-user+unsubscr...@googlegroups.com.
> To post to this group, send email to akka-user@googlegroups.com.
> Visit this group at https://groups.google.com/group/akka-user.
> For more options, visit https://groups.google.com/d/optout.
>
>

-- 
>>  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 because you are subscribed to the Google Groups "Akka 
User List" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to akka-user+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at https://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

Re: [akka-user] Get ActorSystem as part of a stream materialization process

2016-07-30 Thread Alexey S

I'm trying to bind stream life-cycle to an actor life-cycle (let's call it
master actor). In a sense that if the stream is destroyed - the master
actor receives some Termination message but stays alive, but if the actor
is destroyed - the stream has to be shut down as well.
When I construct part of the stream flow, that has to be responsible for
the logic above, I have only an ActorRef of the master actor I want bind
the stream life-cycle to.

Originally I wanted to do the following: during stream materialization I
get its KillSwitch and create an aux actor with KillSwitch and master
ActorRef as parameters. The aux actor will create a watch for the master
actor and kill the stream using KillSwitch, once master actor shuts down.

As an alternative I can probably create a branch in the flow, filter off
all the possible events/messages and attach the master actor as a
Sink.actorRef.

WDYT?

Thanks.

WBR,
Alexey

On Sat, Jul 30, 2016 at 1:41 PM, Konrad Malawski <
konrad.malaw...@lightbend.com> wrote:

> Not using safe APIs.
> But instead I'd turn around the question and ask what you're trying to
> achieve?
> Perhaps there's a cleaner way than reaching out to the ActorSystem.
>
> --
> Konrad `ktoso` Malawski
> Akka  @ Lightbend 
>
> On 30 July 2016 at 22:39:47, oleksiys (kvr...@gmail.com) wrote:
>
> Hi,
>
> is it possible to get access to the ActorSystem, that is being used to
> materialize the stream during materialization?
>
> Something like:
>
> Flow[String].viaMat(*ExposeActorSystemMat.instance*).mapMaterializedValue(actorSystem
> => doSomethingWithActorSystem(actorSystem))
>
> Thanks.
>
> WBR,
> Alexey
> --
> >> 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 because you are subscribed to the Google Groups
> "Akka User List" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to akka-user+unsubscr...@googlegroups.com.
> To post to this group, send email to akka-user@googlegroups.com.
> Visit this group at https://groups.google.com/group/akka-user.
> For more options, visit https://groups.google.com/d/optout.
>
>

-- 
>>  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 because you are subscribed to the Google Groups "Akka 
User List" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to akka-user+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at https://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

Re: [akka-user] Get ActorSystem as part of a stream materialization process

2016-07-30 Thread Konrad Malawski

Not using safe APIs.
But instead I'd turn around the question and ask what you're trying to
achieve?
Perhaps there's a cleaner way than reaching out to the ActorSystem.

-- 
Konrad `ktoso` Malawski
Akka  @ Lightbend 

On 30 July 2016 at 22:39:47, oleksiys (kvr...@gmail.com) wrote:

Hi,

is it possible to get access to the ActorSystem, that is being used to
materialize the stream during materialization?

Something like:

Flow[String].viaMat(*ExposeActorSystemMat.instance*).mapMaterializedValue(actorSystem
=> doSomethingWithActorSystem(actorSystem))

Thanks.

WBR,
Alexey
--
>> 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 because you are subscribed to the Google Groups
"Akka User List" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to akka-user+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at https://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

-- 
>>  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 because you are subscribed to the Google Groups "Akka 
User List" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to akka-user+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at https://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

[akka-user] Get ActorSystem as part of a stream materialization process

2016-07-30 Thread oleksiys

Hi,

is it possible to get access to the ActorSystem, that is being used to 
materialize the stream during materialization?

Something like:

Flow[String].viaMat(*ExposeActorSystemMat.instance*).mapMaterializedValue(actorSystem
 
=> doSomethingWithActorSystem(actorSystem))

Thanks.

WBR,
Alexey

-- 
>>  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 because you are subscribed to the Google Groups "Akka 
User List" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to akka-user+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at https://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

Re: [akka-user] Cassandra persistence - with Cassandra 2.2.7 + akka-persistence-cassandra-0.7 + akka 2.4.8 - not working

2016-07-30 Thread Justin du coeur

I see you got things working, which is great.  I just wanted to caution:

On Sat, Jul 30, 2016 at 8:29 AM, Muthukumaran Kothandaraman <
muthu.kmk2...@gmail.com> wrote:

> I assume my application.conf below is fine because I do not see any
> exceptions.
>

As a rule of thumb, this isn't a safe assumption.  Config-file format is
weakly typed, remember -- it's just strings -- and it does *not*
automatically detect errors.  Some mistakes will get caught by the relevant
libraries, but in general if you make a typo in the name, and the library
has a default value for that config key, the error will be silently
ignored...

-- 
>>  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 because you are subscribed to the Google Groups "Akka 
User List" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to akka-user+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at https://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

[akka-user] Re: Cassandra persistence - with Cassandra 2.2.7 + akka-persistence-cassandra-0.7 + akka 2.4.8 - not working [SOLVED]

2016-07-30 Thread Muthukumaran Kothandaraman

Moved to Cassandra version 3.7 and no other changes - it works now !

Just in case somebody is hitting same problem, this could be useful. 

Please note that this is purely localhost testing. Will start cluster 
testing sometime

Regards
Muthu




On Saturday, 30 July 2016 17:59:07 UTC+5:30, Muthukumaran Kothandaraman 
wrote:
>
> Hi, 
>
> With above combination I am getting following error while running a simple 
> PersistentActor. Checked compatibility on page - 
> https://github.com/akka/akka-persistence-cassandra 
>
> Will give a try with 
>
>
> [WARN] [07/30/2016 08:13:20.699] 
> [example-cassandra-journal.default-dispatcher-6] 
> [akka://example/system/cassandra-journal] Failed to connect to Cassandra 
> and initialize. It will be retried on demand. Caused by: line 2:13 no 
> viable alternative at input 'MATERIALIZED' (  [CREATE] MATERIALIZED...)
>
> Strangely, when I check the keyspaces and tables with cqlsh directly 
> connecting to Cassandra, I was able to see the keyspace named akka and 
> corresponding tables created by akka. So, I assume connectivity itself is 
> not an issue. 
> But, the table akka.messages is empty always and events do not get 
> populated. 
>
> Before trying with Cassandra  3.0.8 
> 
>  , 
> I would like to check if I am missing something. 
>
> I assume my application.conf below is fine because I do not see any 
> exceptions. I am using cassandra only for journals. In the initial run I am 
> not doing any explicit snapshotting from within actor. 
>
> akka.persistence.journal.plugin = "cassandra-journal"
> akka.persistence.snapshot-store.plugin = 
> "akka.persistence.snapshot-store.local"
>
> akka.persistence.snapshot-store.local.dir = "target/example/snapshots"
>
> # DO NOT USE THIS IN PRODUCTION !!!
> # See also https://github.com/typesafehub/activator/issues/287
> # akka.persistence.journal.leveldb.native = false
>
> # akka.persistence.journal.leveldb.fsync = off
>
> cassandra-journal {
>
>   # FQCN of the cassandra journal plugin
>   class = "akka.persistence.cassandra.journal.CassandraJournal"
>
>   # Comma-separated list of contact points in the cluster
>   contact-points = ["127.0.0.1"]
>
>   # Port of contact points in the cluster
>   port = 9042
>
>   # Name of the keyspace to be created/used by the journal
>   keyspace = "akka"
>
>   # Parameter indicating whether the journal keyspace should be auto created
>   keyspace-autocreate = true
>
>   # In case that schema creation failed you can define a number of retries 
> before giving up.
>   keyspace-autocreate-retries = 1
>
>   # The number of retries when a write request returns a TimeoutException or 
> an UnavailableException.
>   write-retries = 3
>
>   # Deletes are achieved using a metadata entry and then the actual messages 
> are deleted asynchronously
>   # Number of retries before giving up
>   delete-retries = 3
>
>   # Number of retries before giving up connecting to the cluster
>   connect-retries = 3
>
>   # Delay between connection retries
>   connect-retry-delay = 5s
>
>   # Name of the table to be created/used by the journal
>   table = "messages"
>
>   # Compaction strategy for the journal table
>   table-compaction-strategy {
> class = "SizeTieredCompactionStrategy"
>   }
>
>   # Name of the table to be created/used for storing metadata
>   metadata-table = "metadata"
>
>   # Name of the table to be created/used for journal config
>   config-table = "config"
>
>   # replication strategy to use. SimpleStrategy or NetworkTopologyStrategy
>   replication-strategy = "SimpleStrategy"
>
>   # Replication factor to use when creating a keyspace. Is only used when 
> replication-strategy is SimpleStrategy.
>   replication-factor = 1
>
>   # Replication factor list for data centers, e.g. ["dc1:3", "dc2:2"]. Is 
> only used when replication-strategy is NetworkTopologyStrategy.
>   data-center-replication-factors = []
>
>   # Write consistency level
>   write-consistency = "QUORUM"
>
>   # Read consistency level
>   read-consistency = "QUORUM"
>
>   max-message-batch-size = 200
>
>   # Target number of entries per partition (= columns per row).
>   # Must not be changed after table creation (currently not checked).
>   # This is "target" as AtomicWrites that span parition boundaries will 
> result in bigger partitions to ensure atomicity.
>   target-partition-size = 50
>
>   # Maximum size of result set
>   max-result-size = 50001
>
>   # Dispatcher for the plugin actor.
>   plugin-dispatcher = "cassandra-journal.default-dispatcher"
>
>   # Dispatcher for fetching and replaying messages
>   replay-dispatcher = "akka.persistence.dispatchers.default-replay-dispatcher"
>
>   # Default dispatcher for plugin actor.
>   default-dispatcher {
> type = Dispatcher
> executor = "fork-join-executor"
> fork-join-executor {
>   parallelism-min = 2
>   parallelism-max = 8
> }
>   }
>
>   # The time to

[akka-user] Cassandra persistence - with Cassandra 2.2.7 + akka-persistence-cassandra-0.7 + akka 2.4.8 - not working

2016-07-30 Thread Muthukumaran Kothandaraman

Hi, 

With above combination I am getting following error while running a simple 
PersistentActor. Checked compatibility on page - 
https://github.com/akka/akka-persistence-cassandra 

Will give a try with 


[WARN] [07/30/2016 08:13:20.699] 
[example-cassandra-journal.default-dispatcher-6] 
[akka://example/system/cassandra-journal] Failed to connect to Cassandra 
and initialize. It will be retried on demand. Caused by: line 2:13 no 
viable alternative at input 'MATERIALIZED' (  [CREATE] MATERIALIZED...)

Strangely, when I check the keyspaces and tables with cqlsh directly 
connecting to Cassandra, I was able to see the keyspace named akka and 
corresponding tables created by akka. So, I assume connectivity itself is 
not an issue. 
But, the table akka.messages is empty always and events do not get 
populated. 

Before trying with Cassandra  3.0.8 

 , 
I would like to check if I am missing something. 

I assume my application.conf below is fine because I do not see any 
exceptions. I am using cassandra only for journals. In the initial run I am 
not doing any explicit snapshotting from within actor. 

akka.persistence.journal.plugin = "cassandra-journal"
akka.persistence.snapshot-store.plugin = "akka.persistence.snapshot-store.local"

akka.persistence.snapshot-store.local.dir = "target/example/snapshots"

# DO NOT USE THIS IN PRODUCTION !!!
# See also https://github.com/typesafehub/activator/issues/287
# akka.persistence.journal.leveldb.native = false

# akka.persistence.journal.leveldb.fsync = off

cassandra-journal {

  # FQCN of the cassandra journal plugin
  class = "akka.persistence.cassandra.journal.CassandraJournal"

  # Comma-separated list of contact points in the cluster
  contact-points = ["127.0.0.1"]

  # Port of contact points in the cluster
  port = 9042

  # Name of the keyspace to be created/used by the journal
  keyspace = "akka"

  # Parameter indicating whether the journal keyspace should be auto created
  keyspace-autocreate = true

  # In case that schema creation failed you can define a number of retries 
before giving up.
  keyspace-autocreate-retries = 1

  # The number of retries when a write request returns a TimeoutException or an 
UnavailableException.
  write-retries = 3

  # Deletes are achieved using a metadata entry and then the actual messages 
are deleted asynchronously
  # Number of retries before giving up
  delete-retries = 3

  # Number of retries before giving up connecting to the cluster
  connect-retries = 3

  # Delay between connection retries
  connect-retry-delay = 5s

  # Name of the table to be created/used by the journal
  table = "messages"

  # Compaction strategy for the journal table
  table-compaction-strategy {
class = "SizeTieredCompactionStrategy"
  }

  # Name of the table to be created/used for storing metadata
  metadata-table = "metadata"

  # Name of the table to be created/used for journal config
  config-table = "config"

  # replication strategy to use. SimpleStrategy or NetworkTopologyStrategy
  replication-strategy = "SimpleStrategy"

  # Replication factor to use when creating a keyspace. Is only used when 
replication-strategy is SimpleStrategy.
  replication-factor = 1

  # Replication factor list for data centers, e.g. ["dc1:3", "dc2:2"]. Is only 
used when replication-strategy is NetworkTopologyStrategy.
  data-center-replication-factors = []

  # Write consistency level
  write-consistency = "QUORUM"

  # Read consistency level
  read-consistency = "QUORUM"

  max-message-batch-size = 200

  # Target number of entries per partition (= columns per row).
  # Must not be changed after table creation (currently not checked).
  # This is "target" as AtomicWrites that span parition boundaries will result 
in bigger partitions to ensure atomicity.
  target-partition-size = 50

  # Maximum size of result set
  max-result-size = 50001

  # Dispatcher for the plugin actor.
  plugin-dispatcher = "cassandra-journal.default-dispatcher"

  # Dispatcher for fetching and replaying messages
  replay-dispatcher = "akka.persistence.dispatchers.default-replay-dispatcher"

  # Default dispatcher for plugin actor.
  default-dispatcher {
type = Dispatcher
executor = "fork-join-executor"
fork-join-executor {
  parallelism-min = 2
  parallelism-max = 8
}
  }

  # The time to wait before cassandra will remove the thombstones created for 
deleted entries.
  # cfr. gc_grace_seconds table property documentation on 
http://www.datastax.com/documentation/cql/3.1/cql/cql_reference/tabProp.html
  gc-grace-seconds = 864000
}


-- 
>>  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 because you are subscribed to the Google Groups "Akka

[akka-user] Re: Microservices Architecture with AKKA Cluster

Re: [akka-user] Get ActorSystem as part of a stream materialization process

Re: [akka-user] Get ActorSystem as part of a stream materialization process

Re: [akka-user] Get ActorSystem as part of a stream materialization process

Re: [akka-user] Get ActorSystem as part of a stream materialization process

[akka-user] Get ActorSystem as part of a stream materialization process

Re: [akka-user] Cassandra persistence - with Cassandra 2.2.7 + akka-persistence-cassandra-0.7 + akka 2.4.8 - not working

[akka-user] Re: Cassandra persistence - with Cassandra 2.2.7 + akka-persistence-cassandra-0.7 + akka 2.4.8 - not working [SOLVED]

[akka-user] Cassandra persistence - with Cassandra 2.2.7 + akka-persistence-cassandra-0.7 + akka 2.4.8 - not working

9 matches

Site Navigation

Mail list logo

Footer information