[GitHub] eagle issue #787: [MINOR] Change default-rack to /default-rack

2017-01-19 Thread qingwen220
Github user qingwen220 commented on the issue:

https://github.com/apache/eagle/pull/787
  
It do not matter.  The node with a new rack info will replace the old one


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] eagle issue #787: [MINOR] Change default-rack to /default-rack

2017-01-19 Thread r7raul1984
Github user r7raul1984 commented on the issue:

https://github.com/apache/eagle/pull/787
  
@qingwen220  Because ClusterNodeAPITopologyRackResolver use "/default-rack" 
.I think it will issue some problem when  you complete EAGLE-876.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[jira] [Commented] (EAGLE-876) TopologyBaseAPIEntity comparison should consider rack info

2017-01-19 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/EAGLE-876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15831179#comment-15831179
 ] 

ASF GitHub Bot commented on EAGLE-876:
--

Github user r7raul1984 commented on the issue:

https://github.com/apache/eagle/pull/787
  
@qingwen220  Because ClusterNodeAPITopologyRackResolver use "/default-rack" 
.I think it will issue some problem when  you complete EAGLE-876.


> TopologyBaseAPIEntity comparison should consider rack info
> --
>
> Key: EAGLE-876
> URL: https://issues.apache.org/jira/browse/EAGLE-876
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: Zhao, Qingwen
>Assignee: Zhao, Qingwen
> Fix For: v0.5.0
>
>
> TopologyBaseAPIEntity comparison should consider rack info



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[GitHub] eagle issue #787: [MINOR] Change default-rack to /default-rack

2017-01-19 Thread qingwen220
Github user qingwen220 commented on the issue:

https://github.com/apache/eagle/pull/787
  
At the initial design, we prefer to extract the 'exact rack info', for 
example,  '/rack-45' -> 'rack-45',  '/' will be removed.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] eagle issue #787: [MINOR] Change default-rack to /default-rack

2017-01-19 Thread qingwen220
Github user qingwen220 commented on the issue:

https://github.com/apache/eagle/pull/787
  
Why do you need this change?


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[jira] [Commented] (EAGLE-859) MR job performance suggestion

2017-01-19 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/EAGLE-859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15831100#comment-15831100
 ] 

ASF GitHub Bot commented on EAGLE-859:
--

Github user asfgit closed the pull request at:

https://github.com/apache/eagle/pull/784


> MR job performance suggestion
> -
>
> Key: EAGLE-859
> URL: https://issues.apache.org/jira/browse/EAGLE-859
> Project: Eagle
>  Issue Type: New Feature
>Affects Versions: v0.5.0
>Reporter: Zhao, Qingwen
>Assignee: Zhao, Qingwen
>
> Analyze a mapreduce job performance from the following aspects
> * compression setting anaysis
> * split setting analysis
> * spill analysis
> * mapreduce task num analysis
> * data skew analysis
> * GC time analysis



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[GitHub] eagle pull request #784: EAGLE-859 MapReduce job performance suggestion

2017-01-19 Thread asfgit
Github user asfgit closed the pull request at:

https://github.com/apache/eagle/pull/784


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[jira] [Commented] (EAGLE-876) TopologyBaseAPIEntity comparison should consider rack info

2017-01-19 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/EAGLE-876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15831095#comment-15831095
 ] 

ASF GitHub Bot commented on EAGLE-876:
--

Github user asfgit closed the pull request at:

https://github.com/apache/eagle/pull/785


> TopologyBaseAPIEntity comparison should consider rack info
> --
>
> Key: EAGLE-876
> URL: https://issues.apache.org/jira/browse/EAGLE-876
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: Zhao, Qingwen
>Assignee: Zhao, Qingwen
> Fix For: v0.5.0
>
>
> TopologyBaseAPIEntity comparison should consider rack info



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[GitHub] eagle pull request #785: EAGLE-876 TopologyBaseAPIEntity comparison should c...

2017-01-19 Thread asfgit
Github user asfgit closed the pull request at:

https://github.com/apache/eagle/pull/785


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[jira] [Created] (EAGLE-878) mention accurate storm dependency

2017-01-19 Thread Jayesh (JIRA)
Jayesh created EAGLE-878:


 Summary: mention accurate storm dependency
 Key: EAGLE-878
 URL: https://issues.apache.org/jira/browse/EAGLE-878
 Project: Eagle
  Issue Type: Improvement
Reporter: Jayesh
Assignee: Jayesh


till storm 0.10.0 the packages are backtype.storm.*
but for storm >= 1.0.0 the packages are org.apache.storm.*

we should clearly mention this in doc.

example: if you run eagle 0.5 on latest storm 1.x it will throw 
ClassNotFoundException for backtype.storm.topology.base.BaseRichBolt



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (EAGLE-878) mention accurate storm dependency

2017-01-19 Thread Jayesh (JIRA)

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

Jayesh updated EAGLE-878:
-
Priority: Minor  (was: Major)

> mention accurate storm dependency
> -
>
> Key: EAGLE-878
> URL: https://issues.apache.org/jira/browse/EAGLE-878
> Project: Eagle
>  Issue Type: Improvement
>Reporter: Jayesh
>Assignee: Jayesh
>Priority: Minor
>
> till storm 0.10.0 the packages are backtype.storm.*
> but for storm >= 1.0.0 the packages are org.apache.storm.*
> we should clearly mention this in doc.
> example: if you run eagle 0.5 on latest storm 1.x it will throw 
> ClassNotFoundException for backtype.storm.topology.base.BaseRichBolt



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[GitHub] eagle pull request #787: [MINOR] Change default-rack to /default-rack

2017-01-19 Thread r7raul1984
GitHub user r7raul1984 opened a pull request:

https://github.com/apache/eagle/pull/787

[MINOR] Change default-rack to /default-rack

- Change default-rack to /default-rack

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/1haodian/eagle DEFAULT-RACK

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/eagle/pull/787.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #787


commit a1379c7016a32817775d4879f62efd313bb79af1
Author: r7raul1984 
Date:   2017-01-20T00:00:06Z

[MINOR] Change default-rack to /default-rack




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[jira] [Commented] (EAGLE-876) TopologyBaseAPIEntity comparison should consider rack info

2017-01-19 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/EAGLE-876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15829930#comment-15829930
 ] 

ASF GitHub Bot commented on EAGLE-876:
--

Github user haoch commented on the issue:

https://github.com/apache/eagle/pull/785
  
LGTM


> TopologyBaseAPIEntity comparison should consider rack info
> --
>
> Key: EAGLE-876
> URL: https://issues.apache.org/jira/browse/EAGLE-876
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: Zhao, Qingwen
>Assignee: Zhao, Qingwen
> Fix For: v0.5.0
>
>
> TopologyBaseAPIEntity comparison should consider rack info



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[GitHub] eagle issue #785: EAGLE-876 TopologyBaseAPIEntity comparison should consider...

2017-01-19 Thread haoch
Github user haoch commented on the issue:

https://github.com/apache/eagle/pull/785
  
LGTM


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[jira] [Commented] (EAGLE-845) HBase JMX Monitoring Dashboard

2017-01-19 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/EAGLE-845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15829707#comment-15829707
 ] 

ASF GitHub Bot commented on EAGLE-845:
--

Github user asfgit closed the pull request at:

https://github.com/apache/eagle/pull/782


> HBase JMX Monitoring Dashboard
> --
>
> Key: EAGLE-845
> URL: https://issues.apache.org/jira/browse/EAGLE-845
> Project: Eagle
>  Issue Type: New Feature
>  Components: Hadoop JMX Monitor, Web UI
>Reporter: JiJun Tang
>Assignee: Lingang Deng
> Fix For: v0.5.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[GitHub] eagle pull request #782: [EAGLE-845][IMPROVEMENT] Using aggregation query in...

2017-01-19 Thread asfgit
Github user asfgit closed the pull request at:

https://github.com/apache/eagle/pull/782


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[jira] [Commented] (EAGLE-877) Rename metric "hadoop.hbase.ipc.ipc.*" to "hadoop.hbase.regionserver.ipc.*" to support different hbase version metric

2017-01-19 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/EAGLE-877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15829702#comment-15829702
 ] 

ASF GitHub Bot commented on EAGLE-877:
--

Github user asfgit closed the pull request at:

https://github.com/apache/eagle/pull/786


> Rename metric "hadoop.hbase.ipc.ipc.*" to "hadoop.hbase.regionserver.ipc.*" 
> to support different hbase version metric
> -
>
> Key: EAGLE-877
> URL: https://issues.apache.org/jira/browse/EAGLE-877
> Project: Eagle
>  Issue Type: Sub-task
>  Components: Hadoop JMX Monitor
>Affects Versions: v0.5.0
>Reporter: Hao Chen
>Assignee: Hao Chen
> Fix For: v0.5.0
>
>
> Rename metric "hadoop.hbase.ipc.ipc.*" to "hadoop.hbase.regionserver.ipc.*" 
> to support different hbase version metric



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[GitHub] eagle pull request #786: [EAGLE-877] Rename metric hadoop.hbase.ipc.ipc.* to...

2017-01-19 Thread asfgit
Github user asfgit closed the pull request at:

https://github.com/apache/eagle/pull/786


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[jira] [Commented] (EAGLE-877) Rename metric "hadoop.hbase.ipc.ipc.*" to "hadoop.hbase.regionserver.ipc.*" to support different hbase version metric

2017-01-19 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/EAGLE-877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15829649#comment-15829649
 ] 

ASF GitHub Bot commented on EAGLE-877:
--

GitHub user haoch opened a pull request:

https://github.com/apache/eagle/pull/786

[EAGLE-877] Rename metric hadoop.hbase.ipc.ipc.* to 
hadoop.hbase.regionserver.ipc.*

Rename metric "hadoop.hbase.ipc.ipc." to "hadoop.hbase.regionserver.ipc." 
to support different hbase version metrics.

https://issues.apache.org/jira/browse/EAGLE-877

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/haoch/eagle EAGLE-877

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/eagle/pull/786.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #786


commit 439bb368d9291f065d4397935a0b9ca49bb5ec7c
Author: Hao Chen 
Date:   2017-01-19T09:42:35Z

Rename metric hadoop.hbase.ipc.ipc.* to hadoop.hbase.regionserver.ipc.* to 
support different hbase version metric




> Rename metric "hadoop.hbase.ipc.ipc.*" to "hadoop.hbase.regionserver.ipc.*" 
> to support different hbase version metric
> -
>
> Key: EAGLE-877
> URL: https://issues.apache.org/jira/browse/EAGLE-877
> Project: Eagle
>  Issue Type: Sub-task
>  Components: Hadoop JMX Monitor
>Affects Versions: v0.5.0
>Reporter: Hao Chen
>Assignee: Hao Chen
> Fix For: v0.5.0
>
>
> Rename metric "hadoop.hbase.ipc.ipc.*" to "hadoop.hbase.regionserver.ipc.*" 
> to support different hbase version metric



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[GitHub] eagle pull request #786: [EAGLE-877] Rename metric hadoop.hbase.ipc.ipc.* to...

2017-01-19 Thread haoch
GitHub user haoch opened a pull request:

https://github.com/apache/eagle/pull/786

[EAGLE-877] Rename metric hadoop.hbase.ipc.ipc.* to 
hadoop.hbase.regionserver.ipc.*

Rename metric "hadoop.hbase.ipc.ipc." to "hadoop.hbase.regionserver.ipc." 
to support different hbase version metrics.

https://issues.apache.org/jira/browse/EAGLE-877

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/haoch/eagle EAGLE-877

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/eagle/pull/786.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #786


commit 439bb368d9291f065d4397935a0b9ca49bb5ec7c
Author: Hao Chen 
Date:   2017-01-19T09:42:35Z

Rename metric hadoop.hbase.ipc.ipc.* to hadoop.hbase.regionserver.ipc.* to 
support different hbase version metric




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[jira] [Commented] (EAGLE-859) MR job performance suggestion

2017-01-19 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/EAGLE-859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15829615#comment-15829615
 ] 

ASF GitHub Bot commented on EAGLE-859:
--

Github user qingwen220 commented on the issue:

https://github.com/apache/eagle/pull/784
  
@r7raul1984  Fixed. Thanks


> MR job performance suggestion
> -
>
> Key: EAGLE-859
> URL: https://issues.apache.org/jira/browse/EAGLE-859
> Project: Eagle
>  Issue Type: New Feature
>Affects Versions: v0.5.0
>Reporter: Zhao, Qingwen
>Assignee: Zhao, Qingwen
>
> Analyze a mapreduce job performance from the following aspects
> * compression setting anaysis
> * split setting analysis
> * spill analysis
> * mapreduce task num analysis
> * data skew analysis
> * GC time analysis



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[GitHub] eagle issue #784: EAGLE-859 MapReduce job performance suggestion

2017-01-19 Thread qingwen220
Github user qingwen220 commented on the issue:

https://github.com/apache/eagle/pull/784
  
@r7raul1984  Fixed. Thanks


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[jira] [Updated] (EAGLE-877) Rename metric "hadoop.hbase.ipc.ipc.*" to "hadoop.hbase.regionserver.ipc.*" to support different hbase version metric

2017-01-19 Thread Hao Chen (JIRA)

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

Hao Chen updated EAGLE-877:
---
Description: Rename metric "hadoop.hbase.ipc.ipc.*" to 
"hadoop.hbase.regionserver.ipc.*" to support different hbase version metric  
(was: Fix hadoop.hbase.ipc.ipc.* metric to hadoop.hbase.regionserver.ipc.* in 
collector script)

> Rename metric "hadoop.hbase.ipc.ipc.*" to "hadoop.hbase.regionserver.ipc.*" 
> to support different hbase version metric
> -
>
> Key: EAGLE-877
> URL: https://issues.apache.org/jira/browse/EAGLE-877
> Project: Eagle
>  Issue Type: Sub-task
>  Components: Hadoop JMX Monitor
>Affects Versions: v0.5.0
>Reporter: Hao Chen
>Assignee: Hao Chen
> Fix For: v0.5.0
>
>
> Rename metric "hadoop.hbase.ipc.ipc.*" to "hadoop.hbase.regionserver.ipc.*" 
> to support different hbase version metric



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (EAGLE-877) Rename metric "hadoop.hbase.ipc.ipc.*" to "hadoop.hbase.regionserver.ipc.*" to support different hbase version metric

2017-01-19 Thread Hao Chen (JIRA)

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

Hao Chen updated EAGLE-877:
---
Summary: Rename metric "hadoop.hbase.ipc.ipc.*" to 
"hadoop.hbase.regionserver.ipc.*" to support different hbase version metric  
(was: Fix hadoop.hbase.ipc.ipc.* metric to hadoop.hbase.regionserver.ipc.* in 
collector script)

> Rename metric "hadoop.hbase.ipc.ipc.*" to "hadoop.hbase.regionserver.ipc.*" 
> to support different hbase version metric
> -
>
> Key: EAGLE-877
> URL: https://issues.apache.org/jira/browse/EAGLE-877
> Project: Eagle
>  Issue Type: Sub-task
>  Components: Hadoop JMX Monitor
>Affects Versions: v0.5.0
>Reporter: Hao Chen
>Assignee: Hao Chen
> Fix For: v0.5.0
>
>
> Fix hadoop.hbase.ipc.ipc.* metric to hadoop.hbase.regionserver.ipc.* in 
> collector script



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Created] (EAGLE-877) Fix hadoop.hbase.ipc.ipc.* metric to hadoop.hbase.regionserver.ipc.* in collector script

2017-01-19 Thread Hao Chen (JIRA)
Hao Chen created EAGLE-877:
--

 Summary: Fix hadoop.hbase.ipc.ipc.* metric to 
hadoop.hbase.regionserver.ipc.* in collector script
 Key: EAGLE-877
 URL: https://issues.apache.org/jira/browse/EAGLE-877
 Project: Eagle
  Issue Type: Sub-task
  Components: Hadoop JMX Monitor
Affects Versions: v0.5.0
Reporter: Hao Chen
Assignee: Hao Chen
 Fix For: v0.5.0


Fix hadoop.hbase.ipc.ipc.* metric to hadoop.hbase.regionserver.ipc.* in 
collector script



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (EAGLE-876) TopologyBaseAPIEntity comparison should consider rack info

2017-01-19 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/EAGLE-876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15829566#comment-15829566
 ] 

ASF GitHub Bot commented on EAGLE-876:
--

GitHub user qingwen220 opened a pull request:

https://github.com/apache/eagle/pull/785

EAGLE-876 TopologyBaseAPIEntity comparison should consider rack info

https://issues.apache.org/jira/browse/EAGLE-876

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/qingwen220/incubator-eagle EAGLE-876

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/eagle/pull/785.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #785


commit cb7f41d48081e078b131419a78a3b110856f6867
Author: Zhao, Qingwen 
Date:   2017-01-19T09:05:41Z

Fix persisting key

commit 8205d99d075ac1ac90c43072f51f819592cb1d35
Author: Zhao, Qingwen 
Date:   2017-01-19T09:11:04Z

fix conflicts

commit 03cfcb139861696160a3c257b090ddb13a2ca89a
Author: Zhao, Qingwen 
Date:   2017-01-19T09:13:05Z

Merge branch 'EAGLE-876' of https://github.com/qingwen220/incubator-eagle 
into EAGLE-876




> TopologyBaseAPIEntity comparison should consider rack info
> --
>
> Key: EAGLE-876
> URL: https://issues.apache.org/jira/browse/EAGLE-876
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: Zhao, Qingwen
>Assignee: Zhao, Qingwen
> Fix For: v0.5.0
>
>
> TopologyBaseAPIEntity comparison should consider rack info



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[GitHub] eagle pull request #785: EAGLE-876 TopologyBaseAPIEntity comparison should c...

2017-01-19 Thread qingwen220
GitHub user qingwen220 opened a pull request:

https://github.com/apache/eagle/pull/785

EAGLE-876 TopologyBaseAPIEntity comparison should consider rack info

https://issues.apache.org/jira/browse/EAGLE-876

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/qingwen220/incubator-eagle EAGLE-876

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/eagle/pull/785.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #785


commit cb7f41d48081e078b131419a78a3b110856f6867
Author: Zhao, Qingwen 
Date:   2017-01-19T09:05:41Z

Fix persisting key

commit 8205d99d075ac1ac90c43072f51f819592cb1d35
Author: Zhao, Qingwen 
Date:   2017-01-19T09:11:04Z

fix conflicts

commit 03cfcb139861696160a3c257b090ddb13a2ca89a
Author: Zhao, Qingwen 
Date:   2017-01-19T09:13:05Z

Merge branch 'EAGLE-876' of https://github.com/qingwen220/incubator-eagle 
into EAGLE-876




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[jira] [Updated] (EAGLE-876) TopologyBaseAPIEntity comparison should consider rack info

2017-01-19 Thread Zhao, Qingwen (JIRA)

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

Zhao, Qingwen updated EAGLE-876:

Fix Version/s: v0.5.0

> TopologyBaseAPIEntity comparison should consider rack info
> --
>
> Key: EAGLE-876
> URL: https://issues.apache.org/jira/browse/EAGLE-876
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: Zhao, Qingwen
>Assignee: Zhao, Qingwen
> Fix For: v0.5.0
>
>
> TopologyBaseAPIEntity comparison should consider rack info



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (EAGLE-876) TopologyBaseAPIEntity comparison should consider rack info

2017-01-19 Thread Zhao, Qingwen (JIRA)

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

Zhao, Qingwen updated EAGLE-876:

Affects Version/s: v0.5.0

> TopologyBaseAPIEntity comparison should consider rack info
> --
>
> Key: EAGLE-876
> URL: https://issues.apache.org/jira/browse/EAGLE-876
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: Zhao, Qingwen
>Assignee: Zhao, Qingwen
> Fix For: v0.5.0
>
>
> TopologyBaseAPIEntity comparison should consider rack info



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Created] (EAGLE-876) TopologyBaseAPIEntity comparison should consider rack info

2017-01-19 Thread Zhao, Qingwen (JIRA)
Zhao, Qingwen created EAGLE-876:
---

 Summary: TopologyBaseAPIEntity comparison should consider rack info
 Key: EAGLE-876
 URL: https://issues.apache.org/jira/browse/EAGLE-876
 Project: Eagle
  Issue Type: Bug
Reporter: Zhao, Qingwen
Assignee: Zhao, Qingwen


TopologyBaseAPIEntity comparison should consider rack info



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (EAGLE-875) Fix hadoop.hbase.ipc.ipc.* metric to hadoop.hbase.regionserver.ipc.*

2017-01-19 Thread Hao Chen (JIRA)

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

Hao Chen updated EAGLE-875:
---
Description: 
* Fix *hadoop.hbase.ipc.ipc.** metric to *hadoop.hbase.regionserver.ipc.** in 
collector script 
* Fix region server monitoring UI to use *hadoop.hbase.regionserver.ipc.** 
instead of *hadoop.hbase.ipc.ipc.**

  was:
* Fix *hadoop.hbase.ipc.ipc.** metric to *hadoop.hbase.regionserver.ipc.** in 
collector script 
* Fix region server monitoring UI using "hadoop.hbase.ipc.ipc.*"


> Fix hadoop.hbase.ipc.ipc.* metric to hadoop.hbase.regionserver.ipc.*
> 
>
> Key: EAGLE-875
> URL: https://issues.apache.org/jira/browse/EAGLE-875
> Project: Eagle
>  Issue Type: Improvement
>  Components: Hadoop JMX Monitor
>Affects Versions: v0.5.0
>Reporter: Hao Chen
>Assignee: Hao Chen
> Fix For: v0.5.0
>
>
> * Fix *hadoop.hbase.ipc.ipc.** metric to *hadoop.hbase.regionserver.ipc.** in 
> collector script 
> * Fix region server monitoring UI to use *hadoop.hbase.regionserver.ipc.** 
> instead of *hadoop.hbase.ipc.ipc.**



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (EAGLE-875) Fix hadoop.hbase.ipc.ipc.* metric to hadoop.hbase.regionserver.ipc.*

2017-01-19 Thread Hao Chen (JIRA)

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

Hao Chen updated EAGLE-875:
---
Description: 
* Fix *hadoop.hbase.ipc.ipc.** metric to *hadoop.hbase.regionserver.ipc.** in 
collector script 
* Fix region server monitoring UI using "hadoop.hbase.ipc.ipc.*"

  was:
* Fix "hadoop.hbase.ipc.ipc.*" metric to "hadoop.hbase.regionserver.ipc.*" in 
collector script 
* Fix region server monitoring UI using "hadoop.hbase.ipc.ipc.*"


> Fix hadoop.hbase.ipc.ipc.* metric to hadoop.hbase.regionserver.ipc.*
> 
>
> Key: EAGLE-875
> URL: https://issues.apache.org/jira/browse/EAGLE-875
> Project: Eagle
>  Issue Type: Improvement
>  Components: Hadoop JMX Monitor
>Affects Versions: v0.5.0
>Reporter: Hao Chen
>Assignee: Hao Chen
> Fix For: v0.5.0
>
>
> * Fix *hadoop.hbase.ipc.ipc.** metric to *hadoop.hbase.regionserver.ipc.** in 
> collector script 
> * Fix region server monitoring UI using "hadoop.hbase.ipc.ipc.*"



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Created] (EAGLE-875) Fix hadoop.hbase.ipc.ipc.* metric to hadoop.hbase.regionserver.ipc.*

2017-01-19 Thread Hao Chen (JIRA)
Hao Chen created EAGLE-875:
--

 Summary: Fix hadoop.hbase.ipc.ipc.* metric to 
hadoop.hbase.regionserver.ipc.*
 Key: EAGLE-875
 URL: https://issues.apache.org/jira/browse/EAGLE-875
 Project: Eagle
  Issue Type: Improvement
  Components: Hadoop JMX Monitor
Affects Versions: v0.5.0
Reporter: Hao Chen
Assignee: Hao Chen
 Fix For: v0.5.0


* Fix "hadoop.hbase.ipc.ipc.*" metric to "hadoop.hbase.regionserver.ipc.*" in 
collector script 
* Fix region server monitoring UI using "hadoop.hbase.ipc.ipc.*"



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (EAGLE-859) MR job performance suggestion

2017-01-19 Thread Zhao, Qingwen (JIRA)

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

Zhao, Qingwen updated EAGLE-859:

Description: 
Analyze a mapreduce job performance from the following aspects
* compression setting anaysis
* split setting analysis
* spill analysis
* mapreduce task num analysis
* data skew analysis
* GC time analysis

  was:
Analyze a mapreduce job performance from the following aspects
* compression setting anaysis
* split setting analysis
* spill analysis
* mapreduce task num analysis
* data skew analysis
* GC time analysis
* queue resource analysis


> MR job performance suggestion
> -
>
> Key: EAGLE-859
> URL: https://issues.apache.org/jira/browse/EAGLE-859
> Project: Eagle
>  Issue Type: New Feature
>Affects Versions: v0.5.0
>Reporter: Zhao, Qingwen
>Assignee: Zhao, Qingwen
>
> Analyze a mapreduce job performance from the following aspects
> * compression setting anaysis
> * split setting analysis
> * spill analysis
> * mapreduce task num analysis
> * data skew analysis
> * GC time analysis



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Created] (EAGLE-874) Improve hadoop jmx collector scripts

2017-01-19 Thread Hao Chen (JIRA)
Hao Chen created EAGLE-874:
--

 Summary: Improve hadoop jmx collector scripts
 Key: EAGLE-874
 URL: https://issues.apache.org/jira/browse/EAGLE-874
 Project: Eagle
  Issue Type: Improvement
  Components: Hadoop JMX Monitor
Affects Versions: v0.5.0
Reporter: Hao Chen
Assignee: Hao Chen
 Fix For: v0.5.0


* Handle IPC metrics name for different version
* Add JMX API query filter to reduce throughput from monitored service.




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Created] (EAGLE-873) Add job name column to let user search their jobs using that field

2017-01-19 Thread jianzhong.chen (JIRA)
jianzhong.chen created EAGLE-873:


 Summary: Add job name column to let user search their jobs using 
that field
 Key: EAGLE-873
 URL: https://issues.apache.org/jira/browse/EAGLE-873
 Project: Eagle
  Issue Type: Improvement
  Components: Job Performance Monitor
Reporter: jianzhong.chen
Assignee: Lingang Deng
Priority: Minor
 Fix For: v0.5.0


lgdeng, please help to add this field in JPM job list.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)