You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Requirement - what kind of business use case are you trying to solve?
I would like to support graceful shutdown for grpc plugin.
Problem - what in Jaeger blocks you from solving the requirement?
Writer in storage plugin might buffer spans in internal queue. AFAIK, kafka writer works that way. Even more, because Writer interface does not support batching, internal buffering is the only viable option for achieving high write throughput.
During graceful restart, collector should flush that internal queue before shutting down. Bundled storage plugins can implement optional Close() method, that is invoked during collector shutdown.
But grpc_plugin storage does not support that method.
Proposal - what do you suggest to solve the problem or improve the existing situation?
Extend plugin protocol with Close method. Plugin would advertise Close support in plugin capabilities.
That way, new collector should stay compatible with old plugins. And new plugins should stay compatible with old collector.
The text was updated successfully, but these errors were encountered:
Requirement - what kind of business use case are you trying to solve?
I would like to support graceful shutdown for grpc plugin.
Problem - what in Jaeger blocks you from solving the requirement?
Writer in storage plugin might buffer spans in internal queue. AFAIK, kafka writer works that way. Even more, because Writer interface does not support batching, internal buffering is the only viable option for achieving high write throughput.
During graceful restart, collector should flush that internal queue before shutting down. Bundled storage plugins can implement optional Close() method, that is invoked during collector shutdown.
But grpc_plugin storage does not support that method.
Proposal - what do you suggest to solve the problem or improve the existing situation?
Extend plugin protocol with Close method. Plugin would advertise Close support in plugin capabilities.
That way, new collector should stay compatible with old plugins. And new plugins should stay compatible with old collector.
The text was updated successfully, but these errors were encountered: