[GitHub] [apisix] aiyiyi121 commented on issue #3937: [discuss]: when a node in the etcd cluster fails, no error log is output

2021-03-30 Thread GitBox


aiyiyi121 commented on issue #3937:
URL: https://github.com/apache/apisix/issues/3937#issuecomment-810717693


   > > > If we skip this for some nodes, there is no way to ensure they are 
correctly initialized.
   > > 
   > > 
   > > Why? ETCD is self-replicated.
   > 
   > People might configure wrong node. Don't be surprise, it happened before.
   
   Thx, got it. We should pay more attention to the HA of etcd


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

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org




[GitHub] [apisix] aiyiyi121 commented on issue #3937: [discuss]: when a node in the etcd cluster fails, no error log is output

2021-03-30 Thread GitBox


aiyiyi121 commented on issue #3937:
URL: https://github.com/apache/apisix/issues/3937#issuecomment-810269709


   > > @spacewander @Firstsawyou
   > > When I use ./apisix start to start the apisix, I found it will init 
etcd. I read the "etcd init" code and found it will check the status of all 
etcd nodes. So when when a node in the etcd cluster(3 nodes) fails, the 
etcd_init will fail too , and the apisix can't start.
   > > I think when a node in the etcd cluster(3 nodes) fails, the etcd_init 
should success because it do no affect on the normal operation of APISIX, and 
the apisix should start normally.
   > 
   > It does. Why do you want to configure a bad node inside APISIX? Start 
APISIX in an unhealthy situation is not a good idea. Consider one of your fail 
nodes has a wrong auth configuration which can't be detected if we just skip it.
   
   Because we want to be able to normally start and use apisix in a production 
environment in case of the 
   extreme cases such as a node in the etcd cluster(3 nodes) fails.
   


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

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org




[GitHub] [apisix] aiyiyi121 commented on issue #3937: [discuss]: when a node in the etcd cluster fails, no error log is output

2021-03-30 Thread GitBox


aiyiyi121 commented on issue #3937:
URL: https://github.com/apache/apisix/issues/3937#issuecomment-810153784


   @spacewander @Firstsawyou 
   When I use ./apisix start to start the apisix, I found it will init etcd. I 
read the "etcd init" code and found it will check the status of all etcd nodes. 
So when when a node in the etcd cluster(3 nodes) fails, the etcd_init will fail 
too , and the apisix can't start.
   I think when a node in the etcd cluster(3 nodes) fails, the etcd_init should 
success because it do no affect on the normal operation of APISIX, and the 
apisix should start normally.


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

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org




[GitHub] [apisix] aiyiyi121 commented on issue #3937: [discuss]: when a node in the etcd cluster fails, no error log is output

2021-03-29 Thread GitBox


aiyiyi121 commented on issue #3937:
URL: https://github.com/apache/apisix/issues/3937#issuecomment-809896187


   > If it reports an error log in 18:26, it doesn't get data from another etcd 
node at that time.
   > @Firstsawyou
   > Does the error log happen forever or just for a moment?
   
   The error log happen forever when a node in the etcd cluster(3 nodes) fails, 
at that time ,apisix can get data from other etcd node and work corretcly.


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

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org