LiteSun commented on PR #12244:
URL: https://github.com/apache/apisix/pull/12244#issuecomment-2914790160

   >  ### How to quantitatively assess the performance impact on etcd?
   > ###  What specific parts are not configured correctly? I think it needs to 
be clearly stated how it should be done correctly. I think this might help 
users who are unable to upgrade and need to use the plugin.
   
   When does the issue occur:
   
   When APISIX is deployed in `traditional` mode, restarting APISIX triggers 
the `server-info` plugin to write data to etcd. If too many APISIX instances 
write to etcd at the same time, it may cause etcd to become unavailable. This 
can prevent APISIX from starting properly, which in turn affects the data plane 
(DP) and its ability to handle traffic.
   
   Recommended approach:
   
   If you need to continue using the `server-info` plugin, before APISIX begins 
handling production traffic, refer to [the etcd example hardware 
configurations](https://etcd.io/docs/v3.5/op-guide/hardware/) to test and 
determine how much etcd hardware resources are required for the number of 
APISIX instances you’re running. This ensures APISIX can start up reliably.
   
   ---
   
   > ### What are the alternatives?
   
   There is currently **no perfect alternative**. If you still need the 
information provided by the server-info plugin, you might consider developing a 
new plugin to store this data in a different backend such as Redis or MySQL. 
Alternatively, you can continue using the server-info plugin with caution, 
making sure that sufficient etcd hardware resources are provisioned.
   
   ---
   
   > ### But in your plan it will be removed at 3.14.0, which is too soon
   
   If you feel the removal is too soon, we can postpone it by two additional 
release cycles to give users more time to adjust and discuss.
   
   Here’s the updated deprecation schedule:
   
   - **3.13.0** – *Deprecation begins*:  
     - Marked as deprecated  
     - Documentation updated  
     - Warning logs emitted  
   
   - **3.14.0** – *Grace period*:  
     - No functional changes  
     - Gives developers time to adapt  
   
   - **3.15.0** – *Extended grace period*:  
     - Continued support  
     - More time for migration and community feedback  
   
   - **3.16.0** – *Final removal*:  
     - The feature will be completely removed from this version onward


-- 
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]

Reply via email to