The 11 commands are running the confdc command in parallel:
/opt/confd/bin/confdc --yangpath /opt/adp/yang -c /tmp/yangArchive320787179/company-complete-ext.yang --use-description -o /models-from-db/fxs/company-complete-ext.fxs --yangpath /tmp/yangArchive320787179 --no-features &
/opt/confd/bin/confdc --yangpath /opt/adp/yang -c /tmp/yangArchive749676220/company-alice.yang --use-description -o /models-from-db/fxs/company-alice.fxs --yangpath /tmp/yangArchive749676220 --no-features &
/opt/confd/bin/confdc --yangpath /opt/adp/yang -c /tmp/yangArchive368855886/company-alice.yang --use-description -o /models-from-db/fxs/company-alice.fxs --yangpath /tmp/yangArchive368855886 &
/opt/confd/bin/confdc --yangpath /opt/adp/yang -c /tmp/yangArchive320787179/company-grouping.yang --use-description -o /models-from-db/fxs/company-grouping.fxs --yangpath /tmp/yangArchive320787179 &
/opt/confd/bin/confdc --yangpath /opt/adp/yang -c /tmp/yangArchive368855886/company-bob.yang --use-description -o /models-from-db/fxs/company-bob.fxs --yangpath /tmp/yangArchive368855886 --no-features &
/opt/confd/bin/confdc --yangpath /opt/adp/yang -c /tmp/yangArchive320787179/company-complete-ext.yang --use-description -o /models-from-db/fxs/company-complete-ext.fxs --yangpath /tmp/yangArchive320787179 --no-features &
/opt/confd/bin/confdc --yangpath /opt/adp/yang -c /tmp/yangArchive368855886/company-bob.yang --use-description -o /models-from-db/fxs/company-bob.fxs --yangpath /tmp/yangArchive368855886 --no-features &
/opt/confd/bin/confdc --yangpath /opt/adp/yang -c /tmp/yangArchive749676220/company-bob.yang --use-description -o /models-from-db/fxs/company-bob.fxs --yangpath /tmp/yangArchive749676220 &
/opt/confd/bin/confdc --yangpath /opt/adp/yang -c /tmp/yangArchive368855886/company-alice.yang --use-description -o /models-from-db/fxs/company-alice.fxs --yangpath /tmp/yangArchive368855886 &
/opt/confd/bin/confdc --yangpath /opt/adp/yang -c /tmp/yangArchive320787179/company-complete-ext-ext.yang --use-description -o /models-from-db/fxs/company-complete-ext-ext.fxs --yangpath /tmp/yangArchive320787179 --no-features &
/opt/confd/bin/confdc --yangpath /opt/adp/yang -c /tmp/yangArchive320787179/company-complete.yang --use-description -o /models-from-db/fxs/company-complete.fxs --yangpath /tmp/yangArchive320787179 --deviation /tmp/yangArchive320787179/company-complete-ext.yang --deviation /tmp/yangArchive320787179/company-complete-ext-ext.yang -F company-complete:implemented,some_cool_feature &
The result is as following:
bash-4.4$ Failed to create dirty io scheduler thread 8, error = 11
[3] Killed /opt/confd/bin/confdc --yangpath /opt/adp/yang -c /tmp/yangArchive368855886/company-alice.yang --use-description -o /models-from-db/fxs/company-alice.fxs --yangpath /tmp/yangArchive368855886
bash-4.4$
[1] Killed /opt/confd/bin/confdc --yangpath /opt/adp/yang -c /tmp/yangArchive320787179/company-complete-ext.yang --use-description -o /models-from-db/fxs/company-complete-ext.fxs --yangpath /tmp/yangArchive320787179 --no-features
[4] Aborted (core dumped) /opt/confd/bin/confdc --yangpath /opt/adp/yang -c /tmp/yangArchive320787179/company-grouping.yang --use-description -o /models-from-db/fxs/company-grouping.fxs --yangpath /tmp/yangArchive320787179
[5] Killed /opt/confd/bin/confdc --yangpath /opt/adp/yang -c /tmp/yangArchive368855886/company-bob.yang --use-description -o /models-from-db/fxs/company-bob.fxs --yangpath /tmp/yangArchive368855886 --no-features
bash-4.4$
[7] Done /opt/confd/bin/confdc --yangpath /opt/adp/yang -c /tmp/yangArchive368855886/company-bob.yang --use-description -o /models-from-db/fxs/company-bob.fxs --yangpath /tmp/yangArchive368855886 --no-features
bash-4.4$
[2] Done /opt/confd/bin/confdc --yangpath /opt/adp/yang -c /tmp/yangArchive749676220/company-alice.yang --use-description -o /models-from-db/fxs/company-alice.fxs --yangpath /tmp/yangArchive749676220 --no-features
[6] Done /opt/confd/bin/confdc --yangpath /opt/adp/yang -c /tmp/yangArchive320787179/company-complete-ext.yang --use-description -o /models-from-db/fxs/company-complete-ext.fxs --yangpath /tmp/yangArchive320787179 --no-features
[8] Done /opt/confd/bin/confdc --yangpath /opt/adp/yang -c /tmp/yangArchive749676220/company-bob.yang --use-description -o /models-from-db/fxs/company-bob.fxs --yangpath /tmp/yangArchive749676220
[9] Done /opt/confd/bin/confdc --yangpath /opt/adp/yang -c /tmp/yangArchive368855886/company-alice.yang --use-description -o /models-from-db/fxs/company-alice.fxs --yangpath /tmp/yangArchive368855886
[10]- Done /opt/confd/bin/confdc --yangpath /opt/adp/yang -c /tmp/yangArchive320787179/company-complete-ext-ext.yang --use-description -o /models-from-db/fxs/company-complete-ext-ext.fxs --yangpath /tmp/yangArchive320787179 --no-features
[11]+ Done /opt/confd/bin/confdc --yangpath /opt/adp/yang -c /tmp/yangArchive320787179/company-complete.yang --use-description -o /models-from-db/fxs/company-complete.fxs --yangpath /tmp/yangArchive320787179 --deviation /tmp/yangArchive320787179/company-complete-ext.yang --deviation /tmp/yangArchive320787179/company-complete-ext-ext.yang -F company-complete:implemented,some_cool_feature
There seems io scheduler error. Other error such as “Failed to create dirty cpu scheduler thread 3, error = 11” and “sys/common/erl_poll.c:440:wake_poller(): Failed to write to wakeup pipe fd=10: enomem (12)” also found in other tries. Confd 7.4 is used:
bash-4.4$ /opt/confd/bin/confdc --version
confd-7.4
bash-4.4$ /opt/confd/lib/confd/erts/bin/confd.smp -V
Erlang (SMP,ASYNC_THREADS) (BEAM) emulator version 10.7.1
In the script confdc of confd 7.3, we found the following lines which is removed in 7.4:
if [ -f ${BINDIR}/confd ]; then
smp=“-smp disable”
else
smp=“-smp enable”
fi
Does this mean SMP Erlang is run by default?
In the node which the docker container run, there are 8 cores:
$ grep processor /proc/cpuinfo | wc -l
8
And the resources allocated to this container by Kubernetes:
limits: cpu: 1000m memory: 250Mi requests: cpu: 50m memory: 50Mi
Would you please help us on run confdc in parallel? How many confdc commands can run in parallel? Is it decided by physical core number? or cpu or memory size limited by kubernetes?