[jira] [Commented] (STORM-525) UI Component Page Executor Uptimes are not sorted correctly

[ https://issues.apache.org/jira/browse/STORM-525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14249537#comment-14249537 ] ASF GitHub Bot commented on STORM-525: -- Github user asfgit closed the pull request at:

[GitHub] storm pull request: STORM-525: Add time sorting function to the 2n...

Github user asfgit closed the pull request at: https://github.com/apache/storm/pull/289 --- 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 enabl

[GitHub] storm pull request: Update cluster.xml

Github user asfgit closed the pull request at: https://github.com/apache/storm/pull/337 --- 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 enabl

[jira] [Commented] (STORM-410) (Security) add groups support to logviewer

[ https://issues.apache.org/jira/browse/STORM-410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14249522#comment-14249522 ] ASF GitHub Bot commented on STORM-410: -- Github user harshach commented on the pull req

[GitHub] storm pull request: [STORM-410] Add groups support to log-viewer

Github user harshach commented on the pull request: https://github.com/apache/storm/pull/317#issuecomment-67280464 +1 looks good to me tested it in secure env. Side note we should add this config security.md. Thanks. --- If your project is set up for it, you can reply to this email a

[jira] [Commented] (STORM-391) KafkaSpout to await for the topic

[ https://issues.apache.org/jira/browse/STORM-391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14249521#comment-14249521 ] ASF GitHub Bot commented on STORM-391: -- Github user harshach commented on the pull req

[GitHub] storm pull request: [STORM-391] KafkaSpout to await for the topic

Github user harshach commented on the pull request: https://github.com/apache/storm/pull/338#issuecomment-67280407 @Lewuathe can you give details whats the agreed upon implementation here. We could use curator to use kafka zk /topics to check if the given topic exists or not. The

[jira] [Created] (STORM-596) "topology.receiver.buffer.size" has no effect

caofangkun created STORM-596: Summary: "topology.receiver.buffer.size" has no effect Key: STORM-596 URL: https://issues.apache.org/jira/browse/STORM-596 Project: Apache Storm Issue Type: Bug

[jira] [Updated] (STORM-183) Supervisor/worker shutdown hook should be called in distributed mode.

[ https://issues.apache.org/jira/browse/STORM-183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sriharsha Chintalapani updated STORM-183: - Assignee: Parth Brahmbhatt > Supervisor/worker shutdown hook should be called in di

[jira] [Updated] (STORM-307) After host crash, supervisor is unable to restart itself

[ https://issues.apache.org/jira/browse/STORM-307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sriharsha Chintalapani updated STORM-307: - Assignee: Thomas Becker > After host crash, supervisor is unable to restart itself

Re: Fwd: Auto-Scaling

Hi, Can someone pls answer my questions from the above thread. *I have 2 questions for you;* *1. In one of your earlier emails, you mentioned that there is a limited Metrics implementation which is available in the current Storm version. * *Will this provide 'acks threshold', i.e, the number

[jira] [Commented] (STORM-248) cluster.xml location is hardcoded for workers.

[ https://issues.apache.org/jira/browse/STORM-248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14248567#comment-14248567 ] Sriharsha Chintalapani commented on STORM-248: -- [~fmazoyer] In your proposal I

[jira] [Commented] (STORM-248) cluster.xml location is hardcoded for workers.

[ https://issues.apache.org/jira/browse/STORM-248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14248553#comment-14248553 ] Sriharsha Chintalapani commented on STORM-248: -- [~fmazoyer] STORM-487 has a pa

[jira] [Commented] (STORM-542) Topology summary executors/workers count labels are mixed up

[ https://issues.apache.org/jira/browse/STORM-542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14248507#comment-14248507 ] Stas Levin commented on STORM-542: -- Btw, when I looked into it, it didn't seem like simply

[jira] [Commented] (STORM-582) Nimbus Halt with FileNotFoundException: '../nimbus/../stormconf.ser' dose not exists

[ https://issues.apache.org/jira/browse/STORM-582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14248377#comment-14248377 ] scooler commented on STORM-582: --- it's also happen in storm-0.9.3

[jira] [Commented] (STORM-542) Topology summary executors/workers count labels are mixed up

[ https://issues.apache.org/jira/browse/STORM-542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14248345#comment-14248345 ] Michael Noll commented on STORM-542: Yes, this is still an issue in Storm 0.9.2-incubat

[jira] [Commented] (STORM-595) storm-hdfs can only work with sequence files that use Writables

[ https://issues.apache.org/jira/browse/STORM-595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14248132#comment-14248132 ] ASF GitHub Bot commented on STORM-595: -- Github user mikert commented on the pull reque

[GitHub] storm pull request: STORM-595 Added support for serialization to S...

Github user mikert commented on the pull request: https://github.com/apache/storm/pull/347#issuecomment-67142387 Created a Jira ticket and updated the pull request. --- 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

[jira] [Commented] (STORM-248) cluster.xml location is hardcoded for workers.

[ https://issues.apache.org/jira/browse/STORM-248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14248130#comment-14248130 ] Frantz Mazoyer commented on STORM-248: -- This may be a dumb question, but I'll ask it a