[GitHub] metron issue #1035: METRON-1581: kill the profiler topology immediately befo...
Github user ottobackwards commented on the issue: https://github.com/apache/metron/pull/1035 Do we know why it is not shutting down? What if this results in data loss? I think we need a better understanding of what is happening. ---
[jira] [Commented] (METRON-1581) restarting profiler topology fails as the kill topology takes longer time
[
https://issues.apache.org/jira/browse/METRON-1581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16492746#comment-16492746
]
ASF GitHub Bot commented on METRON-1581:
Github user ottobackwards commented on the issue:
https://github.com/apache/metron/pull/1035
Do we know why it is not shutting down? What if this results in data loss?
I think we need a better understanding of what is happening.
> restarting profiler topology fails as the kill topology takes longer time
> -
>
> Key: METRON-1581
> URL: https://issues.apache.org/jira/browse/METRON-1581
> Project: Metron
> Issue Type: Bug
>Reporter: Mohan
>Assignee: Mohan
>Priority: Minor
>
> storm kill 'topology' command will leave the profiler topology in 'KILLED'
> state for longer time some times more than 10 mins .. below is the stdout or
> restart profiler command.
> {code:java}
> 2018-05-28 10:45:38,622 - Stack Feature Version Info: Cluster Stack=2.6,
> Command Stack=None, Command Version=2.6.5.0-292 -> 2.6.5.0-292
> 2018-05-28 10:45:38,640 - Using hadoop conf dir:
> /usr/hdp/2.6.5.0-292/hadoop/conf
> 2018-05-28 10:45:39,324 - Stack Feature Version Info: Cluster Stack=2.6,
> Command Stack=None, Command Version=2.6.5.0-292 -> 2.6.5.0-292
> 2018-05-28 10:45:39,335 - Using hadoop conf dir:
> /usr/hdp/2.6.5.0-292/hadoop/conf
> 2018-05-28 10:45:39,338 - Group['metron'] {}
> 2018-05-28 10:45:39,340 - Group['livy'] {}
> 2018-05-28 10:45:39,341 - Group['spark'] {}
> 2018-05-28 10:45:39,341 - Group['solr'] {}
> 2018-05-28 10:45:39,341 - Group['hdfs'] {}
> 2018-05-28 10:45:39,342 - Group['zeppelin'] {}
> 2018-05-28 10:45:39,342 - Group['hadoop'] {}
> 2018-05-28 10:45:39,342 - Group['users'] {}
> 2018-05-28 10:45:39,344 - User['hive'] {'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': [u'hadoop'], 'uid': None}
> 2018-05-28 10:45:39,346 - User['storm'] {'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': [u'hadoop'], 'uid': None}
> 2018-05-28 10:45:39,348 - User['zookeeper'] {'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': [u'hadoop'], 'uid': None}
> 2018-05-28 10:45:39,349 - User['ams'] {'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': [u'hadoop'], 'uid': None}
> 2018-05-28 10:45:39,351 - User['tez'] {'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': [u'users'], 'uid': None}
> 2018-05-28 10:45:39,353 - User['zeppelin'] {'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': [u'zeppelin', u'hadoop'], 'uid':
> None}
> 2018-05-28 10:45:39,356 - User['metron'] {'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': [u'hadoop'], 'uid': None}
> 2018-05-28 10:45:39,357 - User['livy'] {'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': [u'hadoop'], 'uid': None}
> 2018-05-28 10:45:39,359 - User['spark'] {'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': [u'hadoop'], 'uid': None}
> 2018-05-28 10:45:39,361 - User['ambari-qa'] {'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': [u'users'], 'uid': None}
> 2018-05-28 10:45:39,363 - User['solr'] {'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': [u'hadoop'], 'uid': None}
> 2018-05-28 10:45:39,365 - User['kafka'] {'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': [u'hadoop'], 'uid': None}
> 2018-05-28 10:45:39,367 - User['hdfs'] {'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': ['hdfs'], 'uid': None}
> 2018-05-28 10:45:39,369 - User['yarn'] {'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': [u'hadoop'], 'uid': None}
> 2018-05-28 10:45:39,371 - User['mapred'] {'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': [u'hadoop'], 'uid': None}
> 2018-05-28 10:45:39,373 - User['hbase'] {'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': [u'hadoop'], 'uid': None}
> 2018-05-28 10:45:39,375 - User['hcat'] {'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': [u'hadoop'], 'uid': None}
> 2018-05-28 10:45:39,376 - File['/var/lib/ambari-agent/tmp/changeUid.sh']
> {'content': StaticFile('changeToSecureUid.sh'), 'mode': 0555}
> 2018-05-28 10:45:39,380 - Execute['/var/lib/ambari-agent/tmp/changeUid.sh
> ambari-qa
> /tmp/hadoop-ambari-qa,/tmp/hsperfdata_ambari-qa,/home/ambari-qa,/tmp/ambari-qa,/tmp/sqoop-ambari-qa
> 0'] {'not_if': '(test $(id -u ambari-qa) -gt 1000) || (false)'}
> 2018-05-28 10:45:39,390 - Skipping
> Execute['/var/lib/ambari-agent/tmp/changeUid.sh ambari-qa
> /tmp/hadoop-ambari-qa,/tmp/hsperfdata_ambari-qa,/home/ambari-qa,/tmp/ambari-qa,/tmp/sqoop-ambari-qa
> 0'] due to not_if
> 2018-05-28 10:45:39,391 - Directory['/tmp/hbase-hbase'] {'owner': 'hbase',
> 'create_parents': True, 'mode': 0775, 'cd_access': 'a'}
> 2018-05-28 10:45:39,393 - File['/var/lib/ambari-agent/tmp/changeUid.sh']
> {
[jira] [Commented] (METRON-1581) restarting profiler topology fails as the kill topology takes longer time
[
https://issues.apache.org/jira/browse/METRON-1581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16492692#comment-16492692
]
ASF GitHub Bot commented on METRON-1581:
GitHub user MohanDV opened a pull request:
https://github.com/apache/metron/pull/1035
METRON-1581: kill the profiler topology immediately before restarting the
topology if it is in 'KILLED' state for longer time
## Contributor Comments
Restarting profiler topology fails storm kill 'topology' command will leave
the profiler topology in 'KILLED' state for longer time.
### Steps to reproduce:
1. Restart the profiler topology
2. The start topology fails with 'Topology with name `profiler` already
exists on cluster'
3. execute 'storm list' on any node with supervisor which will return the
profiler topology status as KILLED
## Pull Request Checklist
Thank you for submitting a contribution to Apache Metron.
Please refer to our [Development
Guidelines](https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=61332235)
for the complete guide to follow for contributions.
Please refer also to our [Build Verification
Guidelines](https://cwiki.apache.org/confluence/display/METRON/Verifying+Builds?show-miniview)
for complete smoke testing guides.
In order to streamline the review of the contribution we ask you follow
these guidelines and ask you to double check the following:
### For all changes:
- [x] Is there a JIRA ticket associated with this PR? If not one needs to
be created at [Metron
Jira](https://issues.apache.org/jira/browse/METRON/?selectedTab=com.atlassian.jira.jira-projects-plugin:summary-panel).
- [x] Does your PR title start with METRON- where is the JIRA
number you are trying to resolve? Pay particular attention to the hyphen "-"
character.
- [x] Has your PR been rebased against the latest commit within the target
branch (typically master)?
### For code changes:
- [x] Have you included steps to reproduce the behavior or problem that is
being changed or addressed?
- [x] Have you included steps or a guide to how the change may be verified
and tested manually?
- [ ] Have you ensured that the full suite of tests and checks have been
executed in the root metron folder via:
```
mvn -q clean integration-test install &&
dev-utilities/build-utils/verify_licenses.sh
```
- [ ] Have you written or updated unit tests and or integration tests to
verify your changes?
- [ ] If adding new dependencies to the code, are these dependencies
licensed in a way that is compatible for inclusion under [ASF
2.0](http://www.apache.org/legal/resolved.html#category-a)?
- [ ] Have you verified the basic functionality of the build by building
and running locally with Vagrant full-dev environment or the equivalent?
### For documentation related changes:
- [ ] Have you ensured that format looks appropriate for the output in
which it is rendered by building and verifying the site-book? If not then run
the following commands and the verify changes via
`site-book/target/site/index.html`:
```
cd site-book
mvn site
```
Note:
Please ensure that once the PR is submitted, you check travis-ci for build
issues and submit an update to your PR as soon as possible.
It is also recommended that [travis-ci](https://travis-ci.org) is set up
for your personal repository such that your branches are built there before
submitting a pull request.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/MohanDV/metron METRON-1581
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/metron/pull/1035.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 #1035
commit a9d731e77037a2248b2802906f1ed5ea992f261a
Author: Mohan Venkateshaiah
Date: 2018-05-28T13:33:49Z
jira:METRON-1581 kill the profiler topology immediately if it is in
'KILLED' state for long time.
> restarting profiler topology fails as the kill topology takes longer time
> -
>
> Key: METRON-1581
> URL: https://issues.apache.org/jira/browse/METRON-1581
> Project: Metron
> Issue Type: Bug
>Reporter: Mohan
>Assignee: Mohan
>Priority: Minor
>
> storm kill 'topology' command will leave the profiler topology in 'KILLED'
> state for longer time some times more than 10 mins .. below is the stdout or
> restart profiler command.
> {code:java}
> 2018-05-28 10:45:38,622 - Stack Feature Version Info: Cluster Stack=2.6
[GitHub] metron pull request #1035: METRON-1581: kill the profiler topology immediate...
GitHub user MohanDV opened a pull request: https://github.com/apache/metron/pull/1035 METRON-1581: kill the profiler topology immediately before restarting the topology if it is in 'KILLED' state for longer time ## Contributor Comments Restarting profiler topology fails storm kill 'topology' command will leave the profiler topology in 'KILLED' state for longer time. ### Steps to reproduce: 1. Restart the profiler topology 2. The start topology fails with 'Topology with name `profiler` already exists on cluster' 3. execute 'storm list' on any node with supervisor which will return the profiler topology status as KILLED ## Pull Request Checklist Thank you for submitting a contribution to Apache Metron. Please refer to our [Development Guidelines](https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=61332235) for the complete guide to follow for contributions. Please refer also to our [Build Verification Guidelines](https://cwiki.apache.org/confluence/display/METRON/Verifying+Builds?show-miniview) for complete smoke testing guides. In order to streamline the review of the contribution we ask you follow these guidelines and ask you to double check the following: ### For all changes: - [x] Is there a JIRA ticket associated with this PR? If not one needs to be created at [Metron Jira](https://issues.apache.org/jira/browse/METRON/?selectedTab=com.atlassian.jira.jira-projects-plugin:summary-panel). - [x] Does your PR title start with METRON- where is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character. - [x] Has your PR been rebased against the latest commit within the target branch (typically master)? ### For code changes: - [x] Have you included steps to reproduce the behavior or problem that is being changed or addressed? - [x] Have you included steps or a guide to how the change may be verified and tested manually? - [ ] Have you ensured that the full suite of tests and checks have been executed in the root metron folder via: ``` mvn -q clean integration-test install && dev-utilities/build-utils/verify_licenses.sh ``` - [ ] Have you written or updated unit tests and or integration tests to verify your changes? - [ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under [ASF 2.0](http://www.apache.org/legal/resolved.html#category-a)? - [ ] Have you verified the basic functionality of the build by building and running locally with Vagrant full-dev environment or the equivalent? ### For documentation related changes: - [ ] Have you ensured that format looks appropriate for the output in which it is rendered by building and verifying the site-book? If not then run the following commands and the verify changes via `site-book/target/site/index.html`: ``` cd site-book mvn site ``` Note: Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible. It is also recommended that [travis-ci](https://travis-ci.org) is set up for your personal repository such that your branches are built there before submitting a pull request. You can merge this pull request into a Git repository by running: $ git pull https://github.com/MohanDV/metron METRON-1581 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/metron/pull/1035.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 #1035 commit a9d731e77037a2248b2802906f1ed5ea992f261a Author: Mohan Venkateshaiah Date: 2018-05-28T13:33:49Z jira:METRON-1581 kill the profiler topology immediately if it is in 'KILLED' state for long time. ---
[jira] [Created] (METRON-1581) restarting profiler topology fails as the kill topology takes longer time
Mohan created METRON-1581:
-
Summary: restarting profiler topology fails as the kill topology
takes longer time
Key: METRON-1581
URL: https://issues.apache.org/jira/browse/METRON-1581
Project: Metron
Issue Type: Bug
Reporter: Mohan
Assignee: Mohan
storm kill 'topology' command will leave the profiler topology in 'KILLED'
state for longer time some times more than 10 mins .. below is the stdout or
restart profiler command.
{code:java}
2018-05-28 10:45:38,622 - Stack Feature Version Info: Cluster Stack=2.6,
Command Stack=None, Command Version=2.6.5.0-292 -> 2.6.5.0-292
2018-05-28 10:45:38,640 - Using hadoop conf dir:
/usr/hdp/2.6.5.0-292/hadoop/conf
2018-05-28 10:45:39,324 - Stack Feature Version Info: Cluster Stack=2.6,
Command Stack=None, Command Version=2.6.5.0-292 -> 2.6.5.0-292
2018-05-28 10:45:39,335 - Using hadoop conf dir:
/usr/hdp/2.6.5.0-292/hadoop/conf
2018-05-28 10:45:39,338 - Group['metron'] {}
2018-05-28 10:45:39,340 - Group['livy'] {}
2018-05-28 10:45:39,341 - Group['spark'] {}
2018-05-28 10:45:39,341 - Group['solr'] {}
2018-05-28 10:45:39,341 - Group['hdfs'] {}
2018-05-28 10:45:39,342 - Group['zeppelin'] {}
2018-05-28 10:45:39,342 - Group['hadoop'] {}
2018-05-28 10:45:39,342 - Group['users'] {}
2018-05-28 10:45:39,344 - User['hive'] {'gid': 'hadoop',
'fetch_nonlocal_groups': True, 'groups': [u'hadoop'], 'uid': None}
2018-05-28 10:45:39,346 - User['storm'] {'gid': 'hadoop',
'fetch_nonlocal_groups': True, 'groups': [u'hadoop'], 'uid': None}
2018-05-28 10:45:39,348 - User['zookeeper'] {'gid': 'hadoop',
'fetch_nonlocal_groups': True, 'groups': [u'hadoop'], 'uid': None}
2018-05-28 10:45:39,349 - User['ams'] {'gid': 'hadoop',
'fetch_nonlocal_groups': True, 'groups': [u'hadoop'], 'uid': None}
2018-05-28 10:45:39,351 - User['tez'] {'gid': 'hadoop',
'fetch_nonlocal_groups': True, 'groups': [u'users'], 'uid': None}
2018-05-28 10:45:39,353 - User['zeppelin'] {'gid': 'hadoop',
'fetch_nonlocal_groups': True, 'groups': [u'zeppelin', u'hadoop'], 'uid': None}
2018-05-28 10:45:39,356 - User['metron'] {'gid': 'hadoop',
'fetch_nonlocal_groups': True, 'groups': [u'hadoop'], 'uid': None}
2018-05-28 10:45:39,357 - User['livy'] {'gid': 'hadoop',
'fetch_nonlocal_groups': True, 'groups': [u'hadoop'], 'uid': None}
2018-05-28 10:45:39,359 - User['spark'] {'gid': 'hadoop',
'fetch_nonlocal_groups': True, 'groups': [u'hadoop'], 'uid': None}
2018-05-28 10:45:39,361 - User['ambari-qa'] {'gid': 'hadoop',
'fetch_nonlocal_groups': True, 'groups': [u'users'], 'uid': None}
2018-05-28 10:45:39,363 - User['solr'] {'gid': 'hadoop',
'fetch_nonlocal_groups': True, 'groups': [u'hadoop'], 'uid': None}
2018-05-28 10:45:39,365 - User['kafka'] {'gid': 'hadoop',
'fetch_nonlocal_groups': True, 'groups': [u'hadoop'], 'uid': None}
2018-05-28 10:45:39,367 - User['hdfs'] {'gid': 'hadoop',
'fetch_nonlocal_groups': True, 'groups': ['hdfs'], 'uid': None}
2018-05-28 10:45:39,369 - User['yarn'] {'gid': 'hadoop',
'fetch_nonlocal_groups': True, 'groups': [u'hadoop'], 'uid': None}
2018-05-28 10:45:39,371 - User['mapred'] {'gid': 'hadoop',
'fetch_nonlocal_groups': True, 'groups': [u'hadoop'], 'uid': None}
2018-05-28 10:45:39,373 - User['hbase'] {'gid': 'hadoop',
'fetch_nonlocal_groups': True, 'groups': [u'hadoop'], 'uid': None}
2018-05-28 10:45:39,375 - User['hcat'] {'gid': 'hadoop',
'fetch_nonlocal_groups': True, 'groups': [u'hadoop'], 'uid': None}
2018-05-28 10:45:39,376 - File['/var/lib/ambari-agent/tmp/changeUid.sh']
{'content': StaticFile('changeToSecureUid.sh'), 'mode': 0555}
2018-05-28 10:45:39,380 - Execute['/var/lib/ambari-agent/tmp/changeUid.sh
ambari-qa
/tmp/hadoop-ambari-qa,/tmp/hsperfdata_ambari-qa,/home/ambari-qa,/tmp/ambari-qa,/tmp/sqoop-ambari-qa
0'] {'not_if': '(test $(id -u ambari-qa) -gt 1000) || (false)'}
2018-05-28 10:45:39,390 - Skipping
Execute['/var/lib/ambari-agent/tmp/changeUid.sh ambari-qa
/tmp/hadoop-ambari-qa,/tmp/hsperfdata_ambari-qa,/home/ambari-qa,/tmp/ambari-qa,/tmp/sqoop-ambari-qa
0'] due to not_if
2018-05-28 10:45:39,391 - Directory['/tmp/hbase-hbase'] {'owner': 'hbase',
'create_parents': True, 'mode': 0775, 'cd_access': 'a'}
2018-05-28 10:45:39,393 - File['/var/lib/ambari-agent/tmp/changeUid.sh']
{'content': StaticFile('changeToSecureUid.sh'), 'mode': 0555}
2018-05-28 10:45:39,396 - File['/var/lib/ambari-agent/tmp/changeUid.sh']
{'content': StaticFile('changeToSecureUid.sh'), 'mode': 0555}
2018-05-28 10:45:39,398 - call['/var/lib/ambari-agent/tmp/changeUid.sh hbase']
{}
2018-05-28 10:45:39,408 - call returned (0, '1814')
2018-05-28 10:45:39,409 - Execute['/var/lib/ambari-agent/tmp/changeUid.sh hbase
/home/hbase,/tmp/hbase,/usr/bin/hbase,/var/log/hbase,/tmp/hbase-hbase 1814']
{'not_if': '(test $(id -u hbase) -gt 1000) || (false)'}
2018-05-28 10:45:39,416 - Skipping
Execute['/var/lib/ambari-agent/tmp/changeUid.sh hbase
/home/hbase,/tmp/hbase,/usr/bin/hbase,/
