After digging a lot, I have found that IB cards and switch may went to
``bad'' state after host` load spike, so I have limited all
potentially cpu-hungry processes via cg. That`s has no effect at all,
spikes happens almost at same time when osds on the corresponding host
went down as ``wrongly
Sorry for the delay. A quick look at the log doesn't show anything
obvious... Can you elaborate on how you caused the hang?
-Sam
On Wed, Dec 19, 2012 at 3:53 AM, Andrey Korolyov and...@xdel.ru wrote:
Please take a look at the log below, this is slightly different bug -
both osd processes on
On Sun, Dec 30, 2012 at 10:56 PM, Samuel Just sam.j...@inktank.com wrote:
Sorry for the delay. A quick look at the log doesn't show anything
obvious... Can you elaborate on how you caused the hang?
-Sam
I am sorry for all this noise, the issue almost for sure has been
triggered by some bug
On Mon, Dec 17, 2012 at 2:36 AM, Andrey Korolyov and...@xdel.ru wrote:
Hi,
After recent switch do default ``--stripe-count 1'' on image upload I
have observed some strange thing - single import or deletion of the
striped image may temporarily turn off entire cluster, literally(see
log
Hi,
After recent switch do default ``--stripe-count 1'' on image upload I
have observed some strange thing - single import or deletion of the
striped image may temporarily turn off entire cluster, literally(see
log below).
Of course next issued osd map fix the situation, but all in-flight
