Github user HeartSaVioR commented on the issue:
https://github.com/apache/storm/pull/2204
@Ethanlm
No problem. Thanks for testing my patch thoughtfully. Please let me know if
(2) becomes fixed with setting `logs.users` in the topology configuration.
---
If your project is set
Github user Ethanlm commented on the issue:
https://github.com/apache/storm/pull/2204
@HeartSaVioR Thanks! It's good to learn
---
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
Github user HeartSaVioR commented on the issue:
https://github.com/apache/storm/pull/2204
@Ethanlm
For now you should include `ethan` to `logs.users` in `topology
configuration`. Global configuration doesn't take effect. This behavior seems
same as current logviewer.
If we
Github user Ethanlm commented on the issue:
https://github.com/apache/storm/pull/2204
Yea~ It works now.
Use nimbus admin account:
Use "ethan" account (it's not
Github user HeartSaVioR commented on the issue:
https://github.com/apache/storm/pull/2204
@Ethanlm
I realized I missed addressing other places for parameter swapped. Just
addressed and tested as well.
You can just build `storm-webapp` module and copy `storm-webapp jar` into
Github user HeartSaVioR commented on the issue:
https://github.com/apache/storm/pull/2204
@Ethanlm
Yeah I think I addressed (2) and forgot to debug (3). I'll test it quickly.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user Ethanlm commented on the issue:
https://github.com/apache/storm/pull/2204
Just tested (3). Don't know why (3) is still not working (even with nimbus
admin account).
GitHub user Ethanlm opened a pull request:
https://github.com/apache/storm/pull/2237
PacemakerClient code improvement
1. add shutdown checking before connecting
2. add try-catch block for robustness.
You can merge this pull request into a Git repository by running:
$ git
Github user Ethanlm commented on the issue:
https://github.com/apache/storm/pull/2204
@HeartSaVioR I will test it quickly
---
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
Hi Roshan,
I guess rebasing could be necessary even while in review phase, so
personally I'd rather see the PR first even it has merge conflict between
origin master branch, and have review process with changes in PR, and
address once review process is done.
If you want to hold off commits just
Github user HeartSaVioR commented on the issue:
https://github.com/apache/storm/pull/2204
@revans2
I fixed the drop down issue, and also fixed issue regarding authorization
check. I think it was the reason of issues what @Ethanlm observed.
@Ethanlm
Could you test it
thanks for replying . it's the first time i see this error but i searched
for the file in /storm/bin and didn't find anything also searched in other
files like logs and couldn't find the file . the error i copied it from the
UI because i didn't any errors in logs .
On Mon, Jul 24, 2017 at 3:24
In storm, OOM exception is typically caused by incorrectly accumulating
references to the objects that should have been freed. This bug can be
pinpointed and solved by analyzing the memory dump file. In particular, when
OOM happens on a particular worker, a dump file will generated (in the same
I got this error after submitted the topology
java.lang.OutOfMemoryError: Java heap space at
cern.colt.matrix.impl.DenseDoubleMatrix1D.(Unknown Source) at
trident.state.BucketsDB.updateRandomVectors(BucketsDB.java:126) at
trident.state.q
this error appeared after 8 hours from getting results
How
Storm Devs,
My PR for STORM-2306 (messaging subsystem redesign) is almost ready. Not
surprisingly, this PR brings extensive modifications in storm-client module and
touches lightly on some others.
Just finished manually rebasing my local changes (to ~90 files) from an old
version of master
Github user srdo commented on the issue:
https://github.com/apache/storm/pull/2236
Thanks
---
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
Github user asfgit closed the pull request at:
https://github.com/apache/storm/pull/2236
---
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
GitHub user omerhadari opened a pull request:
https://github.com/apache/storm/pull/2236
STORM-2652: fix error in open method of JmsSpout
I changed the casting to `Number` instead of `Integer`
since it is actually a `Long`, and it caused a `ClassCastException`
to be thrown.
Github user liu-zhaokun commented on the issue:
https://github.com/apache/storm/pull/2207
@revans2
Could you help me review this PRï¼there are no committer to review it all
the time.
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user srdo commented on the issue:
https://github.com/apache/storm/pull/2234
Thanks @vesense
---
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
20 matches
Mail list logo
