-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I have issue with memory #8
Comments
================================================================================ Environment Variables: /proc/meminfo: container (cgroup) information: CPU:total 16 (initial active 16) (16 cores per cpu, 1 threads per core) family 6 model 6 stepping 3, cmov, cx8, fxsr, mmx, sse, sse2, sse3, tsc ================================================================================ |
Hi Son, Could you please update issue with output of Regards, |
Hi Aleksej, Regards, |
Thanks! Please provide value of KAFKA_OPTS environment variable for connector Regards, |
Hi Aleksej, Regards, |
Please set
remove transaction files and oracdc.state and retest issue Regards, |
Thanks Aleksej, |
Hi Aleksej, [2020-11-10 14:34:05,898] WARN Took 844228 to add mapping for /data/oracdc/trans/0D570012001F27A5.5260993472897430974/metadata.cq4t (net.openhft.chronicle.bytes.MappedFile:42) Regards, |
Hi Son,
and update this issue with query output Regards, |
Hi Aleksej, select count() from ERP.PM_OUTPUTVOUCHER;
|
Hi Son, This is definitely not software or software configuration issue. Sending more than 150GiB table through Kafka is not good solution. As we discussed before in e-mail loop the right way is: If you do not like to use data migration best practices and belief in a miracle:
Regards, |
Thanks Aleksej, Maybe I'll trying with JDK11. I need test initload to Kafka. Regards, |
Hi Son, oracdc initial load is not designed to handle tables of such size as your ERP.PM_OUTPUTVOUCHER with half billion rows and more than 150GiB size Regards, |
Thanks Aleksej, Regards, |
Hi Aleksej, Regards, |
Hi Son, This is different issue. You need to try with JDK11 without setting KAFKA_HEAP_OPTS/KAFKA_OPTS environment variables. Regards, |
Hi Aleksej, Regards, |
Hi Aleksej, [2020-11-10 21:10:08,609] INFO WorkerSourceTask{id=oracdc-oracle-ov-0} flushing 0 outstanding messages for offset commit (org.apache.kafka.connect.runtime.WorkerSourceTask:443) Regards, |
Mea culpa!
Please set
and try again Regards, |
Ok, Thanks Aleksej. I'm trying again... |
Hi Son, Could you please provide output of following commands:
Thanks. |
Hi Aleksej, [root@oracdc46 ~]# cat /proc/sys/vm/max_map_count Regards, |
Hi Aleksej, jvm.args = -Xms32G, -Xmx32G, -XX:MaxDirectMemorySize=200G, -XX:+UseG1GC, -XX:MaxGCPauseMillis=20, -XX:InitiatingHeapOccupancyPercent=35, -XX:+ExplicitGCInvokesConcurrent, -XX:MaxInlineLevel=15, -Djava.awt.headless=true, -Dcom.sun.management.jmxremote, -Dcom.sun.management.jmxremote.authenticate=false, -Dcom.sun.management.jmxremote.ssl=false, -Dkafka.logs.dir=/data/kafka/bin/../logs, -Dlog4j.configuration=file:/data/kafka/bin/../etc/kafka/connect-log4j.properties [2020-11-11 09:37:59,684] INFO WorkerSourceTask{id=oracdc-oracle-ov-0} flushing 0 outstanding messages for offset commit (org.apache.kafka.connect.runtime.WorkerSourceTask:443) [2020-11-11 10:03:49,790] INFO WorkerSourceTask{id=oracdc-oracle-ov-0} flushing 0 outstanding messages for offset commit (org.apache.kafka.connect.runtime.WorkerSourceTask:443) There is insufficient memory for the Java Runtime Environment to continue.Native memory allocation (mmap) failed to map 65536 bytes for committing reserved memory.An error report file with more information is saved as:/data/kafka/hs_err_pid13075.logCompiler replay data is saved as:/data/kafka/replay_pid13075.logRegards, |
Hi Son, Please upload /data/kafka/hs_err_pid13075.log Regards, |
Hi Aleksej, Regards, |
Hi Son,
Regards, |
Thanks Aleksej, I'm waiting result |
Hi Son, You need to decrease heap as I write! Regards, |
Thanks Aleksej, |
Hi Aleksej, Regards, |
Morning Aleksej,
Have nice a day!
Can you help me?
I have issue with memory
Java HotSpot(TM) 64-Bit Server VM warning: INFO: os::commit_memory(0x00007f2c1f6bd000, 262144, 0) failed; error='Cannot allocate memory' (errno=12)
There is insufficient memory for the Java Runtime Environment to continue.
Native memory allocation (mmap) failed to map 262144 bytes for committing reserved memory.
An error report file with more information is saved as:
/data/kafka/bin/hs_err_pid9147.log
Compiler replay data is saved as:
/data/kafka/bin/replay_pid9147.log
hs_err_pid9147.log
replay_pid9147.log
Regards,
Son
The text was updated successfully, but these errors were encountered: