You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@apisix.apache.org by "juzhiyuan (via GitHub)" <gi...@apache.org> on 2025/09/23 08:39:29 UTC
[I] data is lost when the instance shut down. [apisix]
juzhiyuan opened a new issue, #12627:
URL: https://github.com/apache/apisix/issues/12627
### Current Behavior
Any data in the queue is lost when the instance is shutting down or the worker reload is triggered.
1. https://github.com/apache/apisix/blob/master/docs/en/latest/batch-processor.md
### Expected Behavior
When the APISIX instance shutting down, all left data in the queue should be processed in full and not discarded, unless critical cases (need discussion)
### Error Logs
_No response_
### Steps to Reproduce
No Steps
### Environment
- APISIX version (run `apisix version`): 3.13
--
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: notifications-unsubscribe@apisix.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] discuss: data lost on worker shut down [apisix]
Posted by "Baoyuantop (via GitHub)" <gi...@apache.org>.
Baoyuantop commented on issue #12627:
URL: https://github.com/apache/apisix/issues/12627#issuecomment-6148208927
This issue has been fixed, and the changes are included in APISIX 3.19.0. [#12711](https://github.com/apache/apisix/pull/12711) removed the logic that skipped queued work during shutdown, and [#13288](https://github.com/apache/apisix/pull/13288) completed the shutdown flush and retry handling. The current implementation flushes remaining batches during graceful worker shutdown or reload instead of skipping them solely because a timer ends prematurely.
This addresses the queue loss during normal shutdown reported here. It does not guarantee zero loss after forced termination, when the logging backend is unavailable, or when retries are exhausted.
--
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: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] discuss: data lost on worker shut down [apisix]
Posted by "Baoyuantop (via GitHub)" <gi...@apache.org>.
Baoyuantop closed issue #12627: discuss: data lost on worker shut down
URL: https://github.com/apache/apisix/issues/12627
--
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: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] discuss: data lost on worker shut down [apisix]
Posted by "Baoyuantop (via GitHub)" <gi...@apache.org>.
Baoyuantop commented on issue #12627:
URL: https://github.com/apache/apisix/issues/12627#issuecomment-4009998845
Impact: All 20 logger plugins using batch-processor, covering APISIX's core observability features. In high-traffic scenarios, configuring a large batch_max_size (e.g., 1000) can cause thousands of log entries to be lost during a single reload.
--
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: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org