[jira] [Resolved] (STORM-3251) Using Logviewer Filter settings causes anyone to access logs via log viewer REST API
[ https://issues.apache.org/jira/browse/STORM-3251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Joseph Evans resolved STORM-3251. Resolution: Fixed Fix Version/s: 2.0.0 Thanks [~agresch], I merged this into master. > Using Logviewer Filter settings causes anyone to access logs via log viewer > REST API > > > Key: STORM-3251 > URL: https://issues.apache.org/jira/browse/STORM-3251 > Project: Apache Storm > Issue Type: Bug >Reporter: Aaron Gresch >Assignee: Aaron Gresch >Priority: Critical > Labels: pull-request-available > Fix For: 2.0.0 > > Time Spent: 10m > Remaining Estimate: 0h > > The rest API for logviewer access is checking if UI filter params is set to > deny access to users. It's possible now to configure the logviewer without > UI filter params, so this check is no longer sufficient and can allow anyone > access to logs. > > See ResourceAuthorizer line 68 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (STORM-3252) Blobstore sync bug fix
[ https://issues.apache.org/jira/browse/STORM-3252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Joseph Evans reassigned STORM-3252: -- Assignee: Arun Mahadevan > Blobstore sync bug fix > -- > > Key: STORM-3252 > URL: https://issues.apache.org/jira/browse/STORM-3252 > Project: Apache Storm > Issue Type: Bug >Affects Versions: 1.2.2 >Reporter: Arun Mahadevan >Assignee: Arun Mahadevan >Priority: Major > Labels: pull-request-available > Fix For: 2.0.0 > > Time Spent: 1h 50m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (STORM-3252) Blobstore sync bug fix
[ https://issues.apache.org/jira/browse/STORM-3252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Joseph Evans resolved STORM-3252. Resolution: Fixed Fix Version/s: (was: 1.x) Thanks [~arunmahadevan], I merged this into master. > Blobstore sync bug fix > -- > > Key: STORM-3252 > URL: https://issues.apache.org/jira/browse/STORM-3252 > Project: Apache Storm > Issue Type: Bug >Affects Versions: 1.2.2 >Reporter: Arun Mahadevan >Assignee: Arun Mahadevan >Priority: Major > Labels: pull-request-available > Fix For: 2.0.0 > > Time Spent: 1h 50m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (STORM-3255) Run with dev-zookeeper on travis-ci
[
https://issues.apache.org/jira/browse/STORM-3255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated STORM-3255:
--
Labels: pull-request-available (was: )
> Run with dev-zookeeper on travis-ci
> ---
>
> Key: STORM-3255
> URL: https://issues.apache.org/jira/browse/STORM-3255
> Project: Apache Storm
> Issue Type: Bug
> Components: integration-test
>Reporter: Derek Dagit
>Assignee: Derek Dagit
>Priority: Minor
> Labels: pull-request-available
>
> Currently as part of our automated testing on travis-ci, we install ZooKeeper
> using the system's package manager.
> Recently, the version of the {{zookeeper}} package (3.4.5) became unavailable
> from the system's package repositories, and this caused errors in our
> integration tests.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (STORM-3255) Run with dev-zookeeper on travis-ci
Derek Dagit created STORM-3255:
--
Summary: Run with dev-zookeeper on travis-ci
Key: STORM-3255
URL: https://issues.apache.org/jira/browse/STORM-3255
Project: Apache Storm
Issue Type: Bug
Components: integration-test
Reporter: Derek Dagit
Currently as part of our automated testing on travis-ci, we install ZooKeeper
using the system's package manager.
Recently, the version of the {{zookeeper}} package (3.4.5) became unavailable
from the system's package repositories, and this caused errors in our
integration tests.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (STORM-3255) Run with dev-zookeeper on travis-ci
[
https://issues.apache.org/jira/browse/STORM-3255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Derek Dagit reassigned STORM-3255:
--
Assignee: Derek Dagit
> Run with dev-zookeeper on travis-ci
> ---
>
> Key: STORM-3255
> URL: https://issues.apache.org/jira/browse/STORM-3255
> Project: Apache Storm
> Issue Type: Bug
> Components: integration-test
>Reporter: Derek Dagit
>Assignee: Derek Dagit
>Priority: Minor
>
> Currently as part of our automated testing on travis-ci, we install ZooKeeper
> using the system's package manager.
> Recently, the version of the {{zookeeper}} package (3.4.5) became unavailable
> from the system's package repositories, and this caused errors in our
> integration tests.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (STORM-3254) Blob localization time-outs can cause Slot to be stuck and leaked over time
[ https://issues.apache.org/jira/browse/STORM-3254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated STORM-3254: -- Labels: pull-request-available (was: ) > Blob localization time-outs can cause Slot to be stuck and leaked over time > --- > > Key: STORM-3254 > URL: https://issues.apache.org/jira/browse/STORM-3254 > Project: Apache Storm > Issue Type: Bug > Components: storm-server >Reporter: Kishor Patil >Assignee: Kishor Patil >Priority: Major > Labels: pull-request-available > > If Blobs requested by slot take forever to come back, the Slot could get > stuck in _waiting-for-blob-localization_ state, even after release of slot > or topology being killed making that slot unusable. So worker for next > assignment will never be launched. > The steps to reproduce this are: > # Delay blob store localization. > # kill topology and check jstack. > # worker will not be scheduled. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (STORM-3254) Blob localization time-outs can cause Slot to be stuck and leaked over time
Kishor Patil created STORM-3254: --- Summary: Blob localization time-outs can cause Slot to be stuck and leaked over time Key: STORM-3254 URL: https://issues.apache.org/jira/browse/STORM-3254 Project: Apache Storm Issue Type: Bug Components: storm-server Reporter: Kishor Patil Assignee: Kishor Patil If Blobs requested by slot take forever to come back, the Slot could get stuck in _waiting-for-blob-localization_ state, even after release of slot or topology being killed making that slot unusable. So worker for next assignment will never be launched. The steps to reproduce this are: # Delay blob store localization. # kill topology and check jstack. # worker will not be scheduled. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
