bilbolodz

Any idas fow to fix it?

I don't quite get it. Could you me please more precise? I did NOT remove any stageing files manually. My brief engine config bellow: engine.name=snapacs2a_expacs db.driver=org.postgresql.Driver db.url=jdbc:postgresql://X.X.X.X/expacs?stringtype=unspecified db.user=xxxxx db.password=yyyyy registration.url= sync.url=http://localhost:31415/sync/snapacs2a_expacs group.id=snapacs2a_ex job.purge.period.time.ms=600000 job.pull.period.time.ms=10000 auto.registration=true initial.load.create.first=true initial.load.defer.create.constraints=true...

SymmmetricDS 3.10.4, full stack bellow: 2019-09-01 03:44:18,530 INFO [snapacs2a_expacs] [RouterService] [snapacs2a_expacs-job-2] Routed 91 data events in 30 ms 2019-09-01 03:44:22,648 INFO [snapacs2db_expacs] [DataLoaderService] [qtp394785440-2025] 740000 data and 74 batches loaded during push request from snapacs2a_ex:004:004 2019-09-01 03:44:23,386 INFO [snapacs2a_expacs] [PushService] [snapacs2a_expacs-push-default-7] Pushed data to node snapacs2db_ex:005:005. 740000 data and 74 batches were processed....

Hudge database (1.4Tb), postgres to postgres migration. After a log time of copying data from source to target database extract proces stops and "reset" with such an error: 2019-09-01 03:44:28,784 INFO [snapacs2a_expacs] [DataExtractorService] [snapacs2a_expacs-dataextractor-311] Resetting status of request 11 to extract table instance into batches 1049 through 56695 for node 005 2019-09-01 03:44:29,409 ERROR [snapacs2a_expacs] [DataExtractorService] [snapacs2a_expacs-push-default-7] Failed to extract...

Just "for record": to get stage file choped into chunks "initial.load.use.extract.job.enabled" parmetr it has to be true. In other case (false) symmetric create one big file for a table. Still looking for method to limit number of created initial stage files or throthle "downloading" speed from source database into stage files.

I'd to restart migration because of strange errors, so I can repeat my questions: 1) How to force SymmetricDS to create smaller stage files (now one stage file is 30Gb and growing) 2) How to force SymmetricDS to limit number of stage file to avoid filling up the whole filesystem? The largest table in my database is neae 500Gb!

I'd to restart migration because of strange errors. I repeat my questions: 1) How to force SymmetricDS to create smaller stage files (now one stage file is 30Gb and growing) 2) How to force SymmetricDS to limit number of stage file to avoid filling up the whole filesystem? The largest table in my database is neae 500Gb!

Unfortunatelly it's not working in my case. I'd to remove constrains from tables in destination database. Fortunatelly it's only "one way synchrosization" so it was possible to do that.