[
https://issues.apache.org/jira/browse/STORM-404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Noll resolved STORM-404.
Resolution: Fixed
Fix Version/s: 0.9.4
0.10.0
Assignee: Michael
[
https://issues.apache.org/jira/browse/STORM-770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14521072#comment-14521072
]
Michael Pershyn commented on STORM-770:
---
I did extended it, but so far there were no
[
https://issues.apache.org/jira/browse/STORM-404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Noll updated STORM-404:
---
Description:
I have two workers (one on each machine). The first worker(10.30.206.125) had a
problem
[
https://issues.apache.org/jira/browse/STORM-803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14521906#comment-14521906
]
ASF GitHub Bot commented on STORM-803:
--
Github user revans2 commented on the pull
Github user revans2 commented on the pull request:
https://github.com/apache/storm/pull/539#issuecomment-97890019
@HeartSaVioR I agree that some things may be lost when we write the logs
out to a file. That is why I added in the `cat` on failure when compiling, and
the `tail -500`
Github user HeartSaVioR commented on the pull request:
https://github.com/apache/storm/pull/539#issuecomment-97958909
Btw, restricting log level to WARN level is only applied to storm-core now,
since I didn't add logback-test.xml on any other modules. Other modules don't
print out
Github user HeartSaVioR commented on the pull request:
https://github.com/apache/storm/pull/540#issuecomment-97958707
Btw, restricting log level to WARN level is only applied to storm-core now,
since I didn't add logback-test.xml on any other modules. Other modules don't
print out
[
https://issues.apache.org/jira/browse/STORM-603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14522087#comment-14522087
]
ASF GitHub Bot commented on STORM-603:
--
Github user curtisallen commented on the pull
[
https://issues.apache.org/jira/browse/STORM-803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14522212#comment-14522212
]
ASF GitHub Bot commented on STORM-803:
--
Github user HeartSaVioR commented on the pull
Github user HeartSaVioR commented on the pull request:
https://github.com/apache/storm/pull/539#issuecomment-97956783
Yes, right. We need INFO log since Storm debug messages are printed out
INFO.
Maybe your approach requires Maven to fail fast (--ff), which I didn't used
it
Github user curtisallen commented on the pull request:
https://github.com/apache/storm/pull/361#issuecomment-97934446
@revans2 now we throw NPEs if the values are missing. Leveraged guava's
`Preconditions` . Let me know if you need anything else. Thanks!
---
If your project is set
[
https://issues.apache.org/jira/browse/STORM-806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14522211#comment-14522211
]
ASF GitHub Bot commented on STORM-806:
--
Github user HeartSaVioR commented on the pull
12 matches
Mail list logo