You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@storm.apache.org by HeartSaVioR <gi...@git.apache.org> on 2017/08/30 14:04:51 UTC
[GitHub] storm pull request #2299: STORM-2443 Fix issues on changing log level
GitHub user HeartSaVioR opened a pull request:
https://github.com/apache/storm/pull/2299
STORM-2443 Fix issues on changing log level
* Addressed below issues
* Nimbus throws error when changing log level on UI topology page
* Log configs in worker are removed even they're not timed out and never reset
* The unit of epoch between backend and frontend are different
* second in backend, millisecond in frontend
* millisecond is right so fixed it
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/HeartSaVioR/storm STORM-2443
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/storm/pull/2299.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 #2299
----
commit 01fbb1a76e49d449835f8282e096e0d5828b34b9
Author: Jungtaek Lim <ka...@gmail.com>
Date: 2017-08-30T13:59:13Z
STORM-2443 Fix issues on changing log level
* Addressed below issues
* Nimbus throws error when changing log level on UI topology page
* Log configs in worker are removed even they're not timed out and never reset
* The unit of epoch between backend and frontend are different
* second in backend, millisecond in frontend
* millisecond is right so fixed it
----
---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] storm issue #2299: STORM-2443 Fix issues on changing log level
Posted by HeartSaVioR <gi...@git.apache.org>.
Github user HeartSaVioR commented on the issue:
https://github.com/apache/storm/pull/2299
@satishd Sure. I missed that. Will address.
---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] storm pull request #2299: STORM-2443 Fix issues on changing log level
Posted by asfgit <gi...@git.apache.org>.
Github user asfgit closed the pull request at:
https://github.com/apache/storm/pull/2299
---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] storm issue #2299: STORM-2443 Fix issues on changing log level
Posted by HeartSaVioR <gi...@git.apache.org>.
Github user HeartSaVioR commented on the issue:
https://github.com/apache/storm/pull/2299
@satishd Addressed and squashed commits.
---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] storm issue #2299: STORM-2443 Fix issues on changing log level
Posted by satishd <gi...@git.apache.org>.
Github user satishd commented on the issue:
https://github.com/apache/storm/pull/2299
It seems `org.apache.storm.st.tests.window.SlidingWindowTest` is getting failed but that looks to be an intermittent failure and it is not related to 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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---