[jira] [Assigned] (STORM-3243) Clean up Maven POM dependency on clojure

2018-10-08 Thread Derek Dagit (JIRA)


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

Derek Dagit reassigned STORM-3243:
--

Assignee: Derek Dagit

> Clean up Maven POM dependency on clojure
> 
>
> Key: STORM-3243
> URL: https://issues.apache.org/jira/browse/STORM-3243
> Project: Apache Storm
>  Issue Type: Improvement
>  Components: build
>Reporter: Derek Dagit
>Assignee: Derek Dagit
>Priority: Major
>  Labels: java-migration, jstorm-merger
>
> Investigate whether we can drop non-test dependencies on Clojure. Drop 
> dependencies on Clojure that we no longer need.



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


[jira] [Updated] (STORM-1318) Investigate if backtype.storm.command.shell-submission shuld be dropped

2018-10-08 Thread Robert Joseph Evans (JIRA)


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

Robert Joseph Evans updated STORM-1318:
---
Fix Version/s: (was: 2.0.1)
   2.0.0

> Investigate if backtype.storm.command.shell-submission shuld be dropped
> ---
>
> Key: STORM-1318
> URL: https://issues.apache.org/jira/browse/STORM-1318
> Project: Apache Storm
>  Issue Type: New Feature
>Reporter: Robert Joseph Evans
>Assignee: Derek Dagit
>Priority: Major
>  Labels: java-migration, jstorm-merger, pull-request-available
> Fix For: 2.0.0
>
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> As part of the merger with Jstorm we need to decide if 
> backtype.storm.command.shell-submission should be dropped, or if we should 
> migrate it over to a storm-clojure package.



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


[jira] [Updated] (STORM-621) UI should expose more version information

2018-10-08 Thread Robert Joseph Evans (JIRA)


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

Robert Joseph Evans updated STORM-621:
--
Fix Version/s: (was: 2.0.1)
   2.0.0

> UI should expose more version information
> -
>
> Key: STORM-621
> URL: https://issues.apache.org/jira/browse/STORM-621
> Project: Apache Storm
>  Issue Type: Improvement
>  Components: storm-core
>Affects Versions: 0.10.0
>Reporter: caofangkun
>Assignee: Robert Joseph Evans
>Priority: Minor
> Fix For: 2.0.0
>
>
> We should view the following information on UI page:
> Storm Version: 0.10.0-SNAPSHOT
> Git https  clone URL : https://github.com/caofangkun/apache-storm.git -r 
> ffba148cc47a92185fa1a5db11f72982de10f106
> Git last checkin id: ffba148cc47a92185fa1a5db11f72982de10f106
> Branch storm-243
> Compiled by somebody on Thu Jan 8 10:47:48 CST 2015
> From source with checksum 97e7c942939e3e82dcb854b497991a51



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


[jira] [Updated] (STORM-2963) Updates to Performance.md

2018-10-08 Thread Robert Joseph Evans (JIRA)


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

Robert Joseph Evans updated STORM-2963:
---
Fix Version/s: (was: 2.0.1)
   2.0.0

> Updates to Performance.md 
> --
>
> Key: STORM-2963
> URL: https://issues.apache.org/jira/browse/STORM-2963
> Project: Apache Storm
>  Issue Type: Documentation
>Affects Versions: 2.0.0
>Reporter: Roshan Naik
>Assignee: Roshan Naik
>Priority: Major
>  Labels: pull-request-available
> Fix For: 2.0.0
>
>  Time Spent: 50m
>  Remaining Estimate: 0h
>




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


[jira] [Updated] (STORM-3236) DRPC meterShutdownCalls marked after metrics stopped

2018-10-08 Thread Robert Joseph Evans (JIRA)


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

Robert Joseph Evans updated STORM-3236:
---
Fix Version/s: (was: 2.0.1)
   2.0.0

> DRPC meterShutdownCalls marked after metrics stopped
> 
>
> Key: STORM-3236
> URL: https://issues.apache.org/jira/browse/STORM-3236
> Project: Apache Storm
>  Issue Type: Bug
>Affects Versions: 2.0.0
>Reporter: Aaron Gresch
>Assignee: Aaron Gresch
>Priority: Minor
>  Labels: pull-request-available
> Fix For: 2.0.0
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> If we want to track shutdown calls, we need to mark before the 
> metricsRegistry.stopMetricsReporters() call occurs.



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


[jira] [Updated] (STORM-3233) Upgrade zookeeper client to newest version (3.4.14)

2018-10-08 Thread Robert Joseph Evans (JIRA)


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

Robert Joseph Evans updated STORM-3233:
---
Fix Version/s: (was: 2.0.1)
   2.0.0

> Upgrade zookeeper client to newest version (3.4.14)
> ---
>
> Key: STORM-3233
> URL: https://issues.apache.org/jira/browse/STORM-3233
> Project: Apache Storm
>  Issue Type: New Feature
>  Components: storm-core
>Affects Versions: 2.0.0
>Reporter: Michal Koziorowski
>Assignee: Michal Koziorowski
>Priority: Major
>  Labels: pull-request-available
> Fix For: 2.0.0, 1.2.3, 1.1.4
>
>  Time Spent: 1h
>  Remaining Estimate: 0h
>
> Hi,
> I would like to see new zookeeper client (3.4.13) used in storm.
> New release contains an important fix for cloud environments where zookeeper 
> servers have dynamic ips 
> ([https://jira.apache.org/jira/browse/ZOOKEEPER-2184]).
> If possible, it would be nice to see updated zookeeper also on older storm 
> versions (1.2.x, 1.1.x)



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


[jira] [Updated] (STORM-3238) The result of log search for topology doesn't show in UI page

2018-10-08 Thread Robert Joseph Evans (JIRA)


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

Robert Joseph Evans updated STORM-3238:
---
Fix Version/s: (was: 2.0.1)
   2.0.0

> The result of log search for topology doesn't show in UI page
> -
>
> Key: STORM-3238
> URL: https://issues.apache.org/jira/browse/STORM-3238
> Project: Apache Storm
>  Issue Type: Bug
>  Components: storm-ui
>Affects Versions: 2.0.0
>Reporter: Jungtaek Lim
>Assignee: Derek Dagit
>Priority: Blocker
>  Labels: pull-request-available
> Fix For: 2.0.0
>
> Attachments: Screen Shot 2018-09-30 at 4.26.12 PM.png, Screen Shot 
> 2018-09-30 at 4.26.23 PM.png, Screen Shot 2018-09-30 at 4.27.26 PM.png, 
> Screen Shot 2018-09-30 at 4.27.36 PM.png
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> Please refer the attachments to see the symptom. The result seems to be 
> returned from Logviewer but UI doesn't reflect the output.



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


[jira] [Updated] (STORM-3235) Auto renewal of WorkerTokens broken.

2018-10-08 Thread Robert Joseph Evans (JIRA)


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

Robert Joseph Evans updated STORM-3235:
---
Fix Version/s: (was: 2.0.1)
   2.0.0

> Auto renewal of WorkerTokens broken.
> 
>
> Key: STORM-3235
> URL: https://issues.apache.org/jira/browse/STORM-3235
> Project: Apache Storm
>  Issue Type: Bug
>  Components: storm-server
>Reporter: Kishor Patil
>Assignee: Kishor Patil
>Priority: Major
>  Labels: pull-request-available
> Fix For: 2.0.0
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> The condition to renew WorkerToken needs fix and refactor code out of 
> {{Nimbus}} into {{WorkerTokenManager}}.
>  



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


[jira] [Updated] (STORM-3234) Document Cluster Metrics

2018-10-08 Thread Robert Joseph Evans (JIRA)


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

Robert Joseph Evans updated STORM-3234:
---
Fix Version/s: (was: 2.0.1)
   2.0.0

> Document Cluster Metrics
> 
>
> Key: STORM-3234
> URL: https://issues.apache.org/jira/browse/STORM-3234
> Project: Apache Storm
>  Issue Type: New Feature
>  Components: documentation
>Affects Versions: 2.0.0
>Reporter: Robert Joseph Evans
>Assignee: Robert Joseph Evans
>Priority: Major
>  Labels: pull-request-available
> Fix For: 2.0.0
>
>  Time Spent: 50m
>  Remaining Estimate: 0h
>
> We need better docs on what cluster metrics we have in storm.



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


[jira] [Updated] (STORM-3237) create metric to track mkAssignments exceptions

2018-10-08 Thread Robert Joseph Evans (JIRA)


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

Robert Joseph Evans updated STORM-3237:
---
Fix Version/s: (was: 2.0.1)
   2.0.0

> create metric to track mkAssignments exceptions
> ---
>
> Key: STORM-3237
> URL: https://issues.apache.org/jira/browse/STORM-3237
> Project: Apache Storm
>  Issue Type: Bug
>Affects Versions: 2.0.0
>Reporter: Aaron Gresch
>Assignee: Aaron Gresch
>Priority: Minor
>  Labels: pull-request-available
> Fix For: 2.0.0
>
>  Time Spent: 1h 50m
>  Remaining Estimate: 0h
>
> We had an issue in the past where scheduling was throwing exceptions on 
> nimbus.  I'd like to be able to monitor this issue going forward.



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


[jira] [Updated] (STORM-3244) Logviewer uses UI filter settings

2018-10-08 Thread Robert Joseph Evans (JIRA)


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

Robert Joseph Evans updated STORM-3244:
---
Fix Version/s: (was: 2.0.1)
   2.0.0

> Logviewer uses UI filter settings
> -
>
> Key: STORM-3244
> URL: https://issues.apache.org/jira/browse/STORM-3244
> Project: Apache Storm
>  Issue Type: Bug
>Reporter: Aaron Gresch
>Assignee: Aaron Gresch
>Priority: Minor
>  Labels: pull-request-available
> Fix For: 2.0.0
>
>  Time Spent: 50m
>  Remaining Estimate: 0h
>
> I was configuring filter settings for the logviewer and discovered I needed 
> to update "ui.filter.params" for the logviewer.  Logviewer should use it's 
> own settings.



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


[jira] [Updated] (STORM-3240) healthchecks fail if scripts return 0 exit code

2018-10-08 Thread Robert Joseph Evans (JIRA)


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

Robert Joseph Evans updated STORM-3240:
---
Fix Version/s: (was: 2.0.1)
   2.0.0

> healthchecks fail if scripts return 0 exit code
> ---
>
> Key: STORM-3240
> URL: https://issues.apache.org/jira/browse/STORM-3240
> Project: Apache Storm
>  Issue Type: Bug
>Affects Versions: 2.0.0
>Reporter: Aaron Gresch
>Assignee: Aaron Gresch
>Priority: Major
>  Labels: pull-request-available
> Fix For: 2.0.0
>
>  Time Spent: 2h
>  Remaining Estimate: 0h
>




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


[jira] [Updated] (STORM-3239) Worker profile actions don't work

2018-10-08 Thread Robert Joseph Evans (JIRA)


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

Robert Joseph Evans updated STORM-3239:
---
Fix Version/s: (was: 2.0.1)
   2.0.0

> Worker profile actions don't work
> -
>
> Key: STORM-3239
> URL: https://issues.apache.org/jira/browse/STORM-3239
> Project: Apache Storm
>  Issue Type: Bug
>  Components: storm-ui
>Affects Versions: 2.0.0
>Reporter: Jungtaek Lim
>Assignee: Govind Menon
>Priority: Blocker
>  Labels: pull-request-available
> Fix For: 2.0.0
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> I just noticed that all worker profile actions don't work in 2.0.0-RC1. 
> access-ui logged the message that the action happened, but there's no further 
> log message as well as no action.
> Assigning to [~govindmenon] since he said he is working on this in mailing 
> list.



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


[jira] [Updated] (STORM-3241) Event Log link on the UI Component page is broken when topology.eventlogger.executors is 0

2018-10-08 Thread Robert Joseph Evans (JIRA)


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

Robert Joseph Evans updated STORM-3241:
---
Fix Version/s: (was: 2.0.1)
   2.0.0

> Event Log link on the UI Component page is broken when 
> topology.eventlogger.executors is 0
> --
>
> Key: STORM-3241
> URL: https://issues.apache.org/jira/browse/STORM-3241
> Project: Apache Storm
>  Issue Type: Bug
>  Components: storm-webapp
>Reporter: Derek Dagit
>Assignee: Derek Dagit
>Priority: Major
>  Labels: pull-request-available
> Fix For: 2.0.0
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> The event log link can appear with {{null}} in place of the host. We should 
> hide the event log link when no eventlogger executors have been configured to 
> run.



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


[jira] [Updated] (STORM-3246) Use UTF-8 charset to ensure log capture non ascii characters from logs

2018-10-08 Thread Robert Joseph Evans (JIRA)


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

Robert Joseph Evans updated STORM-3246:
---
Fix Version/s: (was: 2.0.1)
   2.0.0

> Use UTF-8 charset to ensure log capture non ascii characters from logs
> --
>
> Key: STORM-3246
> URL: https://issues.apache.org/jira/browse/STORM-3246
> Project: Apache Storm
>  Issue Type: Bug
>  Components: storm-client, storm-core
>Reporter: Kishor Patil
>Assignee: Kishor Patil
>Priority: Minor
>  Labels: pull-request-available
> Fix For: 2.0.0
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> Many a times, user events contain non-standard characters and not print them 
> in visible mode can make it difficult to debug.



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


[jira] [Updated] (STORM-3247) remove BLOBSTORE_SUPERUSER

2018-10-08 Thread Robert Joseph Evans (JIRA)


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

Robert Joseph Evans updated STORM-3247:
---
Fix Version/s: (was: 2.0.1)
   2.0.0

> remove BLOBSTORE_SUPERUSER
> --
>
> Key: STORM-3247
> URL: https://issues.apache.org/jira/browse/STORM-3247
> Project: Apache Storm
>  Issue Type: Bug
>Affects Versions: 2.0.0
>Reporter: Aaron Gresch
>Assignee: Aaron Gresch
>Priority: Minor
>  Labels: pull-request-available
> Fix For: 2.0.0
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> BLOBSTORE_SUPERUSER doesn't appear to be used. 



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


[jira] [Assigned] (STORM-3250) Clean up old Pull Requests

2018-10-08 Thread Derek Dagit (JIRA)


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

Derek Dagit reassigned STORM-3250:
--

Assignee: Derek Dagit

> Clean up old Pull Requests
> --
>
> Key: STORM-3250
> URL: https://issues.apache.org/jira/browse/STORM-3250
> Project: Apache Storm
>  Issue Type: Task
>Reporter: Derek Dagit
>Assignee: Derek Dagit
>Priority: Minor
>
> Close [pull 
> requests|https://github.com/apache/storm/pulls?utf8=%E2%9C%93=is%3Apr+is%3Aopen+updated%3A%3C2018-01-01]
>  that have not been updated in 2018.



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


[jira] [Created] (STORM-3250) Clean up old Pull Requests

2018-10-08 Thread Derek Dagit (JIRA)
Derek Dagit created STORM-3250:
--

 Summary: Clean up old Pull Requests
 Key: STORM-3250
 URL: https://issues.apache.org/jira/browse/STORM-3250
 Project: Apache Storm
  Issue Type: Task
Reporter: Derek Dagit


Close [pull 
requests|https://github.com/apache/storm/pulls?utf8=%E2%9C%93=is%3Apr+is%3Aopen+updated%3A%3C2018-01-01]
 that have not been updated in 2018.



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


[jira] [Updated] (STORM-3249) Nimbus Shutdown Faster

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


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

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

> Nimbus Shutdown Faster
> --
>
> Key: STORM-3249
> URL: https://issues.apache.org/jira/browse/STORM-3249
> Project: Apache Storm
>  Issue Type: Bug
>  Components: storm-server
>Affects Versions: 2.0.0
>Reporter: Robert Joseph Evans
>Assignee: Robert Joseph Evans
>Priority: Major
>  Labels: pull-request-available
>
> Nimbus takes for ever to shut down in 2.x.  It would really be nice to fix 
> that. (and it is really our own fault why it takes so long)



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


[jira] [Created] (STORM-3248) outputStats not returned in getComponent via Storm API

2018-10-08 Thread Govind Menon (JIRA)
Govind Menon created STORM-3248:
---

 Summary: outputStats not returned in getComponent via Storm API
 Key: STORM-3248
 URL: https://issues.apache.org/jira/browse/STORM-3248
 Project: Apache Storm
  Issue Type: Bug
Reporter: Govind Menon
Assignee: Govind Menon






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


[jira] [Resolved] (STORM-3247) remove BLOBSTORE_SUPERUSER

2018-10-08 Thread Robert Joseph Evans (JIRA)


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

Robert Joseph Evans resolved STORM-3247.

   Resolution: Fixed
Fix Version/s: 2.0.1

Thanks [~agresch],

 

I merged this into master

> remove BLOBSTORE_SUPERUSER
> --
>
> Key: STORM-3247
> URL: https://issues.apache.org/jira/browse/STORM-3247
> Project: Apache Storm
>  Issue Type: Bug
>Affects Versions: 2.0.0
>Reporter: Aaron Gresch
>Assignee: Aaron Gresch
>Priority: Minor
>  Labels: pull-request-available
> Fix For: 2.0.1
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> BLOBSTORE_SUPERUSER doesn't appear to be used. 



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