Open starx1000 opened 8 months ago
I did reproduce some problems but since I am working on a major refactoring of these subscriptions, it does not make much sense fixing this. Once I am done, I will test this use-case as well but you will have to wait for several weeks, at least, until that,
That is ok, thank you!
before that I plan to turn off multi-threads by "-DTHREAD_COUNT=1 ".
Looks like this will workaround the issue. Do you see any side effects for "-DTHREAD_COUNT=1 "?
Yes, no parallel processing of RPCs/accepting new sessions. But other than that it should work fine.
@michalvasko I see new versions of netopeer2 is published, is this refactoring of subscriptions done in the latest published version Version 2.2.13?
thank you in advance.
Yes, the subscriptions were refactored so you can try it again. If you encounter any problems, please include a script or some way of reproducing the scenario.
OK, thank you. I will try and update you result..
hi, netopeer2-version Version 2.1.71 ( latest release) , sysrepo version 2.2.105. Tried with devel branch today, the issue is still there.
when multiple client(e.g 8) connects to netopeer2-server and use established-sub to subscribe for events (multiple streams e.g 10).
After all client connected and subscription established, kill 7 clients. then netopeer2-server will get dead with log prints like "[ERR]: SR: Locking a mutex failed (sr_subscr_del_id: Connection timed out)."
This issue will happen when the clients >= 2, it is 100% rate happen when have more clients connected.
stack is like below:
can you please help for this? thank you very much.