AutoReconnect exception while replica sets vote for PRIMARY
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ceilometer |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
If ceilometer call (ceilometer statistics -m ...) is done while replicas members are voting for new PRIMARY
next traceback might appears in api.og:
2015-04-24 19:08:54.049 13792 ERROR wsme.api [-] Server-side error: "No replica set primary available for query with ReadPreference PRIMARY". Detail:
Traceback (most recent call last):
File "/usr/lib/
result = f(self, *args, **kwargs)
File "/usr/lib/
f, period, g, aggregate)
File "/usr/lib/
pymongo.
File "/usr/lib64/
for doc in clone:
File "/usr/lib64/
if len(self.__data) or self._refresh():
File "/usr/lib64/
self.
File "/usr/lib64/
**kwargs)
File "/usr/lib64/
raise AutoReconnect(msg, errors)
AutoReconnect: No replica set primary available for query with ReadPreference PRIMARY
IMHO, this has to be handled gracefully.
Thanks,Yurii
Changed in ceilometer: | |
assignee: | nobody → Pradeep Kilambi (pkilambi) |
Changed in ceilometer: | |
assignee: | Pradeep Kilambi (pkilambi) → nobody |
ceilometer doesn't do storage no more.