Richard Howell

I am getting this exact same issue, but I do not use Docker and am using SymmetricDS 3.10. Server: ubuntu@ip-172-31-32-215:/usr/local/symmetric-server-3.10.0/logs$ 2022-11-08 20:03:56,630 INFO [cloud-99998] [DataLoaderService] [qtp339099861-220452757] 61 data and 1 batches loaded during push request from site:00076:00076. ubuntu@ip-172-31-32-215:/usr/local/symmetric-server-3.10.0/logs$ 2022-11-08 20:03:57,603 ERROR [cloud-99998] [RouterService] [cloud-99998-job-8] Failed to route and batch data on...

I am getting this exact same issue, but I do not use Docker and am using SymmetricDS 3.10. Server: ubuntu@ip-172-31-32-215:/usr/local/symmetric-server-3.10.0/logs$ 2022-11-08 20:03:56,630 INFO [cloud-99998] [DataLoaderService] [qtp339099861-220452757] 61 data and 1 batches loaded during push request from site:00076:00076. ubuntu@ip-172-31-32-215:/usr/local/symmetric-server-3.10.0/logs$ 2022-11-08 20:03:57,603 ERROR [cloud-99998] [RouterService] [cloud-99998-job-8] Failed to route and batch data on...

I am getting this exact same issue, but I do not use Docker and am using SymmetricDS 3.10. Server: ubuntu@ip-172-31-32-215:/usr/local/symmetric-server-3.10.0/logs$ 2022-11-08 20:03:56,630 INFO [cloud-99998] [DataLoaderService] [qtp339099861-220452757] 61 data and 1 batches loaded during push request from site:00076:00076. ubuntu@ip-172-31-32-215:/usr/local/symmetric-server-3.10.0/logs$ 2022-11-08 20:03:57,603 ERROR [cloud-99998] [RouterService] [cloud-99998-job-8] Failed to route and batch data on...

I am getting this exact same issue, but I do not use Docker and am using SymmetricDS 3.10. Server: ubuntu@ip-172-31-32-215:/usr/local/symmetric-server-3.10.0/logs$ 2022-11-08 20:03:56,630 INFO [cloud-99998] [DataLoaderService] [qtp339099861-220452757] 61 data and 1 batches loaded during push request from site:00076:00076. ubuntu@ip-172-31-32-215:/usr/local/symmetric-server-3.10.0/logs$ 2022-11-08 20:03:57,603 ERROR [cloud-99998] [RouterService] [cloud-99998-job-8] Failed to route and batch data on...

That's funny you mention that, I was just comparing it to the other defaults wondering why it was initially set to "10000," with the default being 60. While we see batches send from the console/in the logs fairly quickly, I wasn't sure if it was instantiating too large of an object at once and possibly getting hammered if that was a multithreaded process. The difference in this case compared to a typical scenario, I suppose, is how many nodes we have online now (a few more) as well as all of them...

That's funny you mention that, I was just comparing it to the other defaults wondering why it was initially set to "10000," with the default being 60. While we see batches send from the console/in the logs fairly quickly, I wasn't sure if it was instantiating too large of an object at once and possibly getting hammered if that was a multithreaded process. The difference in this case compared to a typical scenario, I suppose, is how many nodes we have online now (a few more) as well as all of them...

That's funny you mention that, I was just comparing it to the other defaults wondering why it was initially set to "10000," with the default being 60. While we see batches send from the console/in the logs fairly quickly, I wasn't sure if it was instantiating too large of an object at once and possibly getting hammered if that was a multithreaded process. Our queue is defaulted (25?) Thanks for the feedback on this.

I am running symmetric server 3.10.0 on a t2.micro (1gb memory) EC2 instance on AWS, mostly because it was free of charge when I spun it up. The other day we experienced our first EC2 crash and pulled this information from within the sym logs: There is insufficient memory for the Java Runtime Environment to continue. #Native memory allocation (mmap) failed to map 113512448 bytes for committing reserved memory. I'm sure it's entirely scenario specific, but would bringing on a few more client nodes...