[jira] [Updated] (IMPALA-7734) Catalog and Statestore memz page shows useless memory breakdown

2019-07-03 Thread Tamas Mate (JIRA)


 [ 
https://issues.apache.org/jira/browse/IMPALA-7734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tamas Mate updated IMPALA-7734:
---
Fix Version/s: Impala 3.3.0

> Catalog and Statestore memz page shows useless memory breakdown
> ---
>
> Key: IMPALA-7734
> URL: https://issues.apache.org/jira/browse/IMPALA-7734
> Project: IMPALA
>  Issue Type: Bug
>Affects Versions: Impala 3.0, Impala 2.12.0, Impala 3.1.0
>Reporter: Tim Armstrong
>Assignee: Tamas Mate
>Priority: Minor
>  Labels: newbie, observability, ramp-up, supportability
> Fix For: Impala 3.3.0
>
> Attachments: after.png, before.png
>
>
> If you look at catalogd memz, e.g. at localhost:25020/memz, it has a bogus 
> breakdown. The catalogd does not use the MemTracker infrastructure since the 
> vast majority of it's memory consumption is in the JVM.
> {noformat}
> Breakdown
> : Total=0 Peak=0
>   Untracked Memory: Total=0
> {noformat}
> Reported by [~alanj_impala_5a78]
> Update: It is the same for statestored as well and apart from "breakdown" 
> section, the "Memory consumption / limit" part is also redundant. Should 
> remove both parts from the memz pages of both daemons
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org



[jira] [Updated] (IMPALA-7734) Catalog and Statestore memz page shows useless memory breakdown

2019-06-19 Thread Tamas Mate (JIRA)


 [ 
https://issues.apache.org/jira/browse/IMPALA-7734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tamas Mate updated IMPALA-7734:
---
Attachment: before.png

> Catalog and Statestore memz page shows useless memory breakdown
> ---
>
> Key: IMPALA-7734
> URL: https://issues.apache.org/jira/browse/IMPALA-7734
> Project: IMPALA
>  Issue Type: Bug
>Affects Versions: Impala 3.0, Impala 2.12.0, Impala 3.1.0
>Reporter: Tim Armstrong
>Assignee: Tamas Mate
>Priority: Minor
>  Labels: newbie, observability, ramp-up, supportability
> Attachments: after.png, before.png
>
>
> If you look at catalogd memz, e.g. at localhost:25020/memz, it has a bogus 
> breakdown. The catalogd does not use the MemTracker infrastructure since the 
> vast majority of it's memory consumption is in the JVM.
> {noformat}
> Breakdown
> : Total=0 Peak=0
>   Untracked Memory: Total=0
> {noformat}
> Reported by [~alanj_impala_5a78]
> Update: It is the same for statestored as well and apart from "breakdown" 
> section, the "Memory consumption / limit" part is also redundant. Should 
> remove both parts from the memz pages of both daemons
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org



[jira] [Updated] (IMPALA-7734) Catalog and Statestore memz page shows useless memory breakdown

2019-06-19 Thread Tamas Mate (JIRA)


 [ 
https://issues.apache.org/jira/browse/IMPALA-7734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tamas Mate updated IMPALA-7734:
---
Attachment: after.png

> Catalog and Statestore memz page shows useless memory breakdown
> ---
>
> Key: IMPALA-7734
> URL: https://issues.apache.org/jira/browse/IMPALA-7734
> Project: IMPALA
>  Issue Type: Bug
>Affects Versions: Impala 3.0, Impala 2.12.0, Impala 3.1.0
>Reporter: Tim Armstrong
>Assignee: Tamas Mate
>Priority: Minor
>  Labels: newbie, observability, ramp-up, supportability
> Attachments: after.png, before.png
>
>
> If you look at catalogd memz, e.g. at localhost:25020/memz, it has a bogus 
> breakdown. The catalogd does not use the MemTracker infrastructure since the 
> vast majority of it's memory consumption is in the JVM.
> {noformat}
> Breakdown
> : Total=0 Peak=0
>   Untracked Memory: Total=0
> {noformat}
> Reported by [~alanj_impala_5a78]
> Update: It is the same for statestored as well and apart from "breakdown" 
> section, the "Memory consumption / limit" part is also redundant. Should 
> remove both parts from the memz pages of both daemons
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org



[jira] [Updated] (IMPALA-7734) Catalog and Statestore memz page shows useless memory breakdown

2019-05-14 Thread Bikramjeet Vig (JIRA)


 [ 
https://issues.apache.org/jira/browse/IMPALA-7734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Bikramjeet Vig updated IMPALA-7734:
---
Summary: Catalog and Statestore memz page shows useless memory breakdown  
(was: Catalog memz page shows useless memory breakdown)

> Catalog and Statestore memz page shows useless memory breakdown
> ---
>
> Key: IMPALA-7734
> URL: https://issues.apache.org/jira/browse/IMPALA-7734
> Project: IMPALA
>  Issue Type: Bug
>Affects Versions: Impala 3.0, Impala 2.12.0, Impala 3.1.0
>Reporter: Tim Armstrong
>Priority: Minor
>  Labels: newbie, observability, ramp-up, supportability
>
> If you look at catalogd memz, e.g. at localhost:25020/memz, it has a bogus 
> breakdown. The catalogd does not use the MemTracker infrastructure since the 
> vast majority of it's memory consumption is in the JVM.
> {noformat}
> Breakdown
> : Total=0 Peak=0
>   Untracked Memory: Total=0
> {noformat}
> Reported by [~alanj_impala_5a78]
> Update: It is the same for statestored as well and apart from "breakdown" 
> section, the "Memory consumption / limit" part is also redundant. Should 
> remove both parts from the memz pages of both daemons
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org