[jira] [Commented] (STORM-591) logback.xml

2014-12-19 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/STORM-591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14254503#comment-14254503 ] ASF GitHub Bot commented on STORM-591: -- Github user Lewuathe commented on the pull req

[GitHub] storm pull request: [STORM-591] exclude logback.xml from jar

2014-12-19 Thread Lewuathe
Github user Lewuathe commented on the pull request: https://github.com/apache/storm/pull/352#issuecomment-67724394 @harshach OK. I'll remove `logback.xml`. Thank you for your advice. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHu

[jira] [Commented] (STORM-487) Remove storm.cmd, no need to duplicate work python runs on windows too.

2014-12-19 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/STORM-487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14254247#comment-14254247 ] ASF GitHub Bot commented on STORM-487: -- Github user harshach commented on the pull req

[GitHub] storm pull request: STORM-487 Let bin/storm compatible with Window...

2014-12-19 Thread harshach
Github user harshach commented on the pull request: https://github.com/apache/storm/pull/280#issuecomment-67712765 @HeartSaVioR sorry about taking so long to review this. Its been a challenge to get a windows box :). I tested this both on windows 8 and centos6.5 I tested all the co

[GitHub] storm pull request: Storm 166: Nimbus HA design doc and implementa...

2014-12-19 Thread Parth-Brahmbhatt
GitHub user Parth-Brahmbhatt opened a pull request: https://github.com/apache/storm/pull/354 Storm 166: Nimbus HA design doc and implementation. I have deleted the bit torrent implementation from this pull request as the only available bit torrent library does not support tracker le

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

2014-12-19 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/STORM-248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14253722#comment-14253722 ] ASF GitHub Bot commented on STORM-248: -- GitHub user fmazoyer opened a pull request:

[GitHub] storm pull request: STORM-248 STORM-322 proposal for fix

2014-12-19 Thread fmazoyer
GitHub user fmazoyer opened a pull request: https://github.com/apache/storm/pull/353 STORM-248 STORM-322 proposal for fix Details are in JIRA https://issues.apache.org/jira/browse/STORM-248. As a collateral benefit, this also addresses JIRA https://issues.apache.org/jira/browse/

[jira] [Commented] (STORM-586) Trident kafka spout fails instead of updating offset when kafka offset is out of range.

2014-12-19 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/STORM-586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14253707#comment-14253707 ] ASF GitHub Bot commented on STORM-586: -- Github user harshach commented on the pull req

[GitHub] storm pull request: STORM-586: TridentKafkaEmitter should catch up...

2014-12-19 Thread harshach
Github user harshach commented on the pull request: https://github.com/apache/storm/pull/339#issuecomment-67672726 @nathanmarz Yes previously it used keep retrying but this is causing too many logs being generated by kafka due to the failed requests. This is fixed in https://issues.a

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

2014-12-19 Thread Sriharsha Chintalapani (JIRA)
[ https://issues.apache.org/jira/browse/STORM-248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14253611#comment-14253611 ] Sriharsha Chintalapani commented on STORM-248: -- [~fmazoyer] Thanks for the pat

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

2014-12-19 Thread Frantz Mazoyer (JIRA)
[ https://issues.apache.org/jira/browse/STORM-248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14253598#comment-14253598 ] Frantz Mazoyer commented on STORM-248: -- Hi, please check following branch : [https://

[jira] [Commented] (STORM-591) logback.xml

2014-12-19 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/STORM-591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14253552#comment-14253552 ] ASF GitHub Bot commented on STORM-591: -- Github user harshach commented on the pull req

[GitHub] storm pull request: [STORM-591] exclude logback.xml from jar

2014-12-19 Thread harshach
Github user harshach commented on the pull request: https://github.com/apache/storm/pull/352#issuecomment-67654350 @Lewuathe I think logback.xml is not being used anymore instead there is logback/cluster.xml, worker.xml. I think a better fix is to remove the file itself. --- If your

[jira] [Updated] (STORM-591) logback.xml

2014-12-19 Thread Sriharsha Chintalapani (JIRA)
[ https://issues.apache.org/jira/browse/STORM-591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sriharsha Chintalapani updated STORM-591: - Assignee: (was: Kai Sasaki) > logback.xml > --- > > Key

[jira] [Updated] (STORM-591) logback.xml

2014-12-19 Thread Sriharsha Chintalapani (JIRA)
[ https://issues.apache.org/jira/browse/STORM-591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sriharsha Chintalapani updated STORM-591: - Assignee: Kai Sasaki > logback.xml > --- > > Key: STORM-591

[jira] [Commented] (STORM-591) logback.xml

2014-12-19 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/STORM-591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14253294#comment-14253294 ] ASF GitHub Bot commented on STORM-591: -- GitHub user Lewuathe opened a pull request:

[GitHub] storm pull request: [STORM-591] exclude logback.xml from jar

2014-12-19 Thread Lewuathe
GitHub user Lewuathe opened a pull request: https://github.com/apache/storm/pull/352 [STORM-591] exclude logback.xml from jar `logback.xml` should not be included jar file because it will override other configuration who use your jar. To avoid this case exclude `logback.xml` fi

[jira] [Commented] (STORM-586) Trident kafka spout fails instead of updating offset when kafka offset is out of range.

2014-12-19 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/STORM-586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14253173#comment-14253173 ] ASF GitHub Bot commented on STORM-586: -- Github user nathanmarz commented on the pull r

[GitHub] storm pull request: STORM-586: TridentKafkaEmitter should catch up...

2014-12-19 Thread nathanmarz
Github user nathanmarz commented on the pull request: https://github.com/apache/storm/pull/339#issuecomment-67615349 Can you elaborate? It should just keep trying that last offset repeatedly. This is a case I tested repeatedly when I originally wrote this, so if this is the case it's