Thanks for the update. Yes, it should be done at startup.
On Wed, Dec 21, 2016 at 9:36 PM, Víctor Martínez
wrote:
> Hi,
>
>
>
> Finally, I have the solution. When the sharding is created in the request
> the sharding fail. If I start the cluster in main all work
Sure, I have:
val extractEntityId: ShardRegion.ExtractEntityId = {
case (id: String, cmd: Command) => {
(id, cmd)
};
}
val numberOfShards = 4
val extractShardId: ShardRegion.ExtractShardId = {
case (generateId: String, cmd: Command) => {
val uuidLong: Long =
Do you start it on all nodes?
ClusterSharding(system).start(...)
On Tue, Dec 20, 2016 at 4:01 PM, Víctor Martínez
wrote:
> I turn on the logs in both nodes but just the younger print information.
> The logs is:
>
> [DEBUG] [12/20/2016 14:54:48.913]
>
I turn on the logs in both nodes but just the younger print information.
The logs is:
[DEBUG] [12/20/2016 14:54:48.913]
[ClusterSystem-akka.actor.default-dispatcher-4]
[akka.tcp://ClusterSystem@172.19.0.3:2551/system/IO-TCP/selectors/$a/0] New
connection accepted
[DEBUG] [12/20/2016
Try to turn on debug log level then. Must be something wrong with the setup.
mån 19 dec. 2016 kl. 22:54 skrev Víctor Martínez :
> Yes, I have persistence working fine. I tried with “ddata” and
> “persistence” with Cassandra. The node 172.19.0.2 don’t print any log.
Yes, I have persistence working fine. I tried with “ddata” and
“persistence” with Cassandra. The node 172.19.0.2 don’t print any log. Why
the coordinator just startup when an actor is creating inside the node
.2(Oldest)?
Thanks,
Víctor
El lunes, 19 de diciembre de 2016, 16:15:17
Any errors in the log of 172.19.0.2:2551 ?
Do you have persistence working there, otherwise the coordinator will not
be able to startup.
On Mon, Dec 19, 2016 at 3:08 PM, Víctor Martínez
wrote:
> Hi Patrick,
>
> Thanks for your answer but the problem is other. Before
Hi Patrick,
Thanks for your answer but the problem is other. Before to start the actor
it try to create the shard coordinator. The log of that is:
[DEBUG] [12/19/2016 14:00:18.735] [main]
[AkkaSSLConfig(akka://ClusterSystem)] Initializing AkkaSSLConfig
extension...
[DEBUG] [12/19/2016
Hi Patrick,
Thanks for your answer but the problem is other. Before to start the actor
it try to create the shard coordinator. The log of that is:
[DEBUG] [12/19/2016 14:00:18.735] [main]
[AkkaSSLConfig(akka://ClusterSystem)] Initializing AkkaSSLConfig
extension...
[DEBUG]
Hi Patrick,
Thanks for your answer but the problem is other. Before to start the actor
it try to create the shard coordinator. The log of that is:
[DEBUG] [12/19/2016 14:00:18.735] [main]
[AkkaSSLConfig(akka://ClusterSystem)] Initializing AkkaSSLConfig
extension...
[DEBUG]
Perhaps you haven't joined the cluster?
http://doc.akka.io/docs/akka/2.4/scala/cluster-usage.html#Joining_to_Seed_Nodes
On Fri, Dec 16, 2016 at 11:04 PM, Víctor Martínez wrote:
> Hi,
>
>
> Hi,
>
>
>
> In my test I have two nodes in cluster. The problem is the
Hi,
Hi,
In my test I have two nodes in cluster. The problem is the sharding
coordinator. When a younger node try to send a message just print.
[akka.tcp://ClusterSystem@localhost:2551/system/sharding/latamautos] Trying
to register to coordinator at [None], but no acknowledgement.
12 matches
Mail list logo