[
https://issues.apache.org/jira/browse/PHOENIX-5120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16760125#comment-16760125
]
Hadoop QA commented on PHOENIX-5120:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12957529/5120-1.4-v3.txt
against master branch at commit 52b5d9d5f8d1f41218956bb6099a3d7eaf50939a.
ATTACHMENT ID: 12957529
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/PreCommit-PHOENIX-Build/2298//console
This message is automatically generated.
> Avoid using MappedByteBuffers for server side sorting.
> ------------------------------------------------------
>
> Key: PHOENIX-5120
> URL: https://issues.apache.org/jira/browse/PHOENIX-5120
> Project: Phoenix
> Issue Type: Task
> Reporter: Lars Hofhansl
> Assignee: Lars Hofhansl
> Priority: Critical
> Attachments: 5120-1.4-v2.txt, 5120-1.4-v3.txt, 5120-1.4-wip.txt,
> 5120-1.4.txt, 5120-master.txt
>
>
> We should had a production outage due to this.
> MappedByteBuffer may leave files around, on top they use direct memory, which
> is not cleared until the JVM executes a full GC.
> See last comment on PHOENIX-2405.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
