[jira] [Created] (HIVE-21689) Buddy Allocator memory accounting does not account for failed allocation attempts
slim bouguerra created HIVE-21689: - Summary: Buddy Allocator memory accounting does not account for failed allocation attempts Key: HIVE-21689 URL: https://issues.apache.org/jira/browse/HIVE-21689 Project: Hive Issue Type: Bug Components: llap Reporter: slim bouguerra Assignee: slim bouguerra Allocation method on Buddy Allocator, does not release the reserved memory in case we failed to allocate the full sequence. Simple example: Assume We have an allocation request of 1kb. Will call reserver and reserve 1KB. Try to allocate will fail due to race condition. Try to discard will fail due to no space. At this point will exit without releasing the reserved memory. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (HIVE-21688) SLF4J binding warning message printed when invoking beeline
Todd Lipcon created HIVE-21688:
--
Summary: SLF4J binding warning message printed when invoking
beeline
Key: HIVE-21688
URL: https://issues.apache.org/jira/browse/HIVE-21688
Project: Hive
Issue Type: Bug
Affects Versions: 4.0.0
Reporter: Todd Lipcon
When I run beeline (or any other hive tool), it outputs the following:
{code}
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in
[jar:file:/data/1/todd/impala/toolchain/cdp_components-1056671/apache-hive-3.1.0.6.0.99.0-147-bin/lib/log4j-slf4j-impl-2.10.0.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in
[jar:file:/data/1/todd/impala/toolchain/cdp_components-1056671/hadoop-3.1.1.6.0.99.0-147/share/hadoop/common/lib/slf4j-log4j12-1.7.25.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
SLF4J: Actual binding is of type [org.apache.logging.slf4j.Log4jLoggerFactory]
{code}
It seems that Hive moved to log4j2 in HIVE-11304 and started bundling the
log4j2 slf4j binding in HIVE-13015. Hadoop is still on log4j 1, so the SLF4J
bindings are conflicting and producing these errors on stderr. This may confuse
users, and makes it hard to understand which log4j properties files are getting
used.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
Re: HIVE-21639 and Hive 2.3.5 release
Ok, I'll do a new build with that patch and post another snapshot so you can test with it. Alan. On Fri, May 3, 2019 at 2:15 AM Yuming Wang wrote: > Yes. This is the last one. > > On Fri, May 3, 2019 at 4:15 PM Hyukjin Kwon wrote: > >> Thank you so much Alan. >> >> As far as I can tell, we're all good except HIVE-21680 for now. >> Yuming, is the last one? or are you still investigating? >> >> 2019년 4월 26일 (금) 오전 6:56, Alan Gates 님이 작성: >> >>> Yuming, and Hjukjin, I've committed HIVE-21639 and HIVE-21536 to >>> branch-2.3. Let me know once you've tested this against Spark 3 and are >>> ready to start the release process. >>> >>> Alan. >>> >>> On Thu, Apr 25, 2019 at 9:47 AM Alan Gates wrote: >>> Yuming Wang and Hjukjin Kwon have proposed releasing a Hive 2.3.5 that Spark can use. They need to push a couple of back ports into branch-2.3 first. See [1] and [2] for details. I'm willing to work with them to get this done. Alan. 1. https://issues.apache.org/jira/browse/HIVE-21639?focusedCommentId=16822802&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16822802 2. https://issues.apache.org/jira/browse/HIVE-21639?focusedCommentId=16826113&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16826113
Re: HIVE-21639 and Hive 2.3.5 release
Thank you so much Alan. As far as I can tell, we're all good except HIVE-21680 for now. Yuming, is the last one? or are you still investigating? 2019년 4월 26일 (금) 오전 6:56, Alan Gates 님이 작성: > Yuming, and Hjukjin, I've committed HIVE-21639 and HIVE-21536 to > branch-2.3. Let me know once you've tested this against Spark 3 and are > ready to start the release process. > > Alan. > > On Thu, Apr 25, 2019 at 9:47 AM Alan Gates wrote: > >> Yuming Wang and Hjukjin Kwon have proposed releasing a Hive 2.3.5 that >> Spark can use. They need to push a couple of back ports into branch-2.3 >> first. See [1] and [2] for details. >> >> I'm willing to work with them to get this done. >> >> Alan. >> >> 1. >> https://issues.apache.org/jira/browse/HIVE-21639?focusedCommentId=16822802&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16822802 >> 2. >> https://issues.apache.org/jira/browse/HIVE-21639?focusedCommentId=16826113&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16826113 >> >>
