https://tracker.ceph.com/https://tracker.ceph.com/favicon.ico2019-01-21T22:21:05ZCeph RADOS - Bug #37871: Ceph cannot connect to any monitors if one of them has a DNS resolution problemhttps://tracker.ceph.com/issues/37871?journal_id=1278742019-01-21T22:21:05ZGreg Farnumgfarnum@redhat.com
<ul><li><strong>Project</strong> changed from <i>Ceph</i> to <i>RADOS</i></li><li><strong>Category</strong> changed from <i>Monitor</i> to <i>Administration/Usability</i></li><li><strong>Component(RADOS)</strong> <i>MonClient</i> added</li></ul> RADOS - Bug #37871: Ceph cannot connect to any monitors if one of them has a DNS resolution problemhttps://tracker.ceph.com/issues/37871?journal_id=1278842019-01-22T03:32:53ZKefu Chaitchaikov@gmail.com
<ul></ul><p>i think the unresolvable address(es) is more of a configuration issue. and we should not ignore this. it's quite different from monitor which is not reachable, but its name can be resolved.</p> RADOS - Bug #37871: Ceph cannot connect to any monitors if one of them has a DNS resolution problemhttps://tracker.ceph.com/issues/37871?journal_id=1278932019-01-22T09:24:13ZJairo Llopisyajo.sk8@gmail.com
<ul></ul><p>In practical terms, what's the difference between not being able to connect because the host name cannot be resolved, and not being able to connect because the host is down?</p>
<p>At the end of the day, you cannot connect to that server, but can still connect to others, so as long as Ceph can still work, I don't see a reason for it to stop doing it...</p>