You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@sentry.apache.org by "Sergio Peña (JIRA)" <ji...@apache.org> on 2017/08/18 14:59:00 UTC

[jira] [Commented] (SENTRY-1889) HMSFollower should log better detailed error message if it cannot connect to HMS

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

Sergio Peña commented on SENTRY-1889:
-------------------------------------

Changed the error message to this:
{noformat}
3:00:57.961 PM	ERROR  Fetching a new HMS snapshot cannot continue because an error occurred during the HMS communication: <THRIFT ERROR HERE>
{noformat}

[~vamsee] could you review if you have time?

> HMSFollower should log better detailed error message if it cannot connect to HMS
> --------------------------------------------------------------------------------
>
>                 Key: SENTRY-1889
>                 URL: https://issues.apache.org/jira/browse/SENTRY-1889
>             Project: Sentry
>          Issue Type: Bug
>          Components: Sentry
>    Affects Versions: 2.0.0
>            Reporter: Sergio Peña
>            Assignee: Sergio Peña
>         Attachments: SENTRY-1889.1.patch
>
>
> When  the HMSFollower thread cannot connect to the HMS server, it logs an error message like this:
> {noformat}
> 3:00:57.961 PM	ERROR	SentryHMSClient	
> Failed to communicate to HMS
> 3:00:58.461 PM	ERROR	SentryHMSClient	
> Failed to communicate to HMS
> {noformat}
> The above error message is not clear why it cannot connect to the HMS.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)