[
https://issues.apache.org/jira/browse/EAGLE-432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15528587#comment-15528587
]
ASF GitHub Bot commented on EAGLE-432:
--------------------------------------
GitHub user DadanielZ opened a pull request:
https://github.com/apache/incubator-eagle/pull/461
[EAGLE-432] Application status monitoring
<!--
{% comment %}
Licensed to the Apache Software Foundation (ASF) under one or more
contributor license agreements. See the NOTICE file distributed with
this work for additional information regarding copyright ownership.
The ASF licenses this file to you under the Apache License, Version 2.0
(the "License"); you may not use this file except in compliance with
the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
{% endcomment %}
-->
Be sure to do all of the following to help us incorporate your contribution
quickly and easily:
- [ ] Make sure the PR title is formatted like:
`[EAGLE-<Jira issue #>] Description of pull request`
- [ ] Make sure tests pass via `mvn clean verify`. (Even better, enable
Travis-CI on your fork and ensure the whole test matrix passes).
- [ ] Replace `<Jira issue #>` in the title with the actual Jira issue
number, if there is one.
- [ ] If this contribution is large, please file an Apache
[Individual Contributor License
Agreement](https://www.apache.org/licenses/icla.txt).
---
- REST API call of app status can return:
"INITIALIZED"
"STARTING"
"RUNNING"
"STOPPING"
- Added CheckStatus Operation as a new application Operation
- ApplicationStatusUpdateService will probe topology status periodically
and update the status in application Entity, this background task is based on
"guava". The initial delay and period setting can be set in configuration file.
- status() in StormExecutionRuntime supports both "LOCAL" and "CLUSTER"
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/DadanielZ/incubator-eagle
EAGLE-432-Application-status-monitoring
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-eagle/pull/461.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 #461
----
commit ab0c583b9fee6b3d7d9ad5200dcb0f360f79e060
Author: DadanielZ <[email protected]>
Date: 2016-09-28T06:24:03Z
[EAGLE-432] Application status monitoring
- REST API call of app status can return:
"INITIALIZED"
"STARTING"
"RUNNING"
"STOPPING"
- Added CheckStatus Operation as a new application Operation
- ApplicationStatusUpdateService will probe topology status periodically
and update the status in application Entity, this background task is based on
"guava". The initial delay and period setting can be set in configuration file.
- status() in StormExecutionRuntime supports both "LOCAL" and "CLUSTER"
----
> Application status monitoring
> -----------------------------
>
> Key: EAGLE-432
> URL: https://issues.apache.org/jira/browse/EAGLE-432
> Project: Eagle
> Issue Type: Improvement
> Affects Versions: v0.5.0
> Reporter: Edward Zhang
> Assignee: DanielZhou
> Fix For: v0.5.0
>
>
> App framework needs to probe application status periodically or on demand.
> ApplicationEntity contains status field, and this field's value should come
> from physical storm applications.
> We can start background threads to check application status or on-demand.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
