Hi Liam I can’t reply to you directly. So I have to reply it here. We are running many kinds of customized connectors. Most of them are jdbc source and sink tasks. The error throws on the standalone KC.
Here is the output of ulimit [devops@gio_server4-21 ~]$ ulimit -a core file size (blocks, -c) 0 data seg size (kbytes, -d) unlimited scheduling priority (-e) 0 file size (blocks, -f) unlimited pending signals (-i) 63461 max locked memory (kbytes, -l) 64 max memory size (kbytes, -m) unlimited open files (-n) 65535 pipe size (512 bytes, -p) 8 POSIX message queues (bytes, -q) 819200 real-time priority (-r) 0 stack size (kbytes, -s) unlimited cpu time (seconds, -t) unlimited max user processes (-u) unlimited virtual memory (kbytes, -v) unlimited file locks (-x) unlimited Usually there are hundreds of open files [devops@gio_server4-21 ~]$ lsof -p 18580|wc -l 1028 But sometimes the the open file numbers can reach more than 36000 and even exceed the max open files And here is part of the listof -p 16862 output (16862 is the process id of ConnectStandalone) java 16862 devops 703w REG 253,1 0 397391 /tmp/connect.offsets java 16862 devops 704w REG 253,1 0 397391 /tmp/connect.offsets java 16862 devops 705w REG 253,1 0 397391 /tmp/connect.offsets java 16862 devops 706w REG 253,1 0 397391 /tmp/connect.offsets java 16862 devops 707w REG 253,1 0 397391 /tmp/connect.offsets java 16862 devops 708w REG 253,1 0 397391 /tmp/connect.offsets java 16862 devops 709w REG 253,1 0 397391 /tmp/connect.offsets java 16862 devops 710w REG 253,1 0 397391 /tmp/connect.offsets java 16862 devops 711w REG 253,1 0 397391 /tmp/connect.offsets java 16862 devops 712w REG 253,1 0 397391 /tmp/connect.offsets java 16862 devops 713w REG 253,1 0 397391 /tmp/connect.offsets java 16862 devops 714w REG 253,1 0 397391 /tmp/connect.offsets java 16862 devops 715w REG 253,1 0 397391 /tmp/connect.offsets java 16862 devops 716w REG 253,1 0 397391 /tmp/connect.offsets java 16862 devops 717w REG 253,1 0 397391 /tmp/connect.offsets java 16862 devops 718w REG 253,1 0 397391 /tmp/connect.offsets java 16862 devops 719w REG 253,1 0 397391 /tmp/connect.offsets java 16862 devops 720w REG 253,1 0 397391 /tmp/connect.offsets java 16862 devops 721w REG 253,1 0 397391 /tmp/connect.offsets java 16862 devops 722w REG 253,1 0 397391 /tmp/connect.offsets java 16862 devops 723w REG 253,1 0 397391 /tmp/connect.offsets Regars On 2021/05/13 02:20:47, Gu Haihua <g...@outlook.com> wrote: > Hi everyone> > > We have a kafka connect service, which runs in standalone mode. Recently, > there are too many tasks running on it, and sometimes too many open files > error will be thrown. Through the lsof command, it can be seen that there are > many commit.offsets files open.> > > $ lsof -p 16862|wc -l> > 36960> > > $ lsof -p 16862|grep connect.offsets|wc -l> > 36161> > > Does anyone know the reason?> > > Regards> > Haihua> >
