| 2014-11-03 10:34:07 |
ZhiQiang Fan |
bug |
|
|
added bug |
| 2014-11-03 10:34:16 |
ZhiQiang Fan |
ceilometer: assignee |
|
ZhiQiang Fan (aji-zqfan) |
|
| 2014-11-03 10:34:42 |
ZhiQiang Fan |
description |
Currently, we lots of generate samples by polling data from other services, but theses rest request have no timeout limitation. We have observed that some requests (for example, keystone due to openssl problem) may stuck for over several days (maybe forever if we don't restart the service). Other pollsters in same thread will not be able to work. The worst thing is that, when outside (keystone) service becomes normal, Ceilometer cannot recover it automatically.
So I strongly suggest that we should add timeout limit to **every** rest api call, this is quite important to Ceilometer's robust and reliability. |
Currently, we lots of generate samples by polling data from other services, but theses rest request have no timeout limitation. We have observed that some requests (for example, keystone due to openssl problem) may stuck for over several days (maybe forever if we don't restart the service). Other pollsters in same thread will not be able to work. The worst thing is that, when outside (keystone) service becomes normal, Ceilometer cannot recover itself automatically.
So I strongly suggest that we should add timeout limit to **every** rest api call, this is quite important to Ceilometer's robust and reliability. |
|
| 2014-11-03 10:35:04 |
ZhiQiang Fan |
description |
Currently, we lots of generate samples by polling data from other services, but theses rest request have no timeout limitation. We have observed that some requests (for example, keystone due to openssl problem) may stuck for over several days (maybe forever if we don't restart the service). Other pollsters in same thread will not be able to work. The worst thing is that, when outside (keystone) service becomes normal, Ceilometer cannot recover itself automatically.
So I strongly suggest that we should add timeout limit to **every** rest api call, this is quite important to Ceilometer's robust and reliability. |
Currently, we lots of generate samples by polling data from other services, but theses rest request have no timeout limitation. We have observed that some requests (for example, keystone due to openssl problem) may stuck for over several days (maybe forever if we don't restart the service). Other pollsters in same thread will not be able to work. The worst thing is that, when outside (keystone) service becomes normal, Ceilometer cannot recover itself automatically, cloud operator needs to restart it manually.
So I strongly suggest that we should add timeout limit to **every** rest api call, this is quite important to Ceilometer's robust and reliability. |
|
| 2014-11-06 09:05:56 |
OpenStack Infra |
ceilometer: status |
New |
In Progress |
|
| 2014-11-25 12:38:11 |
Eoghan Glynn |
ceilometer: milestone |
|
kilo-1 |
|
| 2014-11-25 12:43:57 |
Eoghan Glynn |
ceilometer: importance |
Undecided |
High |
|
| 2014-11-25 15:38:06 |
OpenStack Infra |
ceilometer: status |
In Progress |
Fix Committed |
|
| 2014-11-27 17:15:53 |
Eoghan Glynn |
nominated for series |
|
ceilometer/juno |
|
| 2014-11-27 17:15:53 |
Eoghan Glynn |
bug task added |
|
ceilometer/juno |
|
| 2014-11-27 17:16:02 |
Eoghan Glynn |
ceilometer/juno: milestone |
|
2014.2.1 |
|
| 2014-11-27 17:16:05 |
Eoghan Glynn |
ceilometer/juno: assignee |
|
Eoghan Glynn (eglynn) |
|
| 2014-11-27 17:16:07 |
Eoghan Glynn |
ceilometer/juno: importance |
Undecided |
High |
|
| 2014-11-27 17:16:10 |
Eoghan Glynn |
ceilometer/juno: status |
New |
In Progress |
|
| 2014-11-27 18:43:40 |
OpenStack Infra |
ceilometer/juno: status |
In Progress |
Fix Committed |
|
| 2014-12-05 08:08:24 |
Alan Pevec |
ceilometer/juno: status |
Fix Committed |
Fix Released |
|
| 2014-12-18 15:56:00 |
Thierry Carrez |
ceilometer: status |
Fix Committed |
Fix Released |
|
| 2015-04-30 08:58:23 |
Thierry Carrez |
ceilometer: milestone |
kilo-1 |
2015.1.0 |
|
