[
https://issues.apache.org/jira/browse/SENTRY-2183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16415808#comment-16415808
]
Sergio Peña commented on SENTRY-2183:
-------------------------------------
[~arjunmishra13] After thinking this for a while, I wonder if we really need
this change? The timeout will vary based on the amount of data users use. For
small users, 3.3min is enough, for large users, 20 or 30min is enough, for
others 10min is enough, so being this a configuration value that can be
customized on the sentry-site.xml file, then I don't think we should try to
change the value. What do you think?
> Increase default sentry-hdfs rpc timeout to 20 mins
> ---------------------------------------------------
>
> Key: SENTRY-2183
> URL: https://issues.apache.org/jira/browse/SENTRY-2183
> Project: Sentry
> Issue Type: Improvement
> Components: Sentry
> Affects Versions: 2.1.0
> Reporter: Arjun Mishra
> Assignee: Arjun Mishra
> Priority: Major
> Attachments: SENTRY-2183.001.patch, SENTRY-2183.002.patch,
> SENTRY-2183.01.patch
>
>
> Full HMS Snapshots for large amounts of data (millions of databases, or
> tables or partitions etc) take a lot more time than the current default of
> 3.3mins. Also ideally since a full HMS snapshot should only occur once it is
> best to increase the default to 20mins. This highly reduce the chance of
> failure while sending a full snapshot which could be critical
> Set sentry.hdfs.service.client.server.rpc-connection-timeout = 1200000
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
