[jira] [Commented] (EAGLE-697) wrong metric url composed when endpoint url doesn't end with a slash
[ https://issues.apache.org/jira/browse/EAGLE-697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15614542#comment-15614542 ] ASF GitHub Bot commented on EAGLE-697: -- Github user wujinhu commented on the issue: https://github.com/apache/incubator-eagle/pull/578 Reviewed, pls merge > wrong metric url composed when endpoint url doesn't end with a slash > > > Key: EAGLE-697 > URL: https://issues.apache.org/jira/browse/EAGLE-697 > Project: Eagle > Issue Type: Bug >Reporter: Michael Wu >Assignee: Michael Wu > > For hadoop queue monitoring, when endpoint url doesn't end with a slash, the > final url will be composed by concatenating endpoint directly with resource > path. E.g. > endpoint: https://a.b.c: > resource path: ws/v1/cluster/some > Then final url is: https://a.b.c:ws/v1/cluster/some, which make > application fail. > We should add "/" to existing constants of resource paths, and compose final > url with utils. > Besides, add concrete unit test to guarantee this part functions normally. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (EAGLE-683) AlertEngine : Improve metadata store performance
[
https://issues.apache.org/jira/browse/EAGLE-683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15614584#comment-15614584
]
ASF GitHub Bot commented on EAGLE-683:
--
Github user RalphSu commented on a diff in the pull request:
https://github.com/apache/incubator-eagle/pull/566#discussion_r85466631
--- Diff:
eagle-core/eagle-alert-parent/eagle-alert/alert-metadata-parent/alert-metadata/src/main/java/org/apache/eagle/alert/metadata/impl/MongoMetadataDaoImpl.java
---
@@ -127,41 +157,41 @@ private void init() {
BsonDocument doc1 = new BsonDocument();
IndexOptions io1 = new
IndexOptions().background(true).name("versionIndex");
doc1.append("version", new BsonInt32(1));
-scheduleStates = db.getCollection("schedule_specs");
+scheduleStates = getCollection("schedule_specs");
scheduleStates.createIndex(doc1, io1);
-spoutSpecs = db.getCollection("spoutSpecs");
+spoutSpecs = getCollection("spoutSpecs");
{
IndexOptions ioInternal = new
IndexOptions().background(true).name("topologyIdIndex");
BsonDocument docInternal = new BsonDocument();
docInternal.append("topologyId", new BsonInt32(1));
spoutSpecs.createIndex(docInternal, ioInternal);
}
-alertSpecs = db.getCollection("alertSpecs");
+alertSpecs = getCollection("alertSpecs");
{
IndexOptions ioInternal = new
IndexOptions().background(true).name("topologyNameIndex");
BsonDocument docInternal = new BsonDocument();
docInternal.append("topologyName", new BsonInt32(1));
alertSpecs.createIndex(docInternal, ioInternal);
}
-groupSpecs = db.getCollection("groupSpecs");
+groupSpecs = getCollection("groupSpecs");
--- End diff --
The getCollection method will make all the collection as capped. Capped
should only apply for collections that related to schedule specs that listed on
the jira. Please make sure the impact of the code change.
> AlertEngine : Improve metadata store performance
>
>
> Key: EAGLE-683
> URL: https://issues.apache.org/jira/browse/EAGLE-683
> Project: Eagle
> Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Su Ralph
>Assignee: Zeng, Bryant
> Fix For: v0.5.0
>
>
> Currently, we enable periodically schedule in coordinator service itself. If
> this is enabled, the schedule spec will finally used up metadata storage.
> We should
> 1. Disable periodically schedule by default (storage like mysql doesn't have
> capped feature)
> 2. For mongodb storage, use capped collection for schedule_specs,
> policy_snapshots, streamSnapshots, groupSpecs, alertSpecs, monitoredStreams,
> spoutSpecs (all schedule spec related collection).
> Let use default config of 20,000 as capped collection size.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (EAGLE-683) AlertEngine : Improve metadata store performance
[
https://issues.apache.org/jira/browse/EAGLE-683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15614592#comment-15614592
]
ASF GitHub Bot commented on EAGLE-683:
--
Github user mizeng commented on a diff in the pull request:
https://github.com/apache/incubator-eagle/pull/566#discussion_r85482632
--- Diff:
eagle-core/eagle-alert-parent/eagle-alert/alert-metadata-parent/alert-metadata/src/main/java/org/apache/eagle/alert/metadata/impl/MongoMetadataDaoImpl.java
---
@@ -127,41 +157,41 @@ private void init() {
BsonDocument doc1 = new BsonDocument();
IndexOptions io1 = new
IndexOptions().background(true).name("versionIndex");
doc1.append("version", new BsonInt32(1));
-scheduleStates = db.getCollection("schedule_specs");
+scheduleStates = getCollection("schedule_specs");
scheduleStates.createIndex(doc1, io1);
-spoutSpecs = db.getCollection("spoutSpecs");
+spoutSpecs = getCollection("spoutSpecs");
{
IndexOptions ioInternal = new
IndexOptions().background(true).name("topologyIdIndex");
BsonDocument docInternal = new BsonDocument();
docInternal.append("topologyId", new BsonInt32(1));
spoutSpecs.createIndex(docInternal, ioInternal);
}
-alertSpecs = db.getCollection("alertSpecs");
+alertSpecs = getCollection("alertSpecs");
{
IndexOptions ioInternal = new
IndexOptions().background(true).name("topologyNameIndex");
BsonDocument docInternal = new BsonDocument();
docInternal.append("topologyName", new BsonInt32(1));
alertSpecs.createIndex(docInternal, ioInternal);
}
-groupSpecs = db.getCollection("groupSpecs");
+groupSpecs = getCollection("groupSpecs");
--- End diff --
groupSpecs is part of schedule specs..
> AlertEngine : Improve metadata store performance
>
>
> Key: EAGLE-683
> URL: https://issues.apache.org/jira/browse/EAGLE-683
> Project: Eagle
> Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Su Ralph
>Assignee: Zeng, Bryant
> Fix For: v0.5.0
>
>
> Currently, we enable periodically schedule in coordinator service itself. If
> this is enabled, the schedule spec will finally used up metadata storage.
> We should
> 1. Disable periodically schedule by default (storage like mysql doesn't have
> capped feature)
> 2. For mongodb storage, use capped collection for schedule_specs,
> policy_snapshots, streamSnapshots, groupSpecs, alertSpecs, monitoredStreams,
> spoutSpecs (all schedule spec related collection).
> Let use default config of 20,000 as capped collection size.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (EAGLE-683) AlertEngine : Improve metadata store performance
[
https://issues.apache.org/jira/browse/EAGLE-683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15614585#comment-15614585
]
ASF GitHub Bot commented on EAGLE-683:
--
Github user RalphSu commented on a diff in the pull request:
https://github.com/apache/incubator-eagle/pull/566#discussion_r85466419
--- Diff:
eagle-core/eagle-alert-parent/eagle-alert/alert-metadata-parent/alert-metadata/src/main/java/org/apache/eagle/alert/metadata/impl/MongoMetadataDaoImpl.java
---
@@ -89,10 +92,37 @@
@Inject
public MongoMetadataDaoImpl(Config config) {
this.connection = config.getString("connection");
+this.cappedSize = config.hasPath("cappedSize") ?
config.getInt("cappedSize") : 0;
--- End diff --
cappedSize default as 0? why not set it some reasonable value, and i saw
this is set as size in byte. should it be better to control the size in
document number. please check the maxDocuments in CreateCollectionOptions.
> AlertEngine : Improve metadata store performance
>
>
> Key: EAGLE-683
> URL: https://issues.apache.org/jira/browse/EAGLE-683
> Project: Eagle
> Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Su Ralph
>Assignee: Zeng, Bryant
> Fix For: v0.5.0
>
>
> Currently, we enable periodically schedule in coordinator service itself. If
> this is enabled, the schedule spec will finally used up metadata storage.
> We should
> 1. Disable periodically schedule by default (storage like mysql doesn't have
> capped feature)
> 2. For mongodb storage, use capped collection for schedule_specs,
> policy_snapshots, streamSnapshots, groupSpecs, alertSpecs, monitoredStreams,
> spoutSpecs (all schedule spec related collection).
> Let use default config of 20,000 as capped collection size.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (EAGLE-697) wrong metric url composed when endpoint url doesn't end with a slash
[ https://issues.apache.org/jira/browse/EAGLE-697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Wu closed EAGLE-697. > wrong metric url composed when endpoint url doesn't end with a slash > > > Key: EAGLE-697 > URL: https://issues.apache.org/jira/browse/EAGLE-697 > Project: Eagle > Issue Type: Bug >Reporter: Michael Wu >Assignee: Michael Wu > > For hadoop queue monitoring, when endpoint url doesn't end with a slash, the > final url will be composed by concatenating endpoint directly with resource > path. E.g. > endpoint: https://a.b.c: > resource path: ws/v1/cluster/some > Then final url is: https://a.b.c:ws/v1/cluster/some, which make > application fail. > We should add "/" to existing constants of resource paths, and compose final > url with utils. > Besides, add concrete unit test to guarantee this part functions normally. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (EAGLE-695) change to fetching hadoop.cluster.allocatedvirtualcores instead of hadoop.cluster.totalvirtualcores
[ https://issues.apache.org/jira/browse/EAGLE-695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Wu closed EAGLE-695. > change to fetching hadoop.cluster.allocatedvirtualcores instead of > hadoop.cluster.totalvirtualcores > --- > > Key: EAGLE-695 > URL: https://issues.apache.org/jira/browse/EAGLE-695 > Project: Eagle > Issue Type: Task >Reporter: Michael Wu >Assignee: Michael Wu > > Virtual Core related metrics are additional, starting from hadoop version > 2.7.x. And we were originally fetching hadoop.cluster.allocatedvirtualcores. > Now it seems that hadoop.cluster.totalvirtualcores is more meaningful. So > change code to fetch and show it up in hadoop-queue monitoring application. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-eagle pull request #579: [EAGLE-700] API /policies/{policyId} thro...
Github user asfgit closed the pull request at: https://github.com/apache/incubator-eagle/pull/579 --- 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-700) API /policies/{policyId} throws exception if policy does not exist
[
https://issues.apache.org/jira/browse/EAGLE-700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15614699#comment-15614699
]
ASF GitHub Bot commented on EAGLE-700:
--
Github user asfgit closed the pull request at:
https://github.com/apache/incubator-eagle/pull/579
> API /policies/{policyId} throws exception if policy does not exist
> --
>
> Key: EAGLE-700
> URL: https://issues.apache.org/jira/browse/EAGLE-700
> Project: Eagle
> Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: wujinhu
>Assignee: wujinhu
> Fix For: v0.5.0
>
>
> API /policies/{policyId} throws exception if policy does not exist
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[GitHub] incubator-eagle pull request #566: EAGLE-683: Improve metadata store perform...
Github user RalphSu commented on a diff in the pull request:
https://github.com/apache/incubator-eagle/pull/566#discussion_r85466631
--- Diff:
eagle-core/eagle-alert-parent/eagle-alert/alert-metadata-parent/alert-metadata/src/main/java/org/apache/eagle/alert/metadata/impl/MongoMetadataDaoImpl.java
---
@@ -127,41 +157,41 @@ private void init() {
BsonDocument doc1 = new BsonDocument();
IndexOptions io1 = new
IndexOptions().background(true).name("versionIndex");
doc1.append("version", new BsonInt32(1));
-scheduleStates = db.getCollection("schedule_specs");
+scheduleStates = getCollection("schedule_specs");
scheduleStates.createIndex(doc1, io1);
-spoutSpecs = db.getCollection("spoutSpecs");
+spoutSpecs = getCollection("spoutSpecs");
{
IndexOptions ioInternal = new
IndexOptions().background(true).name("topologyIdIndex");
BsonDocument docInternal = new BsonDocument();
docInternal.append("topologyId", new BsonInt32(1));
spoutSpecs.createIndex(docInternal, ioInternal);
}
-alertSpecs = db.getCollection("alertSpecs");
+alertSpecs = getCollection("alertSpecs");
{
IndexOptions ioInternal = new
IndexOptions().background(true).name("topologyNameIndex");
BsonDocument docInternal = new BsonDocument();
docInternal.append("topologyName", new BsonInt32(1));
alertSpecs.createIndex(docInternal, ioInternal);
}
-groupSpecs = db.getCollection("groupSpecs");
+groupSpecs = getCollection("groupSpecs");
--- End diff --
The getCollection method will make all the collection as capped. Capped
should only apply for collections that related to schedule specs that listed on
the jira. Please make sure the impact of the code 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] [Resolved] (EAGLE-688) UI support Alert display
[ https://issues.apache.org/jira/browse/EAGLE-688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jilin, Jiang resolved EAGLE-688. Resolution: Fixed > UI support Alert display > > > Key: EAGLE-688 > URL: https://issues.apache.org/jira/browse/EAGLE-688 > Project: Eagle > Issue Type: New Feature >Affects Versions: v0.5.0 >Reporter: Jilin, Jiang >Assignee: Jilin, Jiang > Fix For: v0.5.0 > > > For backend will provide the alert api. UI will also support it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (EAGLE-697) wrong metric url composed when endpoint url doesn't end with a slash
[ https://issues.apache.org/jira/browse/EAGLE-697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15614645#comment-15614645 ] ASF GitHub Bot commented on EAGLE-697: -- Github user asfgit closed the pull request at: https://github.com/apache/incubator-eagle/pull/578 > wrong metric url composed when endpoint url doesn't end with a slash > > > Key: EAGLE-697 > URL: https://issues.apache.org/jira/browse/EAGLE-697 > Project: Eagle > Issue Type: Bug >Reporter: Michael Wu >Assignee: Michael Wu > > For hadoop queue monitoring, when endpoint url doesn't end with a slash, the > final url will be composed by concatenating endpoint directly with resource > path. E.g. > endpoint: https://a.b.c: > resource path: ws/v1/cluster/some > Then final url is: https://a.b.c:ws/v1/cluster/some, which make > application fail. > We should add "/" to existing constants of resource paths, and compose final > url with utils. > Besides, add concrete unit test to guarantee this part functions normally. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-eagle pull request #576: Eagle-688 UI support Alert display
Github user asfgit closed the pull request at: https://github.com/apache/incubator-eagle/pull/576 --- 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-693) fix application could not detect stream change
[ https://issues.apache.org/jira/browse/EAGLE-693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15614887#comment-15614887 ] ASF GitHub Bot commented on EAGLE-693: -- GitHub user wujinhu opened a pull request: https://github.com/apache/incubator-eagle/pull/580 [EAGLE-693] fix application could not detect stream change You can merge this pull request into a Git repository by running: $ git pull https://github.com/wujinhu/incubator-eagle EAGLE-700 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-eagle/pull/580.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 #580 commit 4a32d92193ad5f48fb0dd9f59ac2070b55ad9c62 Author: wujinhu Date: 2016-10-28T09:25:16Z fix application could not detect stream change > fix application could not detect stream change > -- > > Key: EAGLE-693 > URL: https://issues.apache.org/jira/browse/EAGLE-693 > Project: Eagle > Issue Type: Bug >Affects Versions: v0.5.0 >Reporter: wujinhu >Assignee: wujinhu > Fix For: v0.5.0 > > > After an application is running, user may want to add streams to it.But when > user updates the application, application framework does not update streams. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-eagle pull request #574: [Eagle 695] fetching hadoop.cluster.alloc...
Github user asfgit closed the pull request at: https://github.com/apache/incubator-eagle/pull/574 --- 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] incubator-eagle pull request #578: [EAGLE-697] fix wrong url-concatenation f...
GitHub user anyway1021 opened a pull request: https://github.com/apache/incubator-eagle/pull/578 [EAGLE-697] fix wrong url-concatenation for monitoring hadoop queue For hadoop queue monitoring, when endpoint url doesn't end with a slash, the final url will be composed by concatenating endpoint directly with resource path. E.g. endpoint: https://a.b.c: resource path: ws/v1/cluster/some Then final url is: https://a.b.c:ws/v1/cluster/some, which make application fail. We should add "/" to existing constants of resource paths, and compose final url with utils. Besides, add concrete unit test to guarantee this part functions normally. You can merge this pull request into a Git repository by running: $ git pull https://github.com/anyway1021/incubator-eagle EAGLE-697 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-eagle/pull/578.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 #578 commit 8dd95bd25de917d81592292a2f245670106e6b4c Author: anyway1021 Date: 2016-10-28T04:17:28Z fix wrong url-concatenation for monitoring hadoop queue, also add unit tests --- 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] incubator-eagle pull request #580: [EAGLE-693] fix application could not det...
GitHub user wujinhu opened a pull request: https://github.com/apache/incubator-eagle/pull/580 [EAGLE-693] fix application could not detect stream change You can merge this pull request into a Git repository by running: $ git pull https://github.com/wujinhu/incubator-eagle EAGLE-700 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-eagle/pull/580.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 #580 commit 4a32d92193ad5f48fb0dd9f59ac2070b55ad9c62 Author: wujinhu Date: 2016-10-28T09:25:16Z fix application could not detect stream 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. ---
[GitHub] incubator-eagle pull request #577: [EAGLE-694] alert engine could not reduce...
Github user asfgit closed the pull request at: https://github.com/apache/incubator-eagle/pull/577 --- 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-694) alert engine could not reduce alert bolt number when parallelism of policy reduces
[ https://issues.apache.org/jira/browse/EAGLE-694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15614535#comment-15614535 ] ASF GitHub Bot commented on EAGLE-694: -- Github user asfgit closed the pull request at: https://github.com/apache/incubator-eagle/pull/577 > alert engine could not reduce alert bolt number when parallelism of policy > reduces > -- > > Key: EAGLE-694 > URL: https://issues.apache.org/jira/browse/EAGLE-694 > Project: Eagle > Issue Type: Bug >Reporter: wujinhu >Assignee: wujinhu > > alert engine could not reduce alert bolt number when parallelism of policy > reduces -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-eagle issue #578: [EAGLE-697] fix wrong url-concatenation for moni...
Github user wujinhu commented on the issue: https://github.com/apache/incubator-eagle/pull/578 Reviewed, pls merge --- 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-693) fix application could not detect stream change
[ https://issues.apache.org/jira/browse/EAGLE-693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15614957#comment-15614957 ] ASF GitHub Bot commented on EAGLE-693: -- Github user wujinhu closed the pull request at: https://github.com/apache/incubator-eagle/pull/580 > fix application could not detect stream change > -- > > Key: EAGLE-693 > URL: https://issues.apache.org/jira/browse/EAGLE-693 > Project: Eagle > Issue Type: Bug >Affects Versions: v0.5.0 >Reporter: wujinhu >Assignee: wujinhu > Fix For: v0.5.0 > > > After an application is running, user may want to add streams to it.But when > user updates the application, application framework does not update streams. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-eagle pull request #580: [EAGLE-693] fix application could not det...
Github user wujinhu closed the pull request at: https://github.com/apache/incubator-eagle/pull/580 --- 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] incubator-eagle pull request #580: [EAGLE-693] fix application could not det...
GitHub user wujinhu reopened a pull request: https://github.com/apache/incubator-eagle/pull/580 [EAGLE-693] fix application could not detect stream change You can merge this pull request into a Git repository by running: $ git pull https://github.com/wujinhu/incubator-eagle EAGLE-700 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-eagle/pull/580.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 #580 commit 4a32d92193ad5f48fb0dd9f59ac2070b55ad9c62 Author: wujinhu Date: 2016-10-28T09:25:16Z fix application could not detect stream 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] [Updated] (EAGLE-696) Improve HdfsAuditLogApplication & AlertUnitTopologyApp config
[ https://issues.apache.org/jira/browse/EAGLE-696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhao, Qingwen updated EAGLE-696: Description: add field display name & refactor the configuration organization > Improve HdfsAuditLogApplication & AlertUnitTopologyApp config > -- > > Key: EAGLE-696 > URL: https://issues.apache.org/jira/browse/EAGLE-696 > Project: Eagle > Issue Type: Improvement >Reporter: Zhao, Qingwen >Assignee: Zhao, Qingwen > > add field display name & refactor the configuration organization -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-eagle pull request #566: EAGLE-683: Improve metadata store perform...
Github user RalphSu commented on a diff in the pull request:
https://github.com/apache/incubator-eagle/pull/566#discussion_r85466419
--- Diff:
eagle-core/eagle-alert-parent/eagle-alert/alert-metadata-parent/alert-metadata/src/main/java/org/apache/eagle/alert/metadata/impl/MongoMetadataDaoImpl.java
---
@@ -89,10 +92,37 @@
@Inject
public MongoMetadataDaoImpl(Config config) {
this.connection = config.getString("connection");
+this.cappedSize = config.hasPath("cappedSize") ?
config.getInt("cappedSize") : 0;
--- End diff --
cappedSize default as 0? why not set it some reasonable value, and i saw
this is set as size in byte. should it be better to control the size in
document number. please check the maxDocuments in CreateCollectionOptions.
---
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-698) Help eagle to collect system and Hadoop JMX information
juhe created EAGLE-698: -- Summary: Help eagle to collect system and Hadoop JMX information Key: EAGLE-698 URL: https://issues.apache.org/jira/browse/EAGLE-698 Project: Eagle Issue Type: New Feature Affects Versions: v0.5.0 Reporter: juhe Assignee: juhe Fix For: v0.5.0 Integrated collect and kafka plugin to gather system information and Hadoop JMX information , and write to kafka cluster. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-eagle pull request #581: EAGLE-696: Update HdfsAuditLogApp Configu...
GitHub user qingwen220 opened a pull request: https://github.com/apache/incubator-eagle/pull/581 EAGLE-696: Update HdfsAuditLogApp Configuration https://issues.apache.org/jira/browse/EAGLE-696 You can merge this pull request into a Git repository by running: $ git pull https://github.com/qingwen220/incubator-eagle EAGLE-696 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-eagle/pull/581.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 #581 commit 961f67287b4c87215cf28f44e8d706c4c8f7fa2f Author: Zhao, Qingwen Date: 2016-10-28T09:53:45Z Update HdfsAuditLogApp Configuration --- 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] incubator-eagle pull request #577: [EAGLE-694] alert engine could not reduce...
GitHub user wujinhu opened a pull request: https://github.com/apache/incubator-eagle/pull/577 [EAGLE-694] alert engine could not reduce alert bolt number when parallelism of p⦠You can merge this pull request into a Git repository by running: $ git pull https://github.com/wujinhu/incubator-eagle EAGLE-694 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-eagle/pull/577.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 #577 commit a229476b99555d6ec0951e3af69e7b0f1e02eac7 Author: wujinhu Date: 2016-10-28T06:07:26Z alert engine could not reduce alert bolt number when parallelism of policy reduces --- 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-694) alert engine could not reduce alert bolt number when parallelism of policy reduces
[ https://issues.apache.org/jira/browse/EAGLE-694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15614430#comment-15614430 ] ASF GitHub Bot commented on EAGLE-694: -- GitHub user wujinhu opened a pull request: https://github.com/apache/incubator-eagle/pull/577 [EAGLE-694] alert engine could not reduce alert bolt number when parallelism of p… You can merge this pull request into a Git repository by running: $ git pull https://github.com/wujinhu/incubator-eagle EAGLE-694 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-eagle/pull/577.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 #577 commit a229476b99555d6ec0951e3af69e7b0f1e02eac7 Author: wujinhu Date: 2016-10-28T06:07:26Z alert engine could not reduce alert bolt number when parallelism of policy reduces > alert engine could not reduce alert bolt number when parallelism of policy > reduces > -- > > Key: EAGLE-694 > URL: https://issues.apache.org/jira/browse/EAGLE-694 > Project: Eagle > Issue Type: Bug >Reporter: wujinhu >Assignee: wujinhu > > alert engine could not reduce alert bolt number when parallelism of policy > reduces -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-eagle pull request #566: EAGLE-683: Improve metadata store perform...
Github user mizeng commented on a diff in the pull request:
https://github.com/apache/incubator-eagle/pull/566#discussion_r85482632
--- Diff:
eagle-core/eagle-alert-parent/eagle-alert/alert-metadata-parent/alert-metadata/src/main/java/org/apache/eagle/alert/metadata/impl/MongoMetadataDaoImpl.java
---
@@ -127,41 +157,41 @@ private void init() {
BsonDocument doc1 = new BsonDocument();
IndexOptions io1 = new
IndexOptions().background(true).name("versionIndex");
doc1.append("version", new BsonInt32(1));
-scheduleStates = db.getCollection("schedule_specs");
+scheduleStates = getCollection("schedule_specs");
scheduleStates.createIndex(doc1, io1);
-spoutSpecs = db.getCollection("spoutSpecs");
+spoutSpecs = getCollection("spoutSpecs");
{
IndexOptions ioInternal = new
IndexOptions().background(true).name("topologyIdIndex");
BsonDocument docInternal = new BsonDocument();
docInternal.append("topologyId", new BsonInt32(1));
spoutSpecs.createIndex(docInternal, ioInternal);
}
-alertSpecs = db.getCollection("alertSpecs");
+alertSpecs = getCollection("alertSpecs");
{
IndexOptions ioInternal = new
IndexOptions().background(true).name("topologyNameIndex");
BsonDocument docInternal = new BsonDocument();
docInternal.append("topologyName", new BsonInt32(1));
alertSpecs.createIndex(docInternal, ioInternal);
}
-groupSpecs = db.getCollection("groupSpecs");
+groupSpecs = getCollection("groupSpecs");
--- End diff --
groupSpecs is part of schedule specs..
---
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-696) Improve HdfsAuditLogApplication & AlertUnitTopologyApp config
[ https://issues.apache.org/jira/browse/EAGLE-696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhao, Qingwen updated EAGLE-696: Description: add field display name & refactor the configuration (was: add field display name & refactor the configuration organization) > Improve HdfsAuditLogApplication & AlertUnitTopologyApp config > -- > > Key: EAGLE-696 > URL: https://issues.apache.org/jira/browse/EAGLE-696 > Project: Eagle > Issue Type: Improvement >Reporter: Zhao, Qingwen >Assignee: Zhao, Qingwen > > add field display name & refactor the configuration -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-eagle pull request #582: EAGLE-699 UI imporvement
GitHub user zombieJ opened a pull request:
https://github.com/apache/incubator-eagle/pull/582
EAGLE-699 UI imporvement
* Init UI hide {{}}
* Description update
* Fix JPM widget bug
* UI tab to window / router update
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/zombieJ/incubator-eagle 699
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-eagle/pull/582.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 #582
commit 6f867e456be9473eea6f75386ce783ed638ef989
Author: zombieJ
Date: 2016-10-28T07:32:40Z
UI init pretty
commit d531f2c01aa703e5e451f5312f7d6814e970eb78
Author: zombieJ
Date: 2016-10-28T10:02:35Z
update time tab
commit 73613b5552a29116d97c5b71f18064ac833be598
Author: zombieJ
Date: 2016-10-28T10:18:46Z
ui update
---
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-699) UI imporvement
[
https://issues.apache.org/jira/browse/EAGLE-699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15615020#comment-15615020
]
ASF GitHub Bot commented on EAGLE-699:
--
GitHub user zombieJ opened a pull request:
https://github.com/apache/incubator-eagle/pull/582
EAGLE-699 UI imporvement
* Init UI hide {{}}
* Description update
* Fix JPM widget bug
* UI tab to window / router update
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/zombieJ/incubator-eagle 699
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-eagle/pull/582.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 #582
commit 6f867e456be9473eea6f75386ce783ed638ef989
Author: zombieJ
Date: 2016-10-28T07:32:40Z
UI init pretty
commit d531f2c01aa703e5e451f5312f7d6814e970eb78
Author: zombieJ
Date: 2016-10-28T10:02:35Z
update time tab
commit 73613b5552a29116d97c5b71f18064ac833be598
Author: zombieJ
Date: 2016-10-28T10:18:46Z
ui update
> UI imporvement
> --
>
> Key: EAGLE-699
> URL: https://issues.apache.org/jira/browse/EAGLE-699
> Project: Eagle
> Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Jilin, Jiang
>Assignee: Jilin, Jiang
> Fix For: v0.5.0
>
>
> * Init UI hide {{}}
> * Description update
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (EAGLE-693) fix application could not detect stream change
[ https://issues.apache.org/jira/browse/EAGLE-693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15614958#comment-15614958 ] ASF GitHub Bot commented on EAGLE-693: -- GitHub user wujinhu reopened a pull request: https://github.com/apache/incubator-eagle/pull/580 [EAGLE-693] fix application could not detect stream change You can merge this pull request into a Git repository by running: $ git pull https://github.com/wujinhu/incubator-eagle EAGLE-700 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-eagle/pull/580.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 #580 commit 4a32d92193ad5f48fb0dd9f59ac2070b55ad9c62 Author: wujinhu Date: 2016-10-28T09:25:16Z fix application could not detect stream change > fix application could not detect stream change > -- > > Key: EAGLE-693 > URL: https://issues.apache.org/jira/browse/EAGLE-693 > Project: Eagle > Issue Type: Bug >Affects Versions: v0.5.0 >Reporter: wujinhu >Assignee: wujinhu > Fix For: v0.5.0 > > > After an application is running, user may want to add streams to it.But when > user updates the application, application framework does not update streams. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-eagle pull request #577: [EAGLE-694] alert engine could not reduce...
Github user RalphSu commented on a diff in the pull request:
https://github.com/apache/incubator-eagle/pull/577#discussion_r85476879
--- Diff:
eagle-core/eagle-alert-parent/eagle-alert/alert-coordinator/src/main/java/org/apache/eagle/alert/coordinator/provider/ScheduleContextBuilder.java
---
@@ -224,7 +224,8 @@ private void
clearMonitoredStreams(List monitoredStreams) {
} else {
StreamWorkSlotQueue queue =
queueMap.get(assignment.getQueueId());
if (queue == null
-||
policies.get(assignment.getPolicyName()).getParallelismHint() >
queue.getQueueSize()) {
+||
policies.get(assignment.getPolicyName()).getParallelismHint() >
queue.getQueueSize()
--- End diff --
use != ?
---
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-696) Improve HdfsAuditLogApplication & AlertUnitTopologyApp config
[ https://issues.apache.org/jira/browse/EAGLE-696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15614967#comment-15614967 ] ASF GitHub Bot commented on EAGLE-696: -- GitHub user qingwen220 opened a pull request: https://github.com/apache/incubator-eagle/pull/581 EAGLE-696: Update HdfsAuditLogApp Configuration https://issues.apache.org/jira/browse/EAGLE-696 You can merge this pull request into a Git repository by running: $ git pull https://github.com/qingwen220/incubator-eagle EAGLE-696 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-eagle/pull/581.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 #581 commit 961f67287b4c87215cf28f44e8d706c4c8f7fa2f Author: Zhao, Qingwen Date: 2016-10-28T09:53:45Z Update HdfsAuditLogApp Configuration > Improve HdfsAuditLogApplication & AlertUnitTopologyApp config > -- > > Key: EAGLE-696 > URL: https://issues.apache.org/jira/browse/EAGLE-696 > Project: Eagle > Issue Type: Improvement >Reporter: Zhao, Qingwen >Assignee: Zhao, Qingwen > > add field display name & refactor the configuration organization -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-eagle issue #576: Eagle-688 UI support Alert display
Github user qingwen220 commented on the issue: https://github.com/apache/incubator-eagle/pull/576 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. ---
[GitHub] incubator-eagle pull request #578: [EAGLE-697] fix wrong url-concatenation f...
Github user asfgit closed the pull request at: https://github.com/apache/incubator-eagle/pull/578 --- 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] [Resolved] (EAGLE-697) wrong metric url composed when endpoint url doesn't end with a slash
[ https://issues.apache.org/jira/browse/EAGLE-697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Wu resolved EAGLE-697. -- Resolution: Fixed > wrong metric url composed when endpoint url doesn't end with a slash > > > Key: EAGLE-697 > URL: https://issues.apache.org/jira/browse/EAGLE-697 > Project: Eagle > Issue Type: Bug >Reporter: Michael Wu >Assignee: Michael Wu > > For hadoop queue monitoring, when endpoint url doesn't end with a slash, the > final url will be composed by concatenating endpoint directly with resource > path. E.g. > endpoint: https://a.b.c: > resource path: ws/v1/cluster/some > Then final url is: https://a.b.c:ws/v1/cluster/some, which make > application fail. > We should add "/" to existing constants of resource paths, and compose final > url with utils. > Besides, add concrete unit test to guarantee this part functions normally. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (EAGLE-695) change to fetching hadoop.cluster.allocatedvirtualcores instead of hadoop.cluster.totalvirtualcores
[ https://issues.apache.org/jira/browse/EAGLE-695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Wu resolved EAGLE-695. -- Resolution: Fixed > change to fetching hadoop.cluster.allocatedvirtualcores instead of > hadoop.cluster.totalvirtualcores > --- > > Key: EAGLE-695 > URL: https://issues.apache.org/jira/browse/EAGLE-695 > Project: Eagle > Issue Type: Task >Reporter: Michael Wu >Assignee: Michael Wu > > Virtual Core related metrics are additional, starting from hadoop version > 2.7.x. And we were originally fetching hadoop.cluster.allocatedvirtualcores. > Now it seems that hadoop.cluster.totalvirtualcores is more meaningful. So > change code to fetch and show it up in hadoop-queue monitoring application. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-700) API /policies/{policyId} throws exception if policy does not exist
wujinhu created EAGLE-700:
-
Summary: API /policies/{policyId} throws exception if policy does
not exist
Key: EAGLE-700
URL: https://issues.apache.org/jira/browse/EAGLE-700
Project: Eagle
Issue Type: Bug
Affects Versions: v0.5.0
Reporter: wujinhu
Assignee: wujinhu
Fix For: v0.5.0
API /policies/{policyId} throws exception if policy does not exist
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (EAGLE-699) UI imporvement
Jilin, Jiang created EAGLE-699:
--
Summary: UI imporvement
Key: EAGLE-699
URL: https://issues.apache.org/jira/browse/EAGLE-699
Project: Eagle
Issue Type: Improvement
Affects Versions: v0.5.0
Reporter: Jilin, Jiang
Assignee: Jilin, Jiang
Fix For: v0.5.0
* Init UI hide {{}}
* Description update
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[GitHub] incubator-eagle pull request #579: [EAGLE-700] API /policies/{policyId} thro...
GitHub user wujinhu opened a pull request:
https://github.com/apache/incubator-eagle/pull/579
[EAGLE-700] API /policies/{policyId} throws exception if policy does not
exist
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/wujinhu/incubator-eagle EAGLE-693
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-eagle/pull/579.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 #579
commit 6f66d6606f3e92d20ffc41e909ceab7d52b0c676
Author: wujinhu
Date: 2016-10-28T07:51:37Z
API /policies/{policyId} throws exception if policy does not exist
---
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-700) API /policies/{policyId} throws exception if policy does not exist
[
https://issues.apache.org/jira/browse/EAGLE-700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15614665#comment-15614665
]
ASF GitHub Bot commented on EAGLE-700:
--
GitHub user wujinhu opened a pull request:
https://github.com/apache/incubator-eagle/pull/579
[EAGLE-700] API /policies/{policyId} throws exception if policy does not
exist
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/wujinhu/incubator-eagle EAGLE-693
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-eagle/pull/579.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 #579
commit 6f66d6606f3e92d20ffc41e909ceab7d52b0c676
Author: wujinhu
Date: 2016-10-28T07:51:37Z
API /policies/{policyId} throws exception if policy does not exist
> API /policies/{policyId} throws exception if policy does not exist
> --
>
> Key: EAGLE-700
> URL: https://issues.apache.org/jira/browse/EAGLE-700
> Project: Eagle
> Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: wujinhu
>Assignee: wujinhu
> Fix For: v0.5.0
>
>
> API /policies/{policyId} throws exception if policy does not exist
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (EAGLE-701) AlertEngine: bolt should check ZK for latest spec when start
Su Ralph created EAGLE-701: -- Summary: AlertEngine: bolt should check ZK for latest spec when start Key: EAGLE-701 URL: https://issues.apache.org/jira/browse/EAGLE-701 Project: Eagle Issue Type: Improvement Affects Versions: v0.5.0 Reporter: Su Ralph Assignee: Zeng, Bryant Fix For: v0.5.0 Currently, bolt use zk listening for metadata reload only. This require zk to be periodically updated. In the case of bolt down, and storm start bolt another place(vm, process), if the zk is not updated, then new bolt possibly can not get the metadata to work well. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (EAGLE-700) API /policies/{policyId} throws exception if policy does not exist
[
https://issues.apache.org/jira/browse/EAGLE-700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
wujinhu closed EAGLE-700.
-
Resolution: Fixed
> API /policies/{policyId} throws exception if policy does not exist
> --
>
> Key: EAGLE-700
> URL: https://issues.apache.org/jira/browse/EAGLE-700
> Project: Eagle
> Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: wujinhu
>Assignee: wujinhu
> Fix For: v0.5.0
>
>
> API /policies/{policyId} throws exception if policy does not exist
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[GitHub] incubator-eagle pull request #566: EAGLE-683: Improve metadata store perform...
Github user asfgit closed the pull request at: https://github.com/apache/incubator-eagle/pull/566 --- 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-683) AlertEngine : Improve metadata store performance
[ https://issues.apache.org/jira/browse/EAGLE-683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15615115#comment-15615115 ] ASF GitHub Bot commented on EAGLE-683: -- Github user asfgit closed the pull request at: https://github.com/apache/incubator-eagle/pull/566 > AlertEngine : Improve metadata store performance > > > Key: EAGLE-683 > URL: https://issues.apache.org/jira/browse/EAGLE-683 > Project: Eagle > Issue Type: Improvement >Affects Versions: v0.5.0 >Reporter: Su Ralph >Assignee: Zeng, Bryant > Fix For: v0.5.0 > > > Currently, we enable periodically schedule in coordinator service itself. If > this is enabled, the schedule spec will finally used up metadata storage. > We should > 1. Disable periodically schedule by default (storage like mysql doesn't have > capped feature) > 2. For mongodb storage, use capped collection for schedule_specs, > policy_snapshots, streamSnapshots, groupSpecs, alertSpecs, monitoredStreams, > spoutSpecs (all schedule spec related collection). > Let use default config of 20,000 as capped collection size. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (EAGLE-699) UI imporvement
[
https://issues.apache.org/jira/browse/EAGLE-699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15615206#comment-15615206
]
ASF GitHub Bot commented on EAGLE-699:
--
Github user qingwen220 commented on the issue:
https://github.com/apache/incubator-eagle/pull/582
LGTM
> UI imporvement
> --
>
> Key: EAGLE-699
> URL: https://issues.apache.org/jira/browse/EAGLE-699
> Project: Eagle
> Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Jilin, Jiang
>Assignee: Jilin, Jiang
> Fix For: v0.5.0
>
>
> * Init UI hide {{}}
> * Description update
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[GitHub] incubator-eagle issue #582: EAGLE-699 UI imporvement
Github user qingwen220 commented on the issue: https://github.com/apache/incubator-eagle/pull/582 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. ---
[GitHub] incubator-eagle pull request #582: EAGLE-699 UI imporvement
Github user asfgit closed the pull request at: https://github.com/apache/incubator-eagle/pull/582 --- 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-697) wrong metric url composed when endpoint url doesn't end with a slash
[ https://issues.apache.org/jira/browse/EAGLE-697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15614513#comment-15614513 ] ASF GitHub Bot commented on EAGLE-697: -- GitHub user anyway1021 opened a pull request: https://github.com/apache/incubator-eagle/pull/578 [EAGLE-697] fix wrong url-concatenation for monitoring hadoop queue For hadoop queue monitoring, when endpoint url doesn't end with a slash, the final url will be composed by concatenating endpoint directly with resource path. E.g. endpoint: https://a.b.c: resource path: ws/v1/cluster/some Then final url is: https://a.b.c:ws/v1/cluster/some, which make application fail. We should add "/" to existing constants of resource paths, and compose final url with utils. Besides, add concrete unit test to guarantee this part functions normally. You can merge this pull request into a Git repository by running: $ git pull https://github.com/anyway1021/incubator-eagle EAGLE-697 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-eagle/pull/578.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 #578 commit 8dd95bd25de917d81592292a2f245670106e6b4c Author: anyway1021 Date: 2016-10-28T04:17:28Z fix wrong url-concatenation for monitoring hadoop queue, also add unit tests > wrong metric url composed when endpoint url doesn't end with a slash > > > Key: EAGLE-697 > URL: https://issues.apache.org/jira/browse/EAGLE-697 > Project: Eagle > Issue Type: Bug >Reporter: Michael Wu >Assignee: Michael Wu > > For hadoop queue monitoring, when endpoint url doesn't end with a slash, the > final url will be composed by concatenating endpoint directly with resource > path. E.g. > endpoint: https://a.b.c: > resource path: ws/v1/cluster/some > Then final url is: https://a.b.c:ws/v1/cluster/some, which make > application fail. > We should add "/" to existing constants of resource paths, and compose final > url with utils. > Besides, add concrete unit test to guarantee this part functions normally. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (EAGLE-699) UI imporvement
[
https://issues.apache.org/jira/browse/EAGLE-699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jilin, Jiang resolved EAGLE-699.
Resolution: Fixed
> UI imporvement
> --
>
> Key: EAGLE-699
> URL: https://issues.apache.org/jira/browse/EAGLE-699
> Project: Eagle
> Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Jilin, Jiang
>Assignee: Jilin, Jiang
> Fix For: v0.5.0
>
>
> * Init UI hide {{}}
> * Description update
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (EAGLE-699) UI imporvement
[
https://issues.apache.org/jira/browse/EAGLE-699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15615220#comment-15615220
]
ASF GitHub Bot commented on EAGLE-699:
--
Github user asfgit closed the pull request at:
https://github.com/apache/incubator-eagle/pull/582
> UI imporvement
> --
>
> Key: EAGLE-699
> URL: https://issues.apache.org/jira/browse/EAGLE-699
> Project: Eagle
> Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Jilin, Jiang
>Assignee: Jilin, Jiang
> Fix For: v0.5.0
>
>
> * Init UI hide {{}}
> * Description update
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
