[jira] [Commented] (STORM-3195) IllegalArgumentException when rolling upgrade nimbus from 1.x to 2.x

2018-08-15 Thread Jungtaek Lim (JIRA) 


[ 
https://issues.apache.org/jira/browse/STORM-3195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16581928#comment-16581928
 ] 

Jungtaek Lim commented on STORM-3195:
-

[~ethanli]
I'm wondering the symptom itself: shouldn't worker count as well as acker 
executor number be integer? No one would say worker count is 1.66 and acker 
executor count is 2.33, so the value itself looks somewhat incorrect to me.

> IllegalArgumentException when rolling upgrade nimbus from 1.x to 2.x
> 
>
> Key: STORM-3195
> URL: https://issues.apache.org/jira/browse/STORM-3195
> Project: Apache Storm
>  Issue Type: Bug
>Reporter: Ethan Li
>Priority: Major
>
> {code:java}
> 2018-08-15 15:49:06.550 o.a.s.d.n.Nimbus timer [ERROR] Error while processing 
> event
> java.lang.RuntimeException: java.lang.IllegalArgumentException: Don't know 
> how to convert 1.76041667 to int
> at 
> org.apache.storm.daemon.nimbus.Nimbus.lambda$launchServer$48(Nimbus.java:2837)
>  ~[storm-server-2.0.0.y.jar:2.0.0.y]
> at org.apache.storm.StormTimer$1.run(StormTimer.java:110) 
> ~[storm-client-2.0.0.y.jar:2.0.0.y]
> at 
> org.apache.storm.StormTimer$StormTimerTask.run(StormTimer.java:226) 
> [storm-client-2.0.0.y.jar:2.0.0.y]
> Caused by: java.lang.IllegalArgumentException: Don't know how to convert 
> 1.76041667 to int
> at org.apache.storm.utils.ObjectReader.getInt(ObjectReader.java:78) 
> ~[storm-client-2.0.0.y.jar:2.0.0.y]
> at org.apache.storm.daemon.StormCommon.addAcker(StormCommon.java:256) 
> ~[storm-client-2.0.0.y.jar:2.0.0.y]
> at 
> org.apache.storm.daemon.StormCommon.systemTopologyImpl(StormCommon.java:523) 
> ~[storm-client-2.0.0.y.jar:2.0.0.y]
> at 
> org.apache.storm.daemon.StormCommon.systemTopology(StormCommon.java:440) 
> ~[storm-client-2.0.0.y.jar:2.0.0.y]
> at 
> org.apache.storm.daemon.StormCommon.stormTaskInfoImpl(StormCommon.java:544) 
> ~[storm-client-2.0.0.y.jar:2.0.0.y]
> at 
> org.apache.storm.daemon.StormCommon.stormTaskInfo(StormCommon.java:460) 
> ~[storm-client-2.0.0.y.jar:2.0.0.y]
> at 
> org.apache.storm.daemon.nimbus.Nimbus.computeExecutors(Nimbus.java:1732) 
> ~[storm-server-2.0.0.y.jar:2.0.0.y]
> at 
> org.apache.storm.daemon.nimbus.Nimbus.getOrUpdateExecutors(Nimbus.java:1357) 
> ~[storm-server-2.0.0.y.jar:2.0.0.y]
> at 
> org.apache.storm.daemon.nimbus.Nimbus.computeExecutorToComponent(Nimbus.java:1752)
>  ~[storm-server-2.0.0.y.jar:2.0.0.y]
> at 
> org.apache.storm.daemon.nimbus.Nimbus.readTopologyDetails(Nimbus.java:1582) 
> ~[storm-server-2.0.0.y.jar:2.0.0.y]
> at 
> org.apache.storm.daemon.nimbus.Nimbus.getResourcesForTopology(Nimbus.java:2034)
>  ~[storm-server-2.0.0.y.jar:2.0.0.y]
> at 
> org.apache.storm.daemon.nimbus.Nimbus.getClusterInfoImpl(Nimbus.java:2676) 
> ~[storm-server-2.0.0.y.jar:2.0.0.y]
> at 
> org.apache.storm.daemon.nimbus.Nimbus.sendClusterMetricsToExecutors(Nimbus.java:2701)
>  ~[storm-server-2.0.0.y.jar:2.0.0.y]
> at 
> org.apache.storm.daemon.nimbus.Nimbus.lambda$launchServer$48(Nimbus.java:2834)
>  ~[storm-server-2.0.0.y.jar:2.0.0.y]
> ... 2 more
> {code}
> We were rolling upgrading our storm cluster to 2.x and we found this error 
> from nimbus.log. It's not necessary to do rolling upgrade but good news is we 
> basically made it work. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (STORM-3196) 'storm list' should include topology owner in output

2018-08-15 Thread ASF GitHub Bot (JIRA) 


 [ 
https://issues.apache.org/jira/browse/STORM-3196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

ASF GitHub Bot updated STORM-3196:
--
Labels: pull-request-available  (was: )

> 'storm list' should include topology owner in output
> 
>
> Key: STORM-3196
> URL: https://issues.apache.org/jira/browse/STORM-3196
> Project: Apache Storm
>  Issue Type: Improvement
>Reporter: Jacob Tolar
>Assignee: Jacob Tolar
>Priority: Minor
>  Labels: pull-request-available
>
> It would be helpful if 'storm list' included the owner in the output.
> For example:
> {code:java}
> Topology_name Status Num_tasks Num_workers Uptime_secs Owner
> ---
> my_topology ACTIVE 205 15 123456 jtolar
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (STORM-2578) Apply new code style to storm-elasticsearch

2018-08-15 Thread ASF GitHub Bot (JIRA) 


 [ 
https://issues.apache.org/jira/browse/STORM-2578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

ASF GitHub Bot updated STORM-2578:
--
Labels: pull-request-available  (was: )

> Apply new code style to storm-elasticsearch
> ---
>
> Key: STORM-2578
> URL: https://issues.apache.org/jira/browse/STORM-2578
> Project: Apache Storm
>  Issue Type: Task
>  Components: storm-elasticsearch
>Affects Versions: 2.0.0
>Reporter: Jungtaek Lim
>Assignee: Jing Chen
>Priority: Major
>  Labels: pull-request-available
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (STORM-3196) 'storm list' should include topology owner in output

2018-08-15 Thread Jacob Tolar (JIRA) 


 [ 
https://issues.apache.org/jira/browse/STORM-3196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jacob Tolar updated STORM-3196:
---
Issue Type: Improvement  (was: Bug)

> 'storm list' should include topology owner in output
> 
>
> Key: STORM-3196
> URL: https://issues.apache.org/jira/browse/STORM-3196
> Project: Apache Storm
>  Issue Type: Improvement
>Reporter: Jacob Tolar
>Assignee: Jacob Tolar
>Priority: Minor
>
> It would be helpful if 'storm list' included the owner in the output.
> For example:
> {code:java}
> Topology_name Status Num_tasks Num_workers Uptime_secs Owner
> ---
> my_topology ACTIVE 205 15 123456 jtolar
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (STORM-3196) 'storm list' should include topology owner in output

2018-08-15 Thread Jacob Tolar (JIRA) 
Jacob Tolar created STORM-3196:
--

 Summary: 'storm list' should include topology owner in output
 Key: STORM-3196
 URL: https://issues.apache.org/jira/browse/STORM-3196
 Project: Apache Storm
  Issue Type: Bug
Reporter: Jacob Tolar
Assignee: Jacob Tolar


It would be helpful if 'storm list' included the owner in the output.

For example:
{code:java}
Topology_name Status Num_tasks Num_workers Uptime_secs Owner
---
my_topology ACTIVE 205 15 123456 jtolar
{code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Closed] (STORM-3195) IllegalArgumentException when rolling upgrade nimbus from 1.x to 2.x

2018-08-15 Thread Ethan Li (JIRA) 


 [ 
https://issues.apache.org/jira/browse/STORM-3195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ethan Li closed STORM-3195.
---
Resolution: Invalid

Community 1.x will not have this issue because 
https://github.com/apache/storm/pull/2325 wasn't merged into 1.x. The worker 
count will always be int and acker executer number will always be int. 

Our internal version 1.x has https://github.com/apache/storm/pull/2325 feature. 
And that's why it happened. 

> IllegalArgumentException when rolling upgrade nimbus from 1.x to 2.x
> 
>
> Key: STORM-3195
> URL: https://issues.apache.org/jira/browse/STORM-3195
> Project: Apache Storm
>  Issue Type: Bug
>Reporter: Ethan Li
>Priority: Major
>
> {code:java}
> 2018-08-15 15:49:06.550 o.a.s.d.n.Nimbus timer [ERROR] Error while processing 
> event
> java.lang.RuntimeException: java.lang.IllegalArgumentException: Don't know 
> how to convert 1.76041667 to int
> at 
> org.apache.storm.daemon.nimbus.Nimbus.lambda$launchServer$48(Nimbus.java:2837)
>  ~[storm-server-2.0.0.y.jar:2.0.0.y]
> at org.apache.storm.StormTimer$1.run(StormTimer.java:110) 
> ~[storm-client-2.0.0.y.jar:2.0.0.y]
> at 
> org.apache.storm.StormTimer$StormTimerTask.run(StormTimer.java:226) 
> [storm-client-2.0.0.y.jar:2.0.0.y]
> Caused by: java.lang.IllegalArgumentException: Don't know how to convert 
> 1.76041667 to int
> at org.apache.storm.utils.ObjectReader.getInt(ObjectReader.java:78) 
> ~[storm-client-2.0.0.y.jar:2.0.0.y]
> at org.apache.storm.daemon.StormCommon.addAcker(StormCommon.java:256) 
> ~[storm-client-2.0.0.y.jar:2.0.0.y]
> at 
> org.apache.storm.daemon.StormCommon.systemTopologyImpl(StormCommon.java:523) 
> ~[storm-client-2.0.0.y.jar:2.0.0.y]
> at 
> org.apache.storm.daemon.StormCommon.systemTopology(StormCommon.java:440) 
> ~[storm-client-2.0.0.y.jar:2.0.0.y]
> at 
> org.apache.storm.daemon.StormCommon.stormTaskInfoImpl(StormCommon.java:544) 
> ~[storm-client-2.0.0.y.jar:2.0.0.y]
> at 
> org.apache.storm.daemon.StormCommon.stormTaskInfo(StormCommon.java:460) 
> ~[storm-client-2.0.0.y.jar:2.0.0.y]
> at 
> org.apache.storm.daemon.nimbus.Nimbus.computeExecutors(Nimbus.java:1732) 
> ~[storm-server-2.0.0.y.jar:2.0.0.y]
> at 
> org.apache.storm.daemon.nimbus.Nimbus.getOrUpdateExecutors(Nimbus.java:1357) 
> ~[storm-server-2.0.0.y.jar:2.0.0.y]
> at 
> org.apache.storm.daemon.nimbus.Nimbus.computeExecutorToComponent(Nimbus.java:1752)
>  ~[storm-server-2.0.0.y.jar:2.0.0.y]
> at 
> org.apache.storm.daemon.nimbus.Nimbus.readTopologyDetails(Nimbus.java:1582) 
> ~[storm-server-2.0.0.y.jar:2.0.0.y]
> at 
> org.apache.storm.daemon.nimbus.Nimbus.getResourcesForTopology(Nimbus.java:2034)
>  ~[storm-server-2.0.0.y.jar:2.0.0.y]
> at 
> org.apache.storm.daemon.nimbus.Nimbus.getClusterInfoImpl(Nimbus.java:2676) 
> ~[storm-server-2.0.0.y.jar:2.0.0.y]
> at 
> org.apache.storm.daemon.nimbus.Nimbus.sendClusterMetricsToExecutors(Nimbus.java:2701)
>  ~[storm-server-2.0.0.y.jar:2.0.0.y]
> at 
> org.apache.storm.daemon.nimbus.Nimbus.lambda$launchServer$48(Nimbus.java:2834)
>  ~[storm-server-2.0.0.y.jar:2.0.0.y]
> ... 2 more
> {code}
> We were rolling upgrading our storm cluster to 2.x and we found this error 
> from nimbus.log. It's not necessary to do rolling upgrade but good news is we 
> basically made it work. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (STORM-3195) IllegalArgumentException when rolling upgrade nimbus from 1.x to 2.x

2018-08-15 Thread Ethan Li (JIRA) 
Ethan Li created STORM-3195:
---

 Summary: IllegalArgumentException when rolling upgrade nimbus from 
1.x to 2.x
 Key: STORM-3195
 URL: https://issues.apache.org/jira/browse/STORM-3195
 Project: Apache Storm
  Issue Type: Bug
Reporter: Ethan Li



{code:java}
2018-08-15 15:49:06.550 o.a.s.d.n.Nimbus timer [ERROR] Error while processing 
event
java.lang.RuntimeException: java.lang.IllegalArgumentException: Don't know how 
to convert 1.76041667 to int
at 
org.apache.storm.daemon.nimbus.Nimbus.lambda$launchServer$48(Nimbus.java:2837) 
~[storm-server-2.0.0.y.jar:2.0.0.y]
at org.apache.storm.StormTimer$1.run(StormTimer.java:110) 
~[storm-client-2.0.0.y.jar:2.0.0.y]
at org.apache.storm.StormTimer$StormTimerTask.run(StormTimer.java:226) 
[storm-client-2.0.0.y.jar:2.0.0.y]
Caused by: java.lang.IllegalArgumentException: Don't know how to convert 
1.76041667 to int
at org.apache.storm.utils.ObjectReader.getInt(ObjectReader.java:78) 
~[storm-client-2.0.0.y.jar:2.0.0.y]
at org.apache.storm.daemon.StormCommon.addAcker(StormCommon.java:256) 
~[storm-client-2.0.0.y.jar:2.0.0.y]
at 
org.apache.storm.daemon.StormCommon.systemTopologyImpl(StormCommon.java:523) 
~[storm-client-2.0.0.y.jar:2.0.0.y]
at 
org.apache.storm.daemon.StormCommon.systemTopology(StormCommon.java:440) 
~[storm-client-2.0.0.y.jar:2.0.0.y]
at 
org.apache.storm.daemon.StormCommon.stormTaskInfoImpl(StormCommon.java:544) 
~[storm-client-2.0.0.y.jar:2.0.0.y]
at 
org.apache.storm.daemon.StormCommon.stormTaskInfo(StormCommon.java:460) 
~[storm-client-2.0.0.y.jar:2.0.0.y]
at 
org.apache.storm.daemon.nimbus.Nimbus.computeExecutors(Nimbus.java:1732) 
~[storm-server-2.0.0.y.jar:2.0.0.y]
at 
org.apache.storm.daemon.nimbus.Nimbus.getOrUpdateExecutors(Nimbus.java:1357) 
~[storm-server-2.0.0.y.jar:2.0.0.y]
at 
org.apache.storm.daemon.nimbus.Nimbus.computeExecutorToComponent(Nimbus.java:1752)
 ~[storm-server-2.0.0.y.jar:2.0.0.y]
at 
org.apache.storm.daemon.nimbus.Nimbus.readTopologyDetails(Nimbus.java:1582) 
~[storm-server-2.0.0.y.jar:2.0.0.y]
at 
org.apache.storm.daemon.nimbus.Nimbus.getResourcesForTopology(Nimbus.java:2034) 
~[storm-server-2.0.0.y.jar:2.0.0.y]
at 
org.apache.storm.daemon.nimbus.Nimbus.getClusterInfoImpl(Nimbus.java:2676) 
~[storm-server-2.0.0.y.jar:2.0.0.y]
at 
org.apache.storm.daemon.nimbus.Nimbus.sendClusterMetricsToExecutors(Nimbus.java:2701)
 ~[storm-server-2.0.0.y.jar:2.0.0.y]
at 
org.apache.storm.daemon.nimbus.Nimbus.lambda$launchServer$48(Nimbus.java:2834) 
~[storm-server-2.0.0.y.jar:2.0.0.y]
... 2 more
{code}

We were rolling upgrading our storm cluster to 2.x and we found this error from 
nimbus.log. It's not necessary to do rolling upgrade but good news is we 
basically made it work. 





--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (STORM-2617) log4j2 RollingFile rotation failing

2018-08-15 Thread Ivan Omar Olguin Torres (JIRA) 


[ 
https://issues.apache.org/jira/browse/STORM-2617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16581284#comment-16581284
 ] 

Ivan Omar Olguin Torres commented on STORM-2617:


This is a bug in log4j2:

https://issues.apache.org/jira/browse/LOG4J2-1804

The workaround works for me.

> log4j2 RollingFile rotation failing
> ---
>
> Key: STORM-2617
> URL: https://issues.apache.org/jira/browse/STORM-2617
> Project: Apache Storm
>  Issue Type: Bug
>  Components: storm-server
>Affects Versions: 1.1.0
> Environment: NA
>Reporter: Daniel Kinon
>Priority: Minor
>
> I noticed that the default log rotation configuration isn't working as 
> expected.  A specific example is worker.log.  Here is the default log4j2 
> configuration for worker.log (log4j2/worker.xml):
> {code:xml}
>  
> fileName="${sys:workers.artifacts}/${sys:storm.id}/${sys:worker.port}/${sys:logfile.name}"
> 
> filePattern="${sys:workers.artifacts}/${sys:storm.id}/${sys:worker.port}/${sys:logfile.name}.%i.gz">
> 
> ${pattern}
> 
> 
>  
> 
> 
> 
> {code}
> Even thought the DefaultRolloverStrategy is set to 9, I only ever see 
> worker.log and worker.log.1.gz.  It seems like rotation is continually 
> overwriting worker.log.1.gz .  I expect this is either an issue with log4j2 
> or an issue related to the RollingFileAppender and the associated filePattern.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)