[jira] [Resolved] (STORM-2698) Upgrade to newest Mockito and Hamcrest versions

2017-10-09 Thread JIRA
[ https://issues.apache.org/jira/browse/STORM-2698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stig Rohde Døssing resolved STORM-2698. --- Resolution: Fixed Fix Version/s: 2.0.0 > Upgrade to newest Mockito and

[jira] [Updated] (STORM-2759) Let users indicate if a worker should restart on blob download

2017-10-09 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/STORM-2759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated STORM-2759: -- Labels: pull-request-available (was: ) > Let users indicate if a worker should restart on blob

[jira] [Created] (STORM-2771) Some tests are being run twice

2017-10-09 Thread Robert Joseph Evans (JIRA)
Robert Joseph Evans created STORM-2771: -- Summary: Some tests are being run twice Key: STORM-2771 URL: https://issues.apache.org/jira/browse/STORM-2771 Project: Apache Storm Issue Type:

[jira] [Resolved] (STORM-2666) Storm-kafka-client spout can sometimes emit messages that were already committed.

2017-10-09 Thread Jungtaek Lim (JIRA)
[ https://issues.apache.org/jira/browse/STORM-2666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jungtaek Lim resolved STORM-2666. - Resolution: Fixed Fix Version/s: 1.1.2 1.2.0 Thanks [~Srdo], I also

[jira] [Updated] (STORM-2772) In the DRPCSpout class, when the fetch from the DRPC server fails, the log should return to get the DRPC request failed instead of getting the DRPC result failed

2017-10-09 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/STORM-2772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated STORM-2772: -- Labels: pull-request-available (was: ) > In the DRPCSpout class, when the fetch from the DRPC

[jira] [Created] (STORM-2773) If a drpcserver node in cluster is down,drpc cluster won't work is we don't modify the drpc.server configuration and restart the cluster

2017-10-09 Thread liuzhaokun (JIRA)
liuzhaokun created STORM-2773: - Summary: If a drpcserver node in cluster is down,drpc cluster won't work is we don't modify the drpc.server configuration and restart the cluster Key: STORM-2773 URL:

[jira] [Updated] (STORM-2773) If a drpcserver node in cluster is down,drpc cluster won't work if we don't modify the drpc.server configuration and restart the cluster

2017-10-09 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/STORM-2773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated STORM-2773: -- Labels: pull-request-available (was: ) > If a drpcserver node in cluster is down,drpc cluster

[jira] [Created] (STORM-2772) In the DRPCSpout class, when the fetch from the DRPC server fails, the log should return to get the DRPC request failed instead of getting the DRPC result failed

2017-10-09 Thread hantiantian (JIRA)
hantiantian created STORM-2772: -- Summary: In the DRPCSpout class, when the fetch from the DRPC server fails, the log should return to get the DRPC request failed instead of getting the DRPC result failed Key: STORM-2772

[jira] [Updated] (STORM-2773) If a drpcserver node in cluster is down,drpc cluster won't work if we don't modify the drpc.server configuration and restart the cluster

2017-10-09 Thread liuzhaokun (JIRA)
[ https://issues.apache.org/jira/browse/STORM-2773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liuzhaokun updated STORM-2773: -- Summary: If a drpcserver node in cluster is down,drpc cluster won't work if we don't modify the