Single machine replication about dynomite HOT 6 CLOSED

For some reason github did not register the reply, but I got a mail notification.

You shouldn't add the self ip (rack, dc and token) in the dyn_seeds, only the other nodes. Max

So I changed the config to this. But I get the same error.

dyn_o_mite:
  datacenter: dc1
  rack: rack1
  listen: 127.0.0.1:8101
  dyn_listen: 127.0.0.1:8102
  dyn_seeds:
   - 127.0.0.2:8101:rack1:dc1:101134286

  tokens: '12345678'
  servers:
  - 127.0.0.1:21201:1

from dynomite.

• The port in the dyn_seeds should be the dyn_listen.
• Note that, by default the Dynomite guys has choosen the port 8101 for internal communication and 8102, you switch the both.

A correct conf will be:

dyn_o_mite:
  datacenter: dc1
  rack: rack1
  listen: 127.0.0.1:8102
  dyn_listen: 127.0.0.1:8101
  dyn_seeds:
   - 127.0.0.2:8101:rack1:dc1:101134286

  tokens: '12345678'
  servers:
  - 127.0.0.1:21201:1

Then, you can connect your clients on the 8102 port.

from dynomite.

Thank you Max, that worked. I can the access written data from both dynomite instances. However, nothing seems replicated. Data is only stored at the memcachedb instance at 127.0.0.1:21201.

Is it possible to replicate every single write?

from dynomite.

This seems like a question rather than a bug. @krisskross are you still interested in continuing on this, or do you want us to close this issue?

from dynomite.

I will close this But please feel free to reopen if you need

from dynomite.

I too had the same problem in redis, data not replicated. Is that fixed? @krisskross @mfouilleul

from dynomite.