You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Dan Smith (Jira)" <ji...@apache.org> on 2020/03/09 16:52:00 UTC
[jira] [Created] (GEODE-7861) Improve error reporting when a member
is unable to contact a locator
Dan Smith created GEODE-7861:
--------------------------------
Summary: Improve error reporting when a member is unable to contact a locator
Key: GEODE-7861
URL: https://issues.apache.org/jira/browse/GEODE-7861
Project: Geode
Issue Type: Improvement
Components: membership
Reporter: Dan Smith
When a member is unable to contact a join the system due to a failure to contact a locator, we could be a lot more specific, which would help users debug issues in their environment. We currently print out
{noformat}
Unable to join the distributed system. Operation either timed out, was stopped or Locator does not exist.
{noformat}
We should include the underlying exception from the last locator we tried to contact as a cause, so that users can see why it failed (DNS error, ???). Perhaps also the list of locators we tried to contact.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)