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

2018-10-05 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 resolved STORM-3246.

   Resolution: Fixed
Fix Version/s: 2.0.1

Thanks [~kishorvpatil],

 

I merged this into master.  If you want it to go anywhere else just let me know 
and we can cherry-pick it.

> 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.1
>
>  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] [Resolved] (STORM-3244) Logviewer uses UI filter settings

2018-10-05 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 resolved STORM-3244.

   Resolution: Fixed
Fix Version/s: 2.0.1

Thanks [~agresch],

 

I merged this into master.

> 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.1
>
>  Time Spent: 40m
>  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] [Resolved] (STORM-3245) Log viewer cleanup failes if multiple empty worker-artifact dirs

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


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

Robert Joseph Evans resolved STORM-3245.

   Resolution: Fixed
Fix Version/s: 2.0.1

> Log viewer cleanup failes if multiple empty worker-artifact dirs
> 
>
> Key: STORM-3245
> URL: https://issues.apache.org/jira/browse/STORM-3245
> Project: Apache Storm
>  Issue Type: Bug
>  Components: storm-server
>Affects Versions: 2.0.0
>Reporter: Robert Joseph Evans
>Assignee: Robert Joseph Evans
>Priority: Blocker
>  Labels: pull-request-available
> Fix For: 2.0.1
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> If a drive fills up for various reasons it is possible that we can create the 
> directory for a worker in worker-artifacts, but not able to create the 
> worker.yaml.  If we get more than one of these on a node we get an exception 
> like.
>  
> {code:java}
> o.a.s.d.l.u.LogCleaner logviewer-cleanup [ERROR] Exception while cleaning up 
> old log.
> java.lang.IllegalStateException: Duplicate key ...
>     at 
> java.util.stream.Collectors.lambda$throwingMerger$0(Collectors.java:133) 
> ~[?:1.8.0_102]
>     at java.util.HashMap.merge(HashMap.java:1253) ~[?:1.8.0_102]
>     at java.util.stream.Collectors.lambda$toMap$58(Collectors.java:1320) 
> ~[?:1.8.0_102]
>     at 
> java.util.stream.ReduceOps$3ReducingSink.accept(ReduceOps.java:169) 
> ~[?:1.8.0_102]
>     at 
> java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:193) 
> ~[?:1.8.0_102]
>     at 
> java.util.TreeMap$KeySpliterator.forEachRemaining(TreeMap.java:2746) 
> ~[?:1.8.0_102]
>     at 
> java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:481) 
> ~[?:1.8.0_102]
>     at 
> java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:471) 
> ~[?:1.8.0_102]
>     at 
> java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:708) 
> ~[?:1.8.0_102]
>     at 
> java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234) 
> ~[?:1.8.0_102]
>     at 
> java.util.stream.ReferencePipeline.collect(ReferencePipeline.java:499) 
> ~[?:1.8.0_102]
>     at 
> org.apache.storm.daemon.logviewer.utils.WorkerLogs.identifyWorkerLogDirs(WorkerLogs.java:214)
>  ~[storm-webapp-...{code}
> After that we cannot clean up any directories any longer...



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


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

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


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

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

> 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
>
> BLOBSTORE_SUPERUSER doesn't appear to be used. 



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


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

2018-10-05 Thread Aaron Gresch (JIRA)
Aaron Gresch created STORM-3247:
---

 Summary: 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


BLOBSTORE_SUPERUSER doesn't appear to be used. 



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