[jira] [Updated] (SENTRY-957) Exceptions in MetaStoreCacheIntilizer should probably not prevent HMS from starting up

["Sravya Tirukkovalur (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SENTRY-957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sravya Tirukkovalur updated SENTRY-957:
---------------------------------------
    Description: 
Right now if there is an error condition in evaluating paths in MetaStoreCacheIntilizer in one of the tasks, we throw a Runtime Exception. The more I think about, it looks like it would be best to log an error and continue; as a plugin should not cause the service to come down? On the other hand, doing so might result in incomplete sync which might make it hard to get to the root cause. 
{noformat}
for (Future<CallResult> result : results) {
      CallResult callResult = result.get();
      if (callResult.failure != null) {
        throw new RuntimeException(callResult.failure);
      }
    }
{noformat}

  was:
{noformat}
for (Future<CallResult> result : results) {
      CallResult callResult = result.get();
      if (callResult.failure != null) {
        throw new RuntimeException(callResult.failure);
      }
    }
{noformat}


> Exceptions in MetaStoreCacheIntilizer should probably not prevent HMS from starting up
> --------------------------------------------------------------------------------------
>
>                 Key: SENTRY-957
>                 URL: https://issues.apache.org/jira/browse/SENTRY-957
>             Project: Sentry
>          Issue Type: Bug
>          Components: Hdfs Plugin
>    Affects Versions: 1.7.0
>            Reporter: Sravya Tirukkovalur
>            Assignee: Sravya Tirukkovalur
>             Fix For: 1.7.0
>
>
> Right now if there is an error condition in evaluating paths in MetaStoreCacheIntilizer in one of the tasks, we throw a Runtime Exception. The more I think about, it looks like it would be best to log an error and continue; as a plugin should not cause the service to come down? On the other hand, doing so might result in incomplete sync which might make it hard to get to the root cause. 
> {noformat}
> for (Future<CallResult> result : results) {
>       CallResult callResult = result.get();
>       if (callResult.failure != null) {
>         throw new RuntimeException(callResult.failure);
>       }
>     }
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)