0

I set-up symmetricds ( version 3.7.3) to sync a few tables from a central database to two client database, the central and 1 of the client(client1) is in same region as the central, while the other client(client2) is on different region. Hence, central and client2 have different machine timezone. SymmetricDS was able to sync from central to client1, but was not able to sync from central to client2. I tried to move the database client2 to the same region as client1 and then it works. Is anyone having the same problem?

Boris Pavlović
  • 63,078
  • 28
  • 122
  • 148
ivanceras
  • 1,415
  • 3
  • 17
  • 28
  • Which databases are used? MySql, Postgres, Oracle... What's the stack trace of the exception thrown at central and client2 databases (meaning the SymmetricDs log) when client2 is running in another time zone? – Boris Pavlović Feb 12 '15 at 08:50
  • I'm using postgresql 9.3.5 in amazon RDS. The `central` and `client1` database is located in `us-east` while `client2` is located in `eu-west` – ivanceras Feb 12 '15 at 09:01
  • Cool! What's the exception you're getting when the sync is failing? – Boris Pavlović Feb 12 '15 at 10:11
  • One more thing, what's the DDL of `timestamp with time zone` columns? – Boris Pavlović Feb 12 '15 at 10:16
  • There wasn't really error logs. However, In `sym_outgoing_batch` I get entries that have 'NE' status instead for `client2` while 'OK' status for `client1`. Also, the columns of the table that I have to sync, didn't really contain timestamp columns. I'm just suspecting time difference between these machine was causing symmetricds to fail. – ivanceras Feb 12 '15 at 13:08
  • Hm... 'NE' status means new, not error, which would be status 'ER'. Check the symmetricDs logs on the central node to see if it can access the `client2`. – Boris Pavlović Feb 12 '15 at 16:27

0 Answers0