[GitHub] storm pull request: [STORM-1590] port defmeters/defgauge/defhistog...
Github user unsleepy22 commented on the pull request: https://github.com/apache/storm/pull/1171#issuecomment-192615168 @revans2 could you take a look? --- 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 infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (STORM-1590) port defmeters/defgauge/defhistogram... to java for all of our code to use
[ https://issues.apache.org/jira/browse/STORM-1590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15181659#comment-15181659 ] ASF GitHub Bot commented on STORM-1590: --- Github user unsleepy22 commented on the pull request: https://github.com/apache/storm/pull/1171#issuecomment-192615168 @revans2 could you take a look? > port defmeters/defgauge/defhistogram... to java for all of our code to use > -- > > Key: STORM-1590 > URL: https://issues.apache.org/jira/browse/STORM-1590 > Project: Apache Storm > Issue Type: Improvement >Reporter: John Fang >Assignee: Cody > > although metrics belong to metric-clojure， I often use it in code. I > suggest we can port some defined metric methods to java. So the next person > does not have to do it later. for example defmeter/defgauge... -- This message was sent by Atlassian JIRA (v6.3.4#6332)
storm ui result
I've a project using storm and made change in code , tried to get which is better in performance , i submitted old code in storm and took screenshot of numbers appeared in storm ui and now i tested my code "new code" in storm with single machine and in real cluster with another machine is result with using single machine is same with using 2 machine ? i need someone to help me in this numbers Why these numbers changed ? and how can i decide which is better "old code" or "new code " ? Thanks in advance ,
[GitHub] storm pull request: [STORM-1250]: port backtype.storm.serializatio...
Github user wuchong commented on the pull request: https://github.com/apache/storm/pull/1150#issuecomment-192798074 @revans2addressed --- 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 infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (STORM-1250) port backtype.storm.serialization-test to java
[ https://issues.apache.org/jira/browse/STORM-1250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15181980#comment-15181980 ] ASF GitHub Bot commented on STORM-1250: --- Github user wuchong commented on the pull request: https://github.com/apache/storm/pull/1150#issuecomment-192798074 @revans2addressed > port backtype.storm.serialization-test to java > --- > > Key: STORM-1250 > URL: https://issues.apache.org/jira/browse/STORM-1250 > Project: Apache Storm > Issue Type: New Feature > Components: storm-core >Reporter: Robert Joseph Evans >Assignee: Jark Wu > Labels: java-migration, jstorm-merger > > junit test migration -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (STORM-1605) storm shell script should use /bin/env python to check python version
Cody created STORM-1605: --- Summary: storm shell script should use /bin/env python to check python version Key: STORM-1605 URL: https://issues.apache.org/jira/browse/STORM-1605 Project: Apache Storm Issue Type: Bug Components: storm-core Affects Versions: 0.10.1, 2.0.0 Environment: RHEL 5.7 Reporter: Cody Fix For: 0.10.1, 2.0.0 Currently storm script uses /usr/bin/python2.6 and /usr/bin/python to check python version, however, RHEL5 ships with python2.4 by default, so when users upgrade python to 2.7.5 without changing /usr/bin/python to 2.7.5 python binary, storm will fail to start since it thinks it's using python2.4. It would be better to use /bin/env python to detect python version instead. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (STORM-1605) storm shell script should use /bin/env python to check python version
[ https://issues.apache.org/jira/browse/STORM-1605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15182040#comment-15182040 ] Cody commented on STORM-1605: - storm will fail too even there's /usr/bin/python2.7. > storm shell script should use /bin/env python to check python version > - > > Key: STORM-1605 > URL: https://issues.apache.org/jira/browse/STORM-1605 > Project: Apache Storm > Issue Type: Bug > Components: storm-core >Affects Versions: 0.10.1, 2.0.0 > Environment: RHEL 5.7 >Reporter: Cody > Fix For: 0.10.1, 2.0.0 > > Original Estimate: 120h > Remaining Estimate: 120h > > Currently storm script uses /usr/bin/python2.6 and /usr/bin/python to check > python version, however, RHEL5 ships with python2.4 by default, so when users > upgrade python to 2.7.5 without changing /usr/bin/python to 2.7.5 python > binary, storm will fail to start since it thinks it's using python2.4. > It would be better to use /bin/env python to detect python version instead. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
