[jira] [Updated] (PHOENIX-5120) Avoid using MappedByteBuffers for server side sorting.
[ https://issues.apache.org/jira/browse/PHOENIX-5120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-5120: --- Affects Version/s: 4.14.1 > Avoid using MappedByteBuffers for server side sorting. > -- > > Key: PHOENIX-5120 > URL: https://issues.apache.org/jira/browse/PHOENIX-5120 > Project: Phoenix > Issue Type: Task >Affects Versions: 4.14.1 >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-v3.txt, 5120-master-v5.txt, 5120-master-v6.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)
[jira] [Updated] (PHOENIX-5120) Avoid using MappedByteBuffers for server side sorting.
[ https://issues.apache.org/jira/browse/PHOENIX-5120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-5120: --- Attachment: 5120-master-v6.txt > 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-v3.txt, 5120-master-v5.txt, 5120-master-v6.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)
[jira] [Updated] (PHOENIX-5120) Avoid using MappedByteBuffers for server side sorting.
[ https://issues.apache.org/jira/browse/PHOENIX-5120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-5120: --- Attachment: 5120-master-v5.txt > 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-v3.txt, 5120-master-v5.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)
[jira] [Updated] (PHOENIX-5120) Avoid using MappedByteBuffers for server side sorting.
[ https://issues.apache.org/jira/browse/PHOENIX-5120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-5120: --- Attachment: 5120-master-v3.txt > 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-v3.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)
[jira] [Updated] (PHOENIX-5120) Avoid using MappedByteBuffers for server side sorting.
[ https://issues.apache.org/jira/browse/PHOENIX-5120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-5120: --- Attachment: 5120-1.4-v3.txt > 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)
[jira] [Updated] (PHOENIX-5120) Avoid using MappedByteBuffers for server side sorting.
[ https://issues.apache.org/jira/browse/PHOENIX-5120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-5120: --- Attachment: 5120-master.txt > 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-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)
[jira] [Updated] (PHOENIX-5120) Avoid using MappedByteBuffers for server side sorting.
[ https://issues.apache.org/jira/browse/PHOENIX-5120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-5120: --- Priority: Critical (was: Major) > 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-wip.txt, 5120-1.4.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)
[jira] [Updated] (PHOENIX-5120) Avoid using MappedByteBuffers for server side sorting.
[ https://issues.apache.org/jira/browse/PHOENIX-5120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-5120: --- Attachment: 5120-1.4-v2.txt > 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: Major > Attachments: 5120-1.4-v2.txt, 5120-1.4-wip.txt, 5120-1.4.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)
[jira] [Updated] (PHOENIX-5120) Avoid using MappedByteBuffers for server side sorting.
[ https://issues.apache.org/jira/browse/PHOENIX-5120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-5120: --- Attachment: (was: 5120-1.4-v2.txt) > 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: Major > Attachments: 5120-1.4-wip.txt, 5120-1.4.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)
[jira] [Updated] (PHOENIX-5120) Avoid using MappedByteBuffers for server side sorting.
[ https://issues.apache.org/jira/browse/PHOENIX-5120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-5120: --- Attachment: 5120-1.4-v2.txt > 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: Major > Attachments: 5120-1.4-v2.txt, 5120-1.4-wip.txt, 5120-1.4.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)
[jira] [Updated] (PHOENIX-5120) Avoid using MappedByteBuffers for server side sorting.
[ https://issues.apache.org/jira/browse/PHOENIX-5120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-5120: --- Attachment: 5120-1.4.txt > 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 >Priority: Major > Attachments: 5120-1.4-wip.txt, 5120-1.4.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)
[jira] [Updated] (PHOENIX-5120) Avoid using MappedByteBuffers for server side sorting.
[ https://issues.apache.org/jira/browse/PHOENIX-5120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-5120: --- Attachment: 5120-1.4-wip.txt > 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 >Priority: Major > Attachments: 5120-1.4-wip.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)
