[
https://issues.apache.org/jira/browse/GEODE-7861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17261646#comment-17261646
]
ASF subversion and git services commented on GEODE-7861:
--------------------------------------------------------
Commit 089c1ba7e20606f8201a4cd8f7221f6adc60ba5c in geode's branch
refs/heads/develop from Kamilla Aslami
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=089c1ba ]
GEODE-7861: Improve error reporting in GMSJoinLeave.join() (#5839)
* GEODE-7861: Improve error reporting in GMSJoinLeave.join()
* Fix LocatorDUnitTest.testNoLocator
* Changes after the code review
* Fix typo
> 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
> Assignee: Kamilla Aslami
> Priority: Major
> Labels: pull-request-available
>
> 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)
