[ 
https://issues.apache.org/jira/browse/GEODE-7861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17247563#comment-17247563
 ] 

ASF GitHub Bot commented on GEODE-7861:
---------------------------------------

kamilla1201 opened a new pull request #5839:
URL: https://github.com/apache/geode/pull/5839


   Thank you for submitting a contribution to Apache Geode.
   
   In order to streamline the review of the contribution we ask you
   to ensure the following steps have been taken:
   
   ### For all changes:
   - [ ] Is there a JIRA ticket associated with this PR? Is it referenced in 
the commit message?
   
   - [ ] Has your PR been rebased against the latest commit within the target 
branch (typically `develop`)?
   
   - [ ] Is your initial contribution a single, squashed commit?
   
   - [ ] Does `gradlew build` run cleanly?
   
   - [ ] Have you written or updated unit tests to verify your changes?
   
   - [ ] If adding new dependencies to the code, are these dependencies 
licensed in a way that is compatible for inclusion under [ASF 
2.0](http://www.apache.org/legal/resolved.html#category-a)?
   
   ### Note:
   Please ensure that once the PR is submitted, check Concourse for build 
issues and
   submit an update to your PR as soon as possible. If you need help, please 
send an
   email to d...@geode.apache.org.
   


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> 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
>            Priority: Major
>
> 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)

Reply via email to