zbentley commented on issue #127: URL: https://github.com/apache/pulsar-client-python/issues/127#issuecomment-1572982175
A workaround that seemed effective at the application layer was to intentionally leak Client objects into a global in the child processes (an atfork child handler that appends them to a global array that's never emptied, and should be GC'd at interpreter shutdown but not before then). Could something similar be done inside the client? Perhaps by tracking constructing PID and short-circuiting/no-opping destructor calls if the destructing PID and constructing PID mis-match? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
