Thanks for your reply! We inevitably need to use "insert into" for BigFileBatch processing. Do you have any plans to improve this conflict mechanism? Best Wishes, ------------------------------ Qiaoqiao Sun office staff ASUS Technology --------- ...
Yes , it is running on the same host. From the server log. >>> Local ports: TCP:8080 TCP:10800 TCP:11211 TCP:47100 TCP:47500 ------------------------------ Rag ------------------------------
Hello! Are you sure that GridGain was running at the time, on the same host? Can you please enable verbose logging (ignite.sh -v, or -DIGNITE_QUIET=false) and share the >>> Local ports: line from log? Regards, ------------------------------ Ilya ...
It failed with the default port 11211 and 11212 as well control --activate WARNING: An illegal reflective access operation has occurred WARNING: Illegal reflective access by org.apache.ignite.internal.util.GridUnsafe$2 (file:/C:/Work/Raghav/Downloads/apache-ignite-2.9.0-bin/apache-ignite-2.9.0-bin/libs/ignite-core-2.9.0.jar) ...
Hello! As a workaround you can try MERGE INTO instead of INSERT INTO, since it would not produce and collect insert conflicts. You may also use smaller batches of INSERTs or increase the amount of available memory. Unfortunately, there is no mechanism ...
Either the content you're seeking doesn't exist or it requires proper authentication before viewing.