[jira] [Commented] (HIVE-26376) Hive Metastore connection leak (OOM Error)
[
https://issues.apache.org/jira/browse/HIVE-26376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17565258#comment-17565258
]
Ranith Sardar commented on HIVE-26376:
--
[~zabetak] the Heap dump size is 3.5 GB. would try to connect offline and share
logs.
> Hive Metastore connection leak (OOM Error)
> --
>
> Key: HIVE-26376
> URL: https://issues.apache.org/jira/browse/HIVE-26376
> Project: Hive
> Issue Type: Bug
> Components: Metastore
>Affects Versions: 3.1.2
> Environment: !Screenshot 2022-07-07 at 11.52.33 AM.png!
>Reporter: Ranith Sardar
>Assignee: Stamatis Zampetakis
>Priority: Major
> Labels: pull-request-available
> Attachments: Screenshot 2022-07-07 at 11.52.33 AM.png
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Hive version:3.1.2
> Hive metastore heap size is 14GB, Memory Leak is happening after 4-5 days,
> hive meta-store throwing error with OOM.
> If we disable the configuration, the memory leak disappears.
> In the case of, Heap dump size 3.5GB, a large number of filesystem objects(>
> 9k instances) are being retained. It's occupying most of the heap space.
> Added snapshot from the eclipse MAT.
> Bellow are part of the stack trace for OOM error:
> {code:java}
> at
> org.apache.hadoop.hive.common.FileUtils.getFileStatusOrNull(Lorg/apache/hadoop/fs/FileSystem;Lorg/apache/hadoop/fs/Path;)Lorg/apache/hadoop/fs/FileStatus;
> (FileUtils.java:801)
> at
> org.apache.hadoop.hive.ql.security.authorization.StorageBasedAuthorizationProvider.checkPermissions(Lorg/apache/hadoop/conf/Configuration;Lorg/apache/hadoop/fs/Path;Ljava/util/EnumSet;)V
> (StorageBasedAuthorizationProvider.java:371)
> at
> org.apache.hadoop.hive.ql.security.authorization.StorageBasedAuthorizationProvider.authorize(Lorg/apache/hadoop/fs/Path;[Lorg/apache/hadoop/hive/ql/security/authorization/Privilege;[Lorg/apache/hadoop/hive/ql/security/authorization/Privilege;)V
> (StorageBasedAuthorizationProvider.java:346)
> at
> org.apache.hadoop.hive.ql.security.authorization.StorageBasedAuthorizationProvider.authorize(Lorg/apache/hadoop/hive/metastore/api/Database;[Lorg/apache/hadoop/hive/ql/security/authorization/Privilege;[Lorg/apache/hadoop/hive/ql/security/authorization/Privilege;)V
> (StorageBasedAuthorizationProvider.java:154)
> at
> org.apache.hadoop.hive.ql.security.authorization.AuthorizationPreEventListener.authorizeReadDatabase(Lorg/apache/hadoop/hive/metastore/events/PreReadDatabaseEvent;)V
> (AuthorizationPreEventListener.java:208)
> at
> org.apache.hadoop.hive.ql.security.authorization.AuthorizationPreEventListener.onEvent(Lorg/apache/hadoop/hive/metastore/events/PreEventContext;)V
> (AuthorizationPreEventListener.java:153)
> at
> org.apache.hadoop.hive.metastore.HiveMetaStore$HMSHandler.firePreEvent(Lorg/apache/hadoop/hive/metastore/events/PreEventContext;)V
> (HiveMetaStore.java:3221)
> at
> org.apache.hadoop.hive.metastore.HiveMetaStore$HMSHandler.get_database(Ljava/lang/String;)Lorg/apache/hadoop/hive/metastore/api/Database;
> (HiveMetaStore.java:1352){code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (HIVE-26376) Hive Metastore connection leak (OOM Error)
[
https://issues.apache.org/jira/browse/HIVE-26376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17564210#comment-17564210
]
Ranith Sardar commented on HIVE-26376:
--
yes, [~asolimando] [~ayushtkn]
Disabled fs.hdfs.impl.disable.cache property in HDFS level.
> Hive Metastore connection leak (OOM Error)
> --
>
> Key: HIVE-26376
> URL: https://issues.apache.org/jira/browse/HIVE-26376
> Project: Hive
> Issue Type: Bug
> Components: Metastore
>Affects Versions: 3.1.2
> Environment: !Screenshot 2022-07-07 at 11.52.33 AM.png!
>Reporter: Ranith Sardar
>Priority: Major
> Attachments: Screenshot 2022-07-07 at 11.52.33 AM.png
>
>
> Hive version:3.1.2
> Hive metastore heap size is 14GB, Memory Leak is happening after 4-5 days,
> hive meta-store throwing error with OOM.
> If we disable the configuration, the memory leak disappears.
> In the case of, Heap dump size 3.5GB, a large number of filesystem objects(>
> 9k instances) are being retained. It's occupying most of the heap space.
> Added snapshot from the eclipse MAT.
> Bellow are part of the stack trace for OOM error:
> {code:java}
> at
> org.apache.hadoop.hive.common.FileUtils.getFileStatusOrNull(Lorg/apache/hadoop/fs/FileSystem;Lorg/apache/hadoop/fs/Path;)Lorg/apache/hadoop/fs/FileStatus;
> (FileUtils.java:801)
> at
> org.apache.hadoop.hive.ql.security.authorization.StorageBasedAuthorizationProvider.checkPermissions(Lorg/apache/hadoop/conf/Configuration;Lorg/apache/hadoop/fs/Path;Ljava/util/EnumSet;)V
> (StorageBasedAuthorizationProvider.java:371)
> at
> org.apache.hadoop.hive.ql.security.authorization.StorageBasedAuthorizationProvider.authorize(Lorg/apache/hadoop/fs/Path;[Lorg/apache/hadoop/hive/ql/security/authorization/Privilege;[Lorg/apache/hadoop/hive/ql/security/authorization/Privilege;)V
> (StorageBasedAuthorizationProvider.java:346)
> at
> org.apache.hadoop.hive.ql.security.authorization.StorageBasedAuthorizationProvider.authorize(Lorg/apache/hadoop/hive/metastore/api/Database;[Lorg/apache/hadoop/hive/ql/security/authorization/Privilege;[Lorg/apache/hadoop/hive/ql/security/authorization/Privilege;)V
> (StorageBasedAuthorizationProvider.java:154)
> at
> org.apache.hadoop.hive.ql.security.authorization.AuthorizationPreEventListener.authorizeReadDatabase(Lorg/apache/hadoop/hive/metastore/events/PreReadDatabaseEvent;)V
> (AuthorizationPreEventListener.java:208)
> at
> org.apache.hadoop.hive.ql.security.authorization.AuthorizationPreEventListener.onEvent(Lorg/apache/hadoop/hive/metastore/events/PreEventContext;)V
> (AuthorizationPreEventListener.java:153)
> at
> org.apache.hadoop.hive.metastore.HiveMetaStore$HMSHandler.firePreEvent(Lorg/apache/hadoop/hive/metastore/events/PreEventContext;)V
> (HiveMetaStore.java:3221)
> at
> org.apache.hadoop.hive.metastore.HiveMetaStore$HMSHandler.get_database(Ljava/lang/String;)Lorg/apache/hadoop/hive/metastore/api/Database;
> (HiveMetaStore.java:1352){code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (HIVE-19825) HiveServer2 leader selection shall use different zookeeper znode
[ https://issues.apache.org/jira/browse/HIVE-19825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17434228#comment-17434228 ] Ranith Sardar commented on HIVE-19825: -- Tested a similar scenario with the patch. Patch LGTM. > HiveServer2 leader selection shall use different zookeeper znode > > > Key: HIVE-19825 > URL: https://issues.apache.org/jira/browse/HIVE-19825 > Project: Hive > Issue Type: Bug > Components: HiveServer2 >Reporter: Daniel Dai >Assignee: Daniel Dai >Priority: Major > Attachments: HIVE-19825.1.patch > > > Currently, HiveServer2 leader selection (used only by privilegesynchronizer > now) is reuse /hiveserver2 parent znode which is already used for HiveServer2 > service discovery. This interfere the service discovery. I'd like to switch > to a different znode /hiveserver2-leader. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work started] (HIVE-25639) Exclude tomcat-embed-core from libthrift
[ https://issues.apache.org/jira/browse/HIVE-25639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on HIVE-25639 started by Ranith Sardar. > Exclude tomcat-embed-core from libthrift > > > Key: HIVE-25639 > URL: https://issues.apache.org/jira/browse/HIVE-25639 > Project: Hive > Issue Type: Bug > Components: Thrift API >Reporter: Ranith Sardar >Assignee: Ranith Sardar >Priority: Major > > After Thrift dependency up-gradation to 0.14.1 to fix a known CVE but a > dependency issue in libthrift brings in tomcat-embed-core which has many > vulnerabilities. See: THRIFT-5375 > Since this dependency is used in Thrift only for a test we can safely exclude > it inside Hive. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (HIVE-25639) Exclude tomcat-embed-core from libthrift
[ https://issues.apache.org/jira/browse/HIVE-25639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ranith Sardar reassigned HIVE-25639: > Exclude tomcat-embed-core from libthrift > > > Key: HIVE-25639 > URL: https://issues.apache.org/jira/browse/HIVE-25639 > Project: Hive > Issue Type: Bug > Components: Thrift API >Reporter: Ranith Sardar >Assignee: Ranith Sardar >Priority: Major > > After Thrift dependency up-gradation to 0.14.1 to fix a known CVE but a > dependency issue in libthrift brings in tomcat-embed-core which has many > vulnerabilities. See: THRIFT-5375 > Since this dependency is used in Thrift only for a test we can safely exclude > it inside Hive. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (HIVE-25598) Upgrade groovy version to 2.4.21
[ https://issues.apache.org/jira/browse/HIVE-25598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ranith Sardar reassigned HIVE-25598: > Upgrade groovy version to 2.4.21 > > > Key: HIVE-25598 > URL: https://issues.apache.org/jira/browse/HIVE-25598 > Project: Hive > Issue Type: Bug >Reporter: Ranith Sardar >Assignee: Ranith Sardar >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (HIVE-25597) Bump Apache Derby 10.14.1.0 to 10.14.2.0 CVE-2018-1313
[ https://issues.apache.org/jira/browse/HIVE-25597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ranith Sardar reassigned HIVE-25597: > Bump Apache Derby 10.14.1.0 to 10.14.2.0 CVE-2018-1313 > -- > > Key: HIVE-25597 > URL: https://issues.apache.org/jira/browse/HIVE-25597 > Project: Hive > Issue Type: Bug >Reporter: Ranith Sardar >Assignee: Ranith Sardar >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (HIVE-22818) Preparation for jetty 9.4.26 upgrade
[ https://issues.apache.org/jira/browse/HIVE-22818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17405737#comment-17405737 ] Ranith Sardar commented on HIVE-22818: -- Hi [~lpinter], Is there any planning for jetty 9.4.26 upgrade in Hive Master branch? > Preparation for jetty 9.4.26 upgrade > > > Key: HIVE-22818 > URL: https://issues.apache.org/jira/browse/HIVE-22818 > Project: Hive > Issue Type: Improvement > Components: HiveServer2 >Reporter: László Pintér >Assignee: László Pintér >Priority: Minor > Fix For: 4.0.0 > > Attachments: HIVE-22818.01.patch, HIVE-22818.02.patch, > HIVE-22818.03.patch > > > Make some code adjustment, before upgrading jetty to 9.4.26. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (HIVE-25381) Hive impersonation Failed when load data of managed tables set as hive
[
https://issues.apache.org/jira/browse/HIVE-25381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17386715#comment-17386715
]
Ranith Sardar commented on HIVE-25381:
--
hive code is getting used for impersonating
{code}
public static boolean isOwnerOfFileHierarchy(final FileSystem fs,
final FileStatus fileStatus, final String userName, final boolean recurse)
throws IOException, InterruptedException {
UserGroupInformation proxyUser =
UserGroupInformation.createProxyUser(userName,
UserGroupInformation.getLoginUser());
try {
boolean isOwner = proxyUser.doAs(new PrivilegedExceptionAction()
{
@Override
public Boolean run() throws Exception {
FileSystem fsAsUser = FileSystem.get(fs.getUri(), fs.getConf());
return checkIsOwnerOfFileHierarchy(fsAsUser, fileStatus, userName,
recurse);
}
});
return isOwner;
} finally {
FileSystem.closeAllForUGI(proxyUser);
}{code}
Here userName is coming from
{code:java}
String configuredOwner = HiveConf.getVar(conf,
ConfVars.HIVE_LOAD_DATA_OWNER);{code}
which basically means UserGroupInformation.getLoginUser() is impersonating
"userName".
> Hive impersonation Failed when load data of managed tables set as hive
> --
>
> Key: HIVE-25381
> URL: https://issues.apache.org/jira/browse/HIVE-25381
> Project: Hive
> Issue Type: Bug
>Reporter: Ranith Sardar
>Assignee: Ranith Sardar
>Priority: Minor
> Fix For: 3.1.0, 4.0.0
>
>
> When hive.server2.enable.doAs = True and setting hive as the default value
> for "hive.load.data.owner" property, this will cause below logic(in
> Hive.java-needToCopy{color:#24292e}({color})) to fail always as the
> framework is validating the owner of the file against the value which we set
> in the property hive.load.data.owner.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (HIVE-25381) Hive impersonation Failed when load data of managed tables set as hive
[
https://issues.apache.org/jira/browse/HIVE-25381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ranith Sardar updated HIVE-25381:
-
Description: When hive.server2.enable.doAs = True and setting hive as the
default value for "hive.load.data.owner" property, this will cause below
logic(in Hive.java-needToCopy{color:#24292e}({color})) to fail always as the
framework is validating the owner of the file against the value which we set in
the property hive.load.data.owner. (was: When hive.server2.enable.doAs = True
and **
when setting hive as the default value for "hive.load.data.owner" property,
this will cause below logic(in Hive.java-needToCopy{color:#24292e}({color}))
to fail always as the framework is validating the owner of the file against the
value which we set in the property hive.load.data.owner.)
> Hive impersonation Failed when load data of managed tables set as hive
> --
>
> Key: HIVE-25381
> URL: https://issues.apache.org/jira/browse/HIVE-25381
> Project: Hive
> Issue Type: Bug
>Reporter: Ranith Sardar
>Assignee: Ranith Sardar
>Priority: Minor
> Fix For: 3.1.0, 4.0.0
>
>
> When hive.server2.enable.doAs = True and setting hive as the default value
> for "hive.load.data.owner" property, this will cause below logic(in
> Hive.java-needToCopy{color:#24292e}({color})) to fail always as the
> framework is validating the owner of the file against the value which we set
> in the property hive.load.data.owner.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (HIVE-25381) Hive impersonation Failed when load data of managed tables set as hive
[
https://issues.apache.org/jira/browse/HIVE-25381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ranith Sardar reassigned HIVE-25381:
> Hive impersonation Failed when load data of managed tables set as hive
> --
>
> Key: HIVE-25381
> URL: https://issues.apache.org/jira/browse/HIVE-25381
> Project: Hive
> Issue Type: Bug
>Reporter: Ranith Sardar
>Assignee: Ranith Sardar
>Priority: Minor
> Fix For: 4.0.0, 3.1.0
>
>
> When hive.server2.enable.doAs = True and **
> when setting hive as the default value for "hive.load.data.owner" property,
> this will cause below logic(in Hive.java-needToCopy{color:#24292e}({color}))
> to fail always as the framework is validating the owner of the file against
> the value which we set in the property hive.load.data.owner.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (HIVE-19928) Load Data for managed tables should set the owner of loaded files to a configurable user
[ https://issues.apache.org/jira/browse/HIVE-19928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ranith Sardar updated HIVE-19928: - Description: load data of managed tables should set the owner of the loaded files to a configurable user. the default user should be hive.` If the owner of existing file is not hive, then a rename/move operation should be replaced by copy with the copied file having hive as owner. was: load data of managed tables should set the owner of the loaded files to a configurable user. the default user should be hive. If the owner of existing file is not hive, then a rename/move operation should be replaced by copy with the copied file having hive as owner. > Load Data for managed tables should set the owner of loaded files to a > configurable user > > > Key: HIVE-19928 > URL: https://issues.apache.org/jira/browse/HIVE-19928 > Project: Hive > Issue Type: Task >Reporter: Deepak Jaiswal >Assignee: Deepak Jaiswal >Priority: Major > Fix For: 3.1.0, 4.0.0 > > Attachments: HIVE-19928.01-branch-3.patch, > HIVE-19928.02-branch-3.patch, HIVE-19928.1.patch, HIVE-19928.2.patch, > HIVE-19928.3.patch, HIVE-19928.4.patch, HIVE-19928.5.patch, > HIVE-19928.6.patch, HIVE-19928.7.patch > > > load data of managed tables should set the owner of the loaded files to a > configurable user. the default user should be hive.` > If the owner of existing file is not hive, then a rename/move operation > should be replaced by copy with the copied file having hive as owner. -- This message was sent by Atlassian Jira (v8.3.4#803005)
