[jira] [Updated] (HDDS-4187) Fix memory leak of recon
[ https://issues.apache.org/jira/browse/HDDS-4187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-4187: - Description: 40 datanodes with 400, 000 containers, start recon with xmx:10G. After several hours, recon's memory increase to 12G and OOM. Memory leak happens on heap, and the reason is recon is slow to process ContainerReport, so the queue of thread OOM. !screenshot-1.png! !screenshot-2.png! was: 40 datanodes with 400, 000 containers, start recon with xmx:10G. After several hours, recon's memory increase to 12G and OOM. Memory leak happens on heap, and the reason is recon is slow to process ContainerReplicaReport, so the queue of thread OOM. !screenshot-1.png! !screenshot-2.png! > Fix memory leak of recon > > > Key: HDDS-4187 > URL: https://issues.apache.org/jira/browse/HDDS-4187 > Project: Hadoop Distributed Data Store > Issue Type: Bug >Reporter: runzhiwang >Assignee: runzhiwang >Priority: Major > Attachments: screenshot-1.png, screenshot-2.png > > > 40 datanodes with 400, 000 containers, start recon with xmx:10G. After > several hours, recon's memory increase to 12G and OOM. Memory leak happens on > heap, and the reason is recon is slow to process ContainerReport, so the > queue of thread OOM. > !screenshot-1.png! > !screenshot-2.png! -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
[jira] [Updated] (HDDS-4187) Fix memory leak of recon
[ https://issues.apache.org/jira/browse/HDDS-4187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-4187: - Description: 40 datanodes with 400, 000 containers, start recon with xmx:10G. After several hours, recon's memory increase to 12G and OOM. Memory leak happens on heap, and the reason is recon is slow to process ContainerReplicaReport, so the queue of thread OOM. !screenshot-1.png! !screenshot-2.png! was: 40 datanodes with 400, 000 containers, start recon with xmx:10G. After several hours, recon's memory increase to 12G and OOM. Memory leak happens on heap, and the reason is recon is slow to process ContainerReplicaReport, so the queue of thread OOM. > Fix memory leak of recon > > > Key: HDDS-4187 > URL: https://issues.apache.org/jira/browse/HDDS-4187 > Project: Hadoop Distributed Data Store > Issue Type: Bug >Reporter: runzhiwang >Assignee: runzhiwang >Priority: Major > Attachments: screenshot-1.png, screenshot-2.png > > > 40 datanodes with 400, 000 containers, start recon with xmx:10G. After > several hours, recon's memory increase to 12G and OOM. Memory leak happens on > heap, and the reason is recon is slow to process ContainerReplicaReport, so > the queue of thread OOM. > !screenshot-1.png! > !screenshot-2.png! -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
[jira] [Updated] (HDDS-4187) Fix memory leak of recon
[ https://issues.apache.org/jira/browse/HDDS-4187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-4187: - Attachment: screenshot-2.png > Fix memory leak of recon > > > Key: HDDS-4187 > URL: https://issues.apache.org/jira/browse/HDDS-4187 > Project: Hadoop Distributed Data Store > Issue Type: Bug >Reporter: runzhiwang >Assignee: runzhiwang >Priority: Major > Attachments: screenshot-1.png, screenshot-2.png > > > 40 datanodes with 400, 000 containers, start recon with xmx:10G. After > several hours, recon's memory increase to 12G and OOM. Memory leak happens on > heap, and the reason is recon is slow to process ContainerReplicaReport, so > the queue of thread OOM. > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
[jira] [Updated] (HDDS-4187) Fix memory leak of recon
[ https://issues.apache.org/jira/browse/HDDS-4187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-4187: - Attachment: screenshot-1.png > Fix memory leak of recon > > > Key: HDDS-4187 > URL: https://issues.apache.org/jira/browse/HDDS-4187 > Project: Hadoop Distributed Data Store > Issue Type: Bug >Reporter: runzhiwang >Assignee: runzhiwang >Priority: Major > Attachments: screenshot-1.png > > > 40 datanodes with 400, 000 containers, start recon with xmx:10G. After > several hours, recon's memory increase to 12G and OOM. Memory leak happens on > heap, and the reason is recon is slow to process ContainerReplicaReport, so > the queue of thread OOM. > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
[jira] [Updated] (HDDS-4187) Fix memory leak of recon
[ https://issues.apache.org/jira/browse/HDDS-4187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-4187: - Description: 40 datanodes with 400, 000 containers, start recon with xmx:10G. After several hours, recon's memory increase to 12G and OOM. Memory leak happens on heap, and the reason is recon is slow to process ContainerReplicaReport, so the queue of thread OOM. > Fix memory leak of recon > > > Key: HDDS-4187 > URL: https://issues.apache.org/jira/browse/HDDS-4187 > Project: Hadoop Distributed Data Store > Issue Type: Bug >Reporter: runzhiwang >Assignee: runzhiwang >Priority: Major > > 40 datanodes with 400, 000 containers, start recon with xmx:10G. After > several hours, recon's memory increase to 12G and OOM. Memory leak happens on > heap, and the reason is recon is slow to process ContainerReplicaReport, so > the queue of thread OOM. > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org