After a bit more research on old post here on the forum, I came across a post (https://sourceforge.net/p/symmetricds/discussion/739236/thread/35ecb30c/) which describes the setting http.push.stream.output.enabled Basically, by setting this to true you enable chunked transfers. If you do not enable chunked transfers, the entire initial load will be attempted loaded into memory in the process of streaming it over http. I do not get the OOM errors anymore after http.push.stream.output.enabled has been...
I'm running a somewhat older version of Symmetric DS (v2.5) - but I'm not in a position to upgrade right now. I'm running inital load for a table which holds about 25 million rows. The initial load extraction from the seed node goes well, and a temporary file of about 3GB is created. Then, after a couple of minutes - I believe when the destination node pulls the initial load - the seed node starts reporting OOM errors. Xmx is set to 2048m on the seed node, and I can see that java maxes out all the...
I'm running a somewhat older version of Symmetric DS (v2.5) - but I'm not in a position to upgrade right now. I'm running inital load for a table which holds about 25 million rows. The initial load extraction from the seed node goes well, and a temporary file of about 3GB is created. Then, after a couple of minutes - I believe when the destination node pulls the initial load - the seed node starts reporting OOM errors. Xmx is set to 2048m on the seed node, and I can see that java maxes out all the...
I'm running a somewhat older version of Symmetric DS (v2.5) - but I'm not in a position to upgrade right now. I'm running inital load for a table which holds about 25 million rows. The initial load extraction from the seed node goes well, and a temporary file of about 3GB is created. Then, after a couple of minutes - I believe when the destination node pulls the initial load - the seed node starts reporting OOM errors. Xmx is set to 2048m, and I can see that java grabs all of this. What I don't understand...