Jilin, Jiang created EAGLE-949:
--
Summary: JPM support job level suggestion
Key: EAGLE-949
URL: https://issues.apache.org/jira/browse/EAGLE-949
Project: Eagle
Issue Type: Improvement
[
https://issues.apache.org/jira/browse/EAGLE-945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on EAGLE-945 started by Jilin, Jiang.
--
> JPM support queue level overview
>
>
>
Han Hui Wen created EAGLE-948:
--
Summary: can not package by maven
Key: EAGLE-948
URL: https://issues.apache.org/jira/browse/EAGLE-948
Project: Eagle
Issue Type: Bug
Components:
Github user RalphSu commented on the issue:
https://github.com/apache/eagle/pull/864
@wujinhu @haoch
Please help review this 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
Github user qingwen220 commented on the issue:
https://github.com/apache/eagle/pull/861
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
[
https://issues.apache.org/jira/browse/EAGLE-947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Garrett Li resolved EAGLE-947.
--
Resolution: Fixed
fixed by PR - https://github.com/apache/eagle/pull/864
> Publishers with same policy
GitHub user garrettlish opened a pull request:
https://github.com/apache/eagle/pull/864
[EAGLE-947] Publishers with same policy but different schema could produce
duplicate alerts
Assume that we have policy1 which have 2 kinds of output streams, one is
stream1 and another is
[
https://issues.apache.org/jira/browse/EAGLE-947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Garrett Li updated EAGLE-947:
-
Summary: Publishers with same policy but different schema could produce
duplicate alerts (was: Publishers
Garrett Li created EAGLE-947:
Summary: Publishers with different schema could produce duplicate
alerts
Key: EAGLE-947
URL: https://issues.apache.org/jira/browse/EAGLE-947
Project: Eagle
Issue
Github user asfgit closed the pull request at:
https://github.com/apache/eagle/pull/863
---
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
Zhao, Qingwen created EAGLE-946:
---
Summary: Refactor MRRunningJobApp & HadoopQueueApp
Key: EAGLE-946
URL: https://issues.apache.org/jira/browse/EAGLE-946
Project: Eagle
Issue Type: Improvement
[
https://issues.apache.org/jira/browse/EAGLE-940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhao, Qingwen updated EAGLE-940:
Description:
Monitor HDFS RPC requests at a cluster/user level. This feature leverage the
available
[
https://issues.apache.org/jira/browse/EAGLE-940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhao, Qingwen updated EAGLE-940:
Description:
Monitor HDFS RPC requests at a cluster/user level. This feature leverage the
available
[
https://issues.apache.org/jira/browse/EAGLE-940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhao, Qingwen updated EAGLE-940:
Description:
* monitor HDFS RPC requests at a cluster/user level
* refactor all apps which consume
[
https://issues.apache.org/jira/browse/EAGLE-940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15902686#comment-15902686
]
ASF GitHub Bot commented on EAGLE-940:
--
GitHub user qingwen220 opened a pull request:
GitHub user qingwen220 opened a pull request:
https://github.com/apache/eagle/pull/862
EAGLE-940: HDFS traffic monitor by the namenode jmx data
https://issues.apache.org/jira/browse/EAGLE-940
You can merge this pull request into a Git repository by running:
$ git pull
16 matches
Mail list logo