On 04/23/2015 06:58 PM, Craig Lewis wrote:
Yes, unless you've adjusted:
[global]
mon osd min down reporters = 9
mon osd min down reports = 12
OSDs talk to the MONs on the public network. The cluster network is
only used for OSD to OSD communication.
If one OSD node can't talk on that n
On Thu, Apr 23, 2015 at 5:20 AM, Kenneth Waegeman
>
> So it is all fixed now, but is it explainable that at first about 90% of
> the OSDS going into shutdown over and over, and only after some time got in
> a stable situation, because of one host network failure ?
>
> Thanks again!
Yes, unless yo
On 04/22/2015 07:35 PM, Gregory Farnum wrote:
On Wed, Apr 22, 2015 at 8:17 AM, Kenneth Waegeman
wrote:
Hi,
I changed the cluster network parameter in the config files, restarted the
monitors , and then restarted all the OSDs (shouldn't have done that).
Do you mean that you changed the IP a
On Wed, Apr 22, 2015 at 8:17 AM, Kenneth Waegeman
wrote:
> Hi,
>
> I changed the cluster network parameter in the config files, restarted the
> monitors , and then restarted all the OSDs (shouldn't have done that).
Do you mean that you changed the IP addresses of the monitors in the
config files
Hi,
I changed the cluster network parameter in the config files, restarted
the monitors , and then restarted all the OSDs (shouldn't have done
that). Now the OSDS keep on crashing, and the cluster is not able to
restore.. I eventually rebooted the whole cluster, but the problem
remains: For a
