ostinelli / syn

A scalable global Process Registry and Process Group manager for Erlang and Elixir.

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Looks like nodes does not sync between each other

cystbear opened this issue · comments

Hi,

I am currently trying to setup Syn with 2-nodes cluster app. Here are steps to reproduce my case:

  • At first at my app start/2 I connect nodes between each other via net_kernel:connect/1;
  • Next I call syn:init/0 to initialize Syn itself;
  • After initialization during app is working, I call syn:join({user, UserId}, self(), [ %% META_HERE %%]).;
  • Later to check that everything synced, I call syn:get_members({user, UserId}, with_meta)., and get
    [{ <0.1234.0>, [ %% META_HERE %% ] }] at first server and [] at second one.

For sure node/0 and nodes/0 shows that my first and second nodes inside same cluster.

Furthermore if I manually shutdown one of node, other node echo this log message
Received a MNESIA down event, removing on node...
in my opinion this means that nodes been connected and Syn correctly handled shutting down one of them.

Please hint me what I do wrong, and possible way to bypass and/or debug this issue.
Also I can provide any additional information.

I just found the issue, I have some miss configuration of Mnesia
and got this error message during mnesia:change_config/2 at syn_backbone:initdb/0

Error message:

{error,{merge_schema_failed, "Bad cookie in table definition MY_TABLE_NAME... \n"}}

So, I tuned my Mnesia and everything is fine at the moment, related PR #36