Tom

By this article: https://www.jumpmind.com/blog/scaling-symmetricds-for-many-clients So.. If I have 200 nodes and set http.concurrent.workers.max=100 (db.pool.max.active=200), 100 nodes can push and pull at the same time right? But.. if I have for example 10 active channels, I have to divide this by 10 so only 10 nodes at the time? I am little confused here: Channel Queues - By default channels will push or pull in series. Using different channel queues allows the channels to then push or pull in...

By this article: https://www.jumpmind.com/blog/scaling-symmetricds-for-many-clients So.. If I have 200 nodes and set http.concurrent.workers.max=100 (db.pool.max.active=200), 100 nodes can push and pull at the same time right? But.. if I have for example 10 active channels, I have to divide this by 10 so only 10 nodes at the time? I am little confused here: Channel Queues - By default channels will push or pull in series. Using different channel queues allows the channels to then push or pull in...

By this article: https://www.jumpmind.com/blog/scaling-symmetricds-for-many-clients So.. If I have 200 nodes and set http.concurrent.workers.max=100 (db.pool.max.active=200), 100 nodes can push and pull at the same time right? But.. if I have for example 10 active channels, I have to divide this by 10 so only 10 nodes at the time? I am little confused here: Channel Queues - By default channels will push or pull in series. Using different channel queues allows the channels to then push or pull in...

By this article: https://www.jumpmind.com/blog/scaling-symmetricds-for-many-clients So.. If I have 200 nodes and set http.concurrent.workers.max=100 (db.pool.max.active=200), 100 nodes can push and pull at the same time right? But.. if I have for example 10 active channels, I have to divide this by 10 so only 10 nodes at the time? I am little confused here: Channel Queues - By default channels will push or pull in series. Using different channel queues allows the channels to then push or pull in...

Hello, I was wondering if there is some FAQ with general recommended configuration if SymmetricDS use many nodes (e.g. > 100, 200 nodes) on heavy load databases. From my experience, default configuration is quite fine with tens of nodes, but with hundred of nodes it can be quite tricky to choose right set up.. What I am interested in mostly is: a) Channels settings: - Max Batch Size - Max Batch To Send - Max Data To Route --> Is it better to use smaller/large values and when? (less but bigger data...

Firebird 3.0 is working fine with symmetric-3.9.7, it was mistake on our side sorry.. just setup properly firebird.config and user like in the link

Hello, is Firebird 3.0 with Jaybird 3.0.4 for last version of symmetric 3.9.7. supported please? In /symmetric-server-3.9.7/lib/ there is only jaybird-2.1.6.jar that seems quite old. Is possible to replace this with jaybird-3.0.4.jar or is this jaybird-2.1.6.jar still OK? (replace like simple copy or should I do more steps and rewrite some link somewhere from jaybird-2.1.6.jar to jaybird-3.0.4.jar somewhere in symmetric conf?? sorry dont use Java libs much so be grateful for help) After service start...

Hello, thanks for the reply. I will try upgrade when it is possible. Can you reproduce this issue in a separate environment with only 2 nodes? - I have seen this very rarely in other database with different table, there is one central node and about 4 target nodes. In total, this mostly happens when node is not active for some time (hours, days) and when there is more NE batches for this channel and table with more data rows in one batch (e.g more than 1000). Yes, and connection of these nodes are...