[jira] [Closed] (STORM-3049) a potential NPE in SupervisorSimpleACLAuthorizer#permit SimpleACLAuthorizer#permit
[
https://issues.apache.org/jira/browse/STORM-3049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Zowalla closed STORM-3049.
--
Resolution: Won't Fix
We are in the process of migrating our issue tracking system to GitHub issues.
This issue has been stale for the last 5 years, and STORM has evolved with many
dependency updates since this issue was last updated.
If the issue persists in the latest version of Storm, please feel free to
reopen it or provide new context. Thank you very much!
> a potential NPE in SupervisorSimpleACLAuthorizer#permit
> SimpleACLAuthorizer#permit
> --
>
> Key: STORM-3049
> URL: https://issues.apache.org/jira/browse/STORM-3049
> Project: Apache Storm
> Issue Type: Bug
>Reporter: lujie
>Priority: Major
> Labels: pull-request-available
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> We have developed a static analysis tool
> [NPEDetector|https://github.com/lujiefsi/NPEDetector] to find some potential
> NPE. Our analysis shows that some callees may return null in corner case(e.g.
> node crash , IO exception), some of their callers have _!=null_ check but
> some do not have.
> *Bug:*
> callee ReqContext#principal have 12 callers, 10 of them have null checker
> like:
> {code:java}
> public boolean permit(ReqContext context, String operation, Map Object> topoConf) {
> return context.principal() != null ?
> users.contains(context.principal().getName()) : false;
> }
> {code}
> but SupervisorSimpleACLAuthorizer#permit and SimpleACLAuthorizer#permit have
> no, just like:
> {code:java}
> //SupervisorSimpleACLAuthorizer#permit
> String principal = context.principal().getName();{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (STORM-3051) some Potential NPEs
[
https://issues.apache.org/jira/browse/STORM-3051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Zowalla closed STORM-3051.
--
Resolution: Won't Fix
We are in the process of migrating our issue tracking system to GitHub issues.
This issue has been stale for the last 5 years, and STORM has evolved with many
dependency updates since this issue was last updated.
If the issue persists in the latest version of Storm, please feel free to
reopen it or provide new context. Thank you very much!
> some Potential NPEs
> -
>
> Key: STORM-3051
> URL: https://issues.apache.org/jira/browse/STORM-3051
> Project: Apache Storm
> Issue Type: Bug
>Reporter: lujie
>Priority: Major
> Labels: pull-request-available
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> We have developed a static analysis tool
> [NPEDetector|https://github.com/lujiefsi/NPEDetector] to find some potential
> NPE. Our analysis shows that some callees may return null in corner case(e.g.
> node crash , IO exception), some of their callers have _!=null_ check but
> some do not have.
> *Bug:*
> 1. callee CgroupCenter#getSubSystems return null when meet exception:
> {code:java}
> } catch (Exception e) {
> LOG.error("Get subSystems error {}", e);
> }
> return null;
> {code}
> but its caller use it without check:
> {code:java}
> public boolean isSubSystemEnabled(SubSystemType subSystemType) {
> Set subSystems = this.getSubSystems();
> for (SubSystem subSystem : subSystems) {
> if (subSystem.getType() == subSystemType) {
> return true;
> }
> }
> return false;
> }{code}
> other callee and caller pair that have same problem.
> 2. callee RAS_Node#getUsedSlots and caller RAS_Node#totalSlotsUsed
> 3. CgroupCenter#getHierarchies and caller CgroupCenter#isMounted,
> CgroupCenter#getHierarchyWithSubSystems
> 4. callee LocalState#getApprovedWorkers and caller
> BasicContainer#cleanUpForRestart,BasicContainer#
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (STORM-3311) Use Java 7 Files API for IO instead of the older API
[ https://issues.apache.org/jira/browse/STORM-3311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla closed STORM-3311. -- Resolution: Won't Fix We are in the process of migrating our issue tracking system to GitHub issues. This issue has been stale for the last 5 years, and STORM has evolved with many dependency updates since this issue was last updated. If the issue persists in the latest version of Storm, please feel free to reopen it or provide new context. Thank you very much! > Use Java 7 Files API for IO instead of the older API > > > Key: STORM-3311 > URL: https://issues.apache.org/jira/browse/STORM-3311 > Project: Apache Storm > Issue Type: Improvement >Affects Versions: 2.0.0 >Reporter: Stig Rohde Døssing >Assignee: Stig Rohde Døssing >Priority: Major > Labels: pull-request-available > Time Spent: 1h 40m > Remaining Estimate: 0h > > We should try to use the NIO Files API for file IO. The older file API causes > issues on Windows, since it doesn't set the FILE_SHARE_DELETE flag when > opening files. This causes Storm to be unable to delete files that have open > handles, which is unlike the behavior on Linux. This can cause e.g. > unnecessary supervisor crashes because one thread tries to delete a file that > is open in another. > For the same reason, we should get rid of uses of common-io FileUtils, and > get rid of uses of Guava's Files class that opens IO streams. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (STORM-172) Add hooks for creating shared resources among tasks
[ https://issues.apache.org/jira/browse/STORM-172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla closed STORM-172. - Resolution: Fixed We are in the process of migrating our issue tracking system to GitHub issues. This issue has been stale for the last 5 years, and STORM has evolved with many dependency updates since this issue was last updated. If the issue persists in the latest version of Storm, please feel free to reopen it or provide new context. Thank you very much! > Add hooks for creating shared resources among tasks > --- > > Key: STORM-172 > URL: https://issues.apache.org/jira/browse/STORM-172 > Project: Apache Storm > Issue Type: New Feature > Components: storm-core >Reporter: James Xu >Priority: Minor > > https://github.com/nathanmarz/storm/issues/240 > Building off of #155, the worker hook API should have a way to define shared > resources to be used by all tasks. These resources can then be cleaned up in > the worker hook's cleanup method. > -- > xumingming: @nathanmarz is setTaskData implemented for this? > -- > danehammer: I remember seeing several TODOs around this when I was working on > the worker lifecycle code. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (STORM-1382) Netty Client connection failure error message is too alarming
[
https://issues.apache.org/jira/browse/STORM-1382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Zowalla closed STORM-1382.
--
Resolution: Won't Fix
We are in the process of migrating our issue tracking system to GitHub issues.
This issue has been stale for the last 5 years, and STORM has evolved with many
dependency updates since this issue was last updated.
If the issue persists in the latest version of Storm, please feel free to
reopen it or provide new context. Thank you very much!
> Netty Client connection failure error message is too alarming
> -
>
> Key: STORM-1382
> URL: https://issues.apache.org/jira/browse/STORM-1382
> Project: Apache Storm
> Issue Type: Bug
> Components: storm-core
>Reporter: Paul Poulosky
>Priority: Major
>
> The error message printed when a netty-client cannot connect to another
> worker is worded in a way that our users are interpreting as a failure with
> storm.
> There are times, such as at topology launch when such messages are normal as
> not all of the workers have been launched on all of the supervisors yet.
> Other times, it is indicative of a failure (uncaught exception, OOM) on
> another worker, but the end user believes that this client is failing, due to
> the error message.
> eg:
> {noformat}
> 2015-12-03 12:28:53.338 b.s.m.n.Client [ERROR] connection attempt 10 to
> Netty-Client-host1.grid.myco.com/10.1.2.3:6710 failed:
> java.net.ConnectException: Connection refused:
> host1.grid.myco.com/10.1.2.3:6710
> {noformat}
> We should change the message to be more informative to our end users as to
> what happened, and it should not be an ERROR, but a Warning, as there are
> occasions when one would expect to see this.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (STORM-4064) Old code reference in the document
[ https://issues.apache.org/jira/browse/STORM-4064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17864126#comment-17864126 ] Richard Zowalla commented on STORM-4064: Feel free to provide a PR to improve the situation. > Old code reference in the document > -- > > Key: STORM-4064 > URL: https://issues.apache.org/jira/browse/STORM-4064 > Project: Apache Storm > Issue Type: Documentation >Affects Versions: 2.6.2 >Reporter: Gowtham >Priority: Minor > > In the Message Passing Implementation document, it refers to older version > codes > https://storm.apache.org/releases/2.6.2/Message-passing-implementation.html -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (STORM-4064) Old code reference in the document
[ https://issues.apache.org/jira/browse/STORM-4064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla updated STORM-4064: --- Priority: Minor (was: Major) > Old code reference in the document > -- > > Key: STORM-4064 > URL: https://issues.apache.org/jira/browse/STORM-4064 > Project: Apache Storm > Issue Type: Improvement >Affects Versions: 2.6.2 >Reporter: Gowtham >Priority: Minor > > In the Message Passing Implementation document, it refers to older version > codes > https://storm.apache.org/releases/2.6.2/Message-passing-implementation.html -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (STORM-4064) Old code reference in the document
[ https://issues.apache.org/jira/browse/STORM-4064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla updated STORM-4064: --- Issue Type: Documentation (was: Improvement) > Old code reference in the document > -- > > Key: STORM-4064 > URL: https://issues.apache.org/jira/browse/STORM-4064 > Project: Apache Storm > Issue Type: Documentation >Affects Versions: 2.6.2 >Reporter: Gowtham >Priority: Minor > > In the Message Passing Implementation document, it refers to older version > codes > https://storm.apache.org/releases/2.6.2/Message-passing-implementation.html -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (STORM-4066) Jetty 11.0.21
[ https://issues.apache.org/jira/browse/STORM-4066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla closed STORM-4066. -- Resolution: Fixed > Jetty 11.0.21 > - > > Key: STORM-4066 > URL: https://issues.apache.org/jira/browse/STORM-4066 > Project: Apache Storm > Issue Type: Dependency upgrade >Affects Versions: 2.6.2 >Reporter: Richard Zowalla >Assignee: Richard Zowalla >Priority: Major > Fix For: 2.6.3 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (STORM-4065) Dropwizard Metric 4.2.26
[ https://issues.apache.org/jira/browse/STORM-4065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla closed STORM-4065. -- Resolution: Fixed > Dropwizard Metric 4.2.26 > > > Key: STORM-4065 > URL: https://issues.apache.org/jira/browse/STORM-4065 > Project: Apache Storm > Issue Type: Dependency upgrade >Affects Versions: 2.6.2 >Reporter: Richard Zowalla >Assignee: Richard Zowalla >Priority: Major > Fix For: 2.6.3 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (STORM-4067) Jersey 3.1.7
[ https://issues.apache.org/jira/browse/STORM-4067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla closed STORM-4067. -- Resolution: Fixed > Jersey 3.1.7 > > > Key: STORM-4067 > URL: https://issues.apache.org/jira/browse/STORM-4067 > Project: Apache Storm > Issue Type: Dependency upgrade >Affects Versions: 2.6.2 >Reporter: Richard Zowalla >Assignee: Richard Zowalla >Priority: Major > Fix For: 2.6.3 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (STORM-3985) Upgrade dependencies to ones based on Jakarta EE APIs
[ https://issues.apache.org/jira/browse/STORM-3985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla closed STORM-3985. -- Resolution: Fixed > Upgrade dependencies to ones based on Jakarta EE APIs > - > > Key: STORM-3985 > URL: https://issues.apache.org/jira/browse/STORM-3985 > Project: Apache Storm > Issue Type: Dependency upgrade >Affects Versions: 2.6.2 >Reporter: Alexandre Vermeerbergen >Assignee: Richard Zowalla >Priority: Major > Fix For: 2.6.3 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (STORM-4066) Jetty 11.0.21
[ https://issues.apache.org/jira/browse/STORM-4066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla reassigned STORM-4066: -- Assignee: Richard Zowalla > Jetty 11.0.21 > - > > Key: STORM-4066 > URL: https://issues.apache.org/jira/browse/STORM-4066 > Project: Apache Storm > Issue Type: Dependency upgrade >Affects Versions: 2.6.2 >Reporter: Richard Zowalla >Assignee: Richard Zowalla >Priority: Major > Fix For: 2.6.3 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (STORM-4067) Jersey 3.1.7
Richard Zowalla created STORM-4067: -- Summary: Jersey 3.1.7 Key: STORM-4067 URL: https://issues.apache.org/jira/browse/STORM-4067 Project: Apache Storm Issue Type: Dependency upgrade Reporter: Richard Zowalla -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (STORM-4067) Jersey 3.1.7
[ https://issues.apache.org/jira/browse/STORM-4067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla updated STORM-4067: --- Fix Version/s: 2.6.3 > Jersey 3.1.7 > > > Key: STORM-4067 > URL: https://issues.apache.org/jira/browse/STORM-4067 > Project: Apache Storm > Issue Type: Dependency upgrade >Affects Versions: 2.6.2 >Reporter: Richard Zowalla >Assignee: Richard Zowalla >Priority: Major > Fix For: 2.6.3 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (STORM-4067) Jersey 3.1.7
[ https://issues.apache.org/jira/browse/STORM-4067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla reassigned STORM-4067: -- Assignee: Richard Zowalla > Jersey 3.1.7 > > > Key: STORM-4067 > URL: https://issues.apache.org/jira/browse/STORM-4067 > Project: Apache Storm > Issue Type: Dependency upgrade >Reporter: Richard Zowalla >Assignee: Richard Zowalla >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (STORM-4067) Jersey 3.1.7
[ https://issues.apache.org/jira/browse/STORM-4067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla updated STORM-4067: --- Affects Version/s: 2.6.2 > Jersey 3.1.7 > > > Key: STORM-4067 > URL: https://issues.apache.org/jira/browse/STORM-4067 > Project: Apache Storm > Issue Type: Dependency upgrade >Affects Versions: 2.6.2 >Reporter: Richard Zowalla >Assignee: Richard Zowalla >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (STORM-4066) Jetty 11.0.21
Richard Zowalla created STORM-4066: -- Summary: Jetty 11.0.21 Key: STORM-4066 URL: https://issues.apache.org/jira/browse/STORM-4066 Project: Apache Storm Issue Type: Dependency upgrade Affects Versions: 2.6.2 Reporter: Richard Zowalla Fix For: 2.6.3 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (STORM-3985) Upgrade dependencies to ones based on Jakarta EE APIs
[ https://issues.apache.org/jira/browse/STORM-3985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla updated STORM-3985: --- Fix Version/s: 2.6.3 > Upgrade dependencies to ones based on Jakarta EE APIs > - > > Key: STORM-3985 > URL: https://issues.apache.org/jira/browse/STORM-3985 > Project: Apache Storm > Issue Type: Dependency upgrade >Affects Versions: 2.6.2 >Reporter: Alexandre Vermeerbergen >Assignee: Richard Zowalla >Priority: Major > Fix For: 2.6.3 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (STORM-3985) Upgrade dependencies to ones based on Jakarta EE APIs
[ https://issues.apache.org/jira/browse/STORM-3985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla reassigned STORM-3985: -- Assignee: Richard Zowalla > Upgrade dependencies to ones based on Jakarta EE APIs > - > > Key: STORM-3985 > URL: https://issues.apache.org/jira/browse/STORM-3985 > Project: Apache Storm > Issue Type: Dependency upgrade >Affects Versions: 2.6.2 >Reporter: Alexandre Vermeerbergen >Assignee: Richard Zowalla >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (STORM-4065) Dropwizard Metric 4.2.26
[ https://issues.apache.org/jira/browse/STORM-4065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla reassigned STORM-4065: -- Assignee: Richard Zowalla > Dropwizard Metric 4.2.26 > > > Key: STORM-4065 > URL: https://issues.apache.org/jira/browse/STORM-4065 > Project: Apache Storm > Issue Type: Dependency upgrade >Affects Versions: 2.6.2 >Reporter: Richard Zowalla >Assignee: Richard Zowalla >Priority: Major > Fix For: 2.6.3 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (STORM-4065) Dropwizard Metric 4.2.26
Richard Zowalla created STORM-4065: -- Summary: Dropwizard Metric 4.2.26 Key: STORM-4065 URL: https://issues.apache.org/jira/browse/STORM-4065 Project: Apache Storm Issue Type: Dependency upgrade Affects Versions: 2.6.2 Reporter: Richard Zowalla Fix For: 2.6.3 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (STORM-4062) JSON Mini Dev 2.5.1
[ https://issues.apache.org/jira/browse/STORM-4062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla closed STORM-4062. -- Resolution: Fixed > JSON Mini Dev 2.5.1 > --- > > Key: STORM-4062 > URL: https://issues.apache.org/jira/browse/STORM-4062 > Project: Apache Storm > Issue Type: Dependency upgrade >Affects Versions: 2.6.2 >Reporter: Richard Zowalla >Assignee: Richard Zowalla >Priority: Major > Fix For: 2.6.3 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (STORM-4063) Curator 5.7.0
[ https://issues.apache.org/jira/browse/STORM-4063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla closed STORM-4063. -- Resolution: Fixed > Curator 5.7.0 > - > > Key: STORM-4063 > URL: https://issues.apache.org/jira/browse/STORM-4063 > Project: Apache Storm > Issue Type: Dependency upgrade >Affects Versions: 2.6.2 >Reporter: Richard Zowalla >Assignee: Richard Zowalla >Priority: Major > Fix For: 2.6.3 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (STORM-4061) Hadoop 3.4.0
[ https://issues.apache.org/jira/browse/STORM-4061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla closed STORM-4061. -- Resolution: Fixed > Hadoop 3.4.0 > > > Key: STORM-4061 > URL: https://issues.apache.org/jira/browse/STORM-4061 > Project: Apache Storm > Issue Type: Dependency upgrade >Affects Versions: 2.6.2 >Reporter: Richard Zowalla >Assignee: Richard Zowalla >Priority: Major > Fix For: 2.6.3 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (STORM-4063) Curator 5.7.0
Richard Zowalla created STORM-4063: -- Summary: Curator 5.7.0 Key: STORM-4063 URL: https://issues.apache.org/jira/browse/STORM-4063 Project: Apache Storm Issue Type: Dependency upgrade Affects Versions: 2.6.2 Reporter: Richard Zowalla Assignee: Richard Zowalla Fix For: 2.6.3 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (STORM-4061) Hadoop 3.4.0
Richard Zowalla created STORM-4061: -- Summary: Hadoop 3.4.0 Key: STORM-4061 URL: https://issues.apache.org/jira/browse/STORM-4061 Project: Apache Storm Issue Type: Dependency upgrade Affects Versions: 2.6.2 Reporter: Richard Zowalla Assignee: Richard Zowalla Fix For: 2.6.3 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (STORM-4062) JSON Mini Dev 2.5.1
Richard Zowalla created STORM-4062: -- Summary: JSON Mini Dev 2.5.1 Key: STORM-4062 URL: https://issues.apache.org/jira/browse/STORM-4062 Project: Apache Storm Issue Type: Dependency upgrade Affects Versions: 2.6.2 Reporter: Richard Zowalla Assignee: Richard Zowalla Fix For: 2.6.3 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (STORM-3805) change retrying blob update log message to WARN
[ https://issues.apache.org/jira/browse/STORM-3805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla closed STORM-3805. -- Fix Version/s: 2.6.0 Resolution: Fixed > change retrying blob update log message to WARN > --- > > Key: STORM-3805 > URL: https://issues.apache.org/jira/browse/STORM-3805 > Project: Apache Storm > Issue Type: Improvement > Components: blobstore >Reporter: Nikhil Singh >Assignee: Bipin Prasad >Priority: Minor > Fix For: 2.6.0 > > Time Spent: 1.5h > Remaining Estimate: 0h > > We should be able to search supervisor logs for actual errors. This seems > like it should be a WARN: > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (STORM-2287) DemoTest fails intermittently on 1.x-branch & master branch
[ https://issues.apache.org/jira/browse/STORM-2287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla closed STORM-2287. -- Resolution: Won't Fix > DemoTest fails intermittently on 1.x-branch & master branch > --- > > Key: STORM-2287 > URL: https://issues.apache.org/jira/browse/STORM-2287 > Project: Apache Storm > Issue Type: Bug > Components: integration-test >Affects Versions: 1.x >Reporter: Raghav Kumar Gautam >Assignee: Raghav Kumar Gautam >Priority: Critical > > See the following runs: > https://travis-ci.org/apache/storm/builds/191507849 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (STORM-3308) o.a.s.b.BlobStoreUtils [ERROR] Could not update the blob with key
[
https://issues.apache.org/jira/browse/STORM-3308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Zowalla closed STORM-3308.
--
Resolution: Won't Fix
Storm 1.x isn't maintained anymore.
> o.a.s.b.BlobStoreUtils [ERROR] Could not update the blob with key
> -
>
> Key: STORM-3308
> URL: https://issues.apache.org/jira/browse/STORM-3308
> Project: Apache Storm
> Issue Type: Bug
> Components: blobstore, storm-core
>Affects Versions: 1.0.6
>Reporter: Pydi Prasanna Sai Kamanuru
>Priority: Minor
>
> Related to issue STORM-2736
> We run a single instance of storm-nimbus (Non HA). Due to issues with
> connections issues with zookeeper, the ephemeral child nodes at
> /storm.104/blobstore/key/ were lost that was created by the instance. Nimbus
> constantly logs the following line which was fixed in the issue mentioned
> above -
> {code:java}
> o.a.s.b.BlobStoreUtils [ERROR] Could not update the blob with key
> {code}
> But, Shouldn't nimbus automatically create the children with
> hostname:port-sequencenumber automatically if it is up and running ? In my
> case, nimbus did not crash but the ephemeral nodes( the children in the case)
> vanished when the connection was reset between nimbus and zookeeper. I don't
> see any code path that creates the children if they are missing in the
> /blobstore zk path.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (STORM-1992) Deploy multilang-javascript code as node package
[ https://issues.apache.org/jira/browse/STORM-1992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla closed STORM-1992. -- Resolution: Won't Fix Storm 1.x isn't maintained anymore. > Deploy multilang-javascript code as node package > > > Key: STORM-1992 > URL: https://issues.apache.org/jira/browse/STORM-1992 > Project: Apache Storm > Issue Type: New Feature > Components: storm-multilang >Affects Versions: 1.0.1 >Reporter: Marc Zbyszynski >Priority: Minor > Labels: pull-request-available > Time Spent: 20m > Remaining Estimate: 0h > > Now that storm includes Flux, it is easier than ever to deploy a topology > with javascript components. If the Bolt and Spout base classes defined in > storm/multi-lang/javascript were available in a node.js package on > https://www.npmjs.com/ it would allow node.js storm users to take advantage > of node's built in package manager to develop their own bolts and spouts. > It would be relatively trivial to add some maven tasks to > storm/multi-lang/javascript/pom.xml to take the storm.js resource and package > it in a node module and submit it to npm. > This could be added to the pom as a separate profile so it wouldn't impact > the normal storm build process. > This integration will also make it easier to add unit tests for storm.js > For additional background see this discussion: > http://mail-archives.apache.org/mod_mbox/storm-dev/201607.mbox/%3CCAD8EKPHc6O1LCnoQUUoYoDuMQ3uSaNpD5gR4onK%2B0EL5_qcZ3Q%40mail.gmail.com%3E > If this sounds like a worthwhile addition to the project I would be happy to > submit a PR. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (STORM-1015) Store Kafka offsets with Kafka's consumer offset management api
[ https://issues.apache.org/jira/browse/STORM-1015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla closed STORM-1015. -- Resolution: Won't Fix Storm 1.x isn't maintained anymore. > Store Kafka offsets with Kafka's consumer offset management api > --- > > Key: STORM-1015 > URL: https://issues.apache.org/jira/browse/STORM-1015 > Project: Apache Storm > Issue Type: Improvement > Components: storm-kafka >Affects Versions: 1.0.0 >Reporter: Hang Sun >Assignee: He Sun >Priority: Minor > Labels: consumer, kafka, offset, pull-request-available > Original Estimate: 72h > Time Spent: 10m > Remaining Estimate: 71h 50m > > Current Kafka spout stores the offsets (and some other states) inside ZK with > its proprietary format. This does not work well with other Kafka offset > monitoring tools such as Burrow, KafkaOffsetMonitor etc. In addition, the > performance does not scale well compared with offsets managed by Kafka's > built-in offset management api. I have added a new option for Kafka to store > the same data using Kafka's built-in offset management capability. The change > is completely backward compatible with the current ZK storage option. The > feature can be turned on by a single configuration option. Hope this will > help people who wants to explore the option of using Kafka's built-in offset > management api. > References: > https://cwiki.apache.org/confluence/display/KAFKA/Committing+and+fetching+consumer+offsets+in+Kafka > https://cwiki.apache.org/confluence/display/KAFKA/A+Guide+To+The+Kafka+Protocol#AGuideToTheKafkaProtocol-OffsetCommit/FetchAPI > -thanks -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (STORM-3085) Expose Ability to Disable CORS for Storm UI Rest API
[
https://issues.apache.org/jira/browse/STORM-3085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Zowalla closed STORM-3085.
--
Resolution: Won't Fix
{color:#FF}Storm 1.x isn't maintained anymore.{color}
> Expose Ability to Disable CORS for Storm UI Rest API
>
>
> Key: STORM-3085
> URL: https://issues.apache.org/jira/browse/STORM-3085
> Project: Apache Storm
> Issue Type: Improvement
>Affects Versions: 1.2.1
>Reporter: Brian Goerlitz
>Priority: Minor
> Labels: newbie
>
> STORM-1960 enabled CORS by default in Storm UI Rest API. Some users may need
> to disable CORS to comply with security restrictions, so it should be
> possible to disable this.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (STORM-3483) Backpressure turns on after topology is idle for 160 minutes
[ https://issues.apache.org/jira/browse/STORM-3483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla closed STORM-3483. -- Resolution: Won't Fix Storm 1.x isn't maintained anymore. > Backpressure turns on after topology is idle for 160 minutes > > > Key: STORM-3483 > URL: https://issues.apache.org/jira/browse/STORM-3483 > Project: Apache Storm > Issue Type: Bug > Components: storm-core >Affects Versions: 1.2.2 >Reporter: Raj Choudhury >Priority: Minor > Attachments: image-2019-08-08-15-59-25-655.png, > image-2019-08-08-16-02-09-750.png, image-2019-08-08-17-32-10-241.png > > > Storm version used 1.2.2 > While testing a topology we noticed that backpressure was being triggered on > an idle topology, without any data going through the system for roughly 160 > minutes. However once we starting putting data through the system, > backpressure behaved as normal and is off. > We have storm metrics logger to log the disruptor queue sizes, and during > this test we can see the receive queue population is 0 when backpressure > kicks in. > > We confirmed this by turning debug logs on for storm. > !image-2019-08-08-17-32-10-241.png! > > In an idle system where backpressure occurs... > !image-2019-08-08-16-02-09-750.png! > > > What a normal system with data going through looks like... > !image-2019-08-08-15-59-25-655.png! > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (STORM-2611) a batched kafkaspout with offsets in zookeeper
[ https://issues.apache.org/jira/browse/STORM-2611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla closed STORM-2611. -- Resolution: Won't Fix Storm 1.x isn't maintained anymore. > a batched kafkaspout with offsets in zookeeper > -- > > Key: STORM-2611 > URL: https://issues.apache.org/jira/browse/STORM-2611 > Project: Apache Storm > Issue Type: Improvement > Components: examples >Affects Versions: 1.1.0 > Environment: Kafka, storm, zookeeper >Reporter: lilizhi >Priority: Trivial > Labels: features, newbie > Original Estimate: 168h > Remaining Estimate: 168h > > There are some issues with org.apache.storm.kafka.spout.KafkaSpout. > 1. When the topology is running in multi workers in different supervisors, it > is very often to trigger kafkaspout rebalance. And so the streaming is not > stable. And it will cause massive retransmission of lost packets. > 2. When max.uncommitted.offsets is less than 20 (for limited flow), > sometimes there is deadlock. The phenomenon is the heartbeat between spout > and kafka can not be performed. > 3. When the data is from storm to hbase, batch is used to improve writing > productivity. So using batch from spout to bolt is better for special scene. > 4. So a batched kafkaspout and bolt with offsets in zookeeper will be > valuable. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (STORM-985) provide .editorconfig with git pre-commit hooks to check code style before commit
[
https://issues.apache.org/jira/browse/STORM-985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Zowalla closed STORM-985.
-
Resolution: Won't Fix
{color:#FF}Storm 1.x isn't maintained anymore.{color}
> provide .editorconfig with git pre-commit hooks to check code style before
> commit
> --
>
> Key: STORM-985
> URL: https://issues.apache.org/jira/browse/STORM-985
> Project: Apache Storm
> Issue Type: Improvement
> Components: storm-core
>Affects Versions: 1.0.0
>Reporter: caofangkun
>Assignee: caofangkun
>Priority: Trivial
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (STORM-3531) Kafka Spouts Lag error when worker die
[
https://issues.apache.org/jira/browse/STORM-3531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Zowalla closed STORM-3531.
--
Resolution: Won't Fix
Storm 1.x isn't maintained anymore.
> Kafka Spouts Lag error when worker die
> --
>
> Key: STORM-3531
> URL: https://issues.apache.org/jira/browse/STORM-3531
> Project: Apache Storm
> Issue Type: Bug
> Components: storm-kafka-client
>Affects Versions: 1.2.3
> Environment: Linux
>Reporter: khiemvk
>Priority: Major
>
> I deploy topology on cluster (3 Supervisors) with 3 workers, 3 Spouts read
> topic kafka with 3 partitions.
> Step 1: I kill worker1 on Supervisor1
> Step 2: Worker1 automatic running again.
> Step 3: Kafka spout of worker1 register partition 1 and read not lag. Worker2
> and worker3 error lag kafka, not continue read and commit offset
> Log worker:
> {color:#FF}Not polling on partition [TEST-0]. It has [250] uncommitted
> offsets, which exceeds the limit of [250]{color}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (STORM-2437) LocalCluster in Unit Test crash the VM
[ https://issues.apache.org/jira/browse/STORM-2437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla closed STORM-2437. -- Resolution: Won't Fix Storm 1.x isn't maintained anymore. > LocalCluster in Unit Test crash the VM > -- > > Key: STORM-2437 > URL: https://issues.apache.org/jira/browse/STORM-2437 > Project: Apache Storm > Issue Type: Improvement > Components: storm-core >Affects Versions: 1.0.3 > Environment: Linux CentOs7 > Eclipse Mars 2 > Maven 3.3.9 with recent version of surefire, in forkCount=1 reuseFork=false >Reporter: Antoine Tran >Priority: Minor > > When unit testing Storm, we use LocalCluster. There is nothing to say when > the Unit Test is working, the Unit Test ends gracefully. > However, when there are RuntimeException, for instance in the prepare > functions, Storm crash and calls in Utils.mkSuicideFn, which calls > Runtime.getRuntime().exit. So the VM crash and this is contradictory to Maven > Surefire design > (http://maven.apache.org/surefire/maven-surefire-plugin/faq.html#vm-termination). > I searched many ways to either prevent Storm from exiting (using > SecurityManager), or make Unit Test accept the crash of the forked process. > If the Unit Test s VM crash, surefire will be unable to continue. My > suggestion is to allow a configuration of LocalCluster that avoids > System.exit, but just kills the topology (and closes all ressources if > possible, but in the short term, this is not really important in a forked > process). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (STORM-1209) Generalize StringMultiSchemeWithTopic
[ https://issues.apache.org/jira/browse/STORM-1209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla closed STORM-1209. -- Resolution: Won't Fix Storm 1.x isn't maintained anymore. > Generalize StringMultiSchemeWithTopic > - > > Key: STORM-1209 > URL: https://issues.apache.org/jira/browse/STORM-1209 > Project: Apache Storm > Issue Type: Improvement > Components: storm-kafka >Affects Versions: 1.0.0 >Reporter: Paulo Costa >Assignee: Paulo Costa >Priority: Trivial > Original Estimate: 4h > Time Spent: 20m > Remaining Estimate: 3h 40m > > STORM-817 allows a KafkaSpout to listen to multiple topics. > In this scenario, it makes sense to append the kafka topic to the tuples sent > to storm. > This is partially implemented as `StringMultiSchemeWithTopic`. The idea is > great, but not flexible enough, since it only works for Strings. > This should be generalized to work with any Scheme. > My proposed solution is available on https://github.com/apache/storm/pull/883 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (STORM-3346) ClassNotFoundException: clojure.lang.persistentList whiile submitting topology to local cluster in storm
[ https://issues.apache.org/jira/browse/STORM-3346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla closed STORM-3346. -- Resolution: Won't Fix Storm 1.x isn't maintained anymore. > ClassNotFoundException: clojure.lang.persistentList whiile submitting > topology to local cluster in storm > > > Key: STORM-3346 > URL: https://issues.apache.org/jira/browse/STORM-3346 > Project: Apache Storm > Issue Type: Bug >Affects Versions: 1.0.6, 1.2.1, 1.2.2 > Environment: java version "1.8.0_131" > Apache Storm 1.2.1 >Reporter: Tanuj Kulshrestha >Priority: Minor > > Getting below exceptions while submitting storm topology to local cluster > Exception in thread "main" java.lang.ExceptionInInitializerError > at clojure.lang.Namespace.(Namespace.java:34) > at clojure.lang.Namespace.findOrCreate(Namespace.java:176) > at clojure.lang.Var.internPrivate(Var.java:156) > at org.apache.storm.LocalCluster.(Unknown Source) > at KafkaCEPTopology.main(KafkaCEPTopology.java:53) > Caused by: Syntax error compiling . at (clojure/core.clj:20:8). > at clojure.lang.Compiler.analyzeSeq(Compiler.java:7114) > at clojure.lang.Compiler.analyze(Compiler.java:6789) > at clojure.lang.Compiler.access$300(Compiler.java:38) > at clojure.lang.Compiler$DefExpr$Parser.parse(Compiler.java:596) > at clojure.lang.Compiler.analyzeSeq(Compiler.java:7106) > at clojure.lang.Compiler.analyze(Compiler.java:6789) > at clojure.lang.Compiler.analyze(Compiler.java:6745) > at clojure.lang.Compiler.eval(Compiler.java:7180) > at clojure.lang.Compiler.load(Compiler.java:7635) > at clojure.lang.RT.loadResourceScript(RT.java:381) > at clojure.lang.RT.loadResourceScript(RT.java:372) > at clojure.lang.RT.load(RT.java:463) > at clojure.lang.RT.load(RT.java:428) > at clojure.lang.RT.doInit(RT.java:471) > at clojure.lang.RT.(RT.java:338) > ... 5 more > Caused by: java.lang.ClassNotFoundException: clojure.lang.PersistentList > at java.net.URLClassLoader.findClass(URLClassLoader.java:381) > at clojure.lang.DynamicClassLoader.findClass(DynamicClassLoader.java:69) > at java.lang.ClassLoader.loadClass(ClassLoader.java:424) > at clojure.lang.DynamicClassLoader.loadClass(DynamicClassLoader.java:77) > at java.lang.ClassLoader.loadClass(ClassLoader.java:357) > at java.lang.Class.forName0(Native Method) > at java.lang.Class.forName(Class.java:348) > at clojure.lang.RT.classForName(RT.java:2207) > at clojure.lang.RT.classForNameNonLoading(RT.java:2220) > at clojure.lang.Compiler$HostExpr.maybeClass(Compiler.java:1041) > at clojure.lang.Compiler$HostExpr$Parser.parse(Compiler.java:982) > at clojure.lang.Compiler.analyzeSeq(Compiler.java:7106) > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (STORM-3597) workers not getting killed after topology gets killed
[ https://issues.apache.org/jira/browse/STORM-3597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla resolved STORM-3597. Resolution: Won't Fix Storm 1.x isn't maintained anymore. > workers not getting killed after topology gets killed > - > > Key: STORM-3597 > URL: https://issues.apache.org/jira/browse/STORM-3597 > Project: Apache Storm > Issue Type: Bug >Affects Versions: 1.2.2 >Reporter: Saurav Suman >Priority: Major > Attachments: image-2020-03-11-13-45-59-811.png, > image-2020-03-11-13-47-41-005.png > > > Hi Team, > I am using apache storm version 1.2.2. > Topology was not getting killed from the storm UI as it was throwing > exception - " Error while communicating with Nimbus" , Then after killing it > from the storm cli , it says KILLED both at UI and cli but doesn't goes off > and the workers are still running on the supervisors. Please advise on how to > kill and remove this topology. > > !image-2020-03-11-13-47-41-005.png! > !image-2020-03-11-13-45-59-811.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (STORM-3686) o.a.s.t.s.AbstractNonblockingServer$FrameBuffer pool-14-thread-10 [ERROR] Unexpected throwable while invoking! java.lang.NullPointerException: null
[ https://issues.apache.org/jira/browse/STORM-3686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla closed STORM-3686. -- Resolution: Won't Fix Storm 1.x isn't maintained anymore. > o.a.s.t.s.AbstractNonblockingServer$FrameBuffer pool-14-thread-10 [ERROR] > Unexpected throwable while invoking! java.lang.NullPointerException: null > --- > > Key: STORM-3686 > URL: https://issues.apache.org/jira/browse/STORM-3686 > Project: Apache Storm > Issue Type: Bug >Affects Versions: 1.2.2 > Environment: PROD >Reporter: Saurav Suman >Priority: Blocker > Attachments: Storm_ui.log, storm_nimbus.log > > > Hi Team, > > Very often I am getting below error in storm nimbus and after that the storm > UI loads only with some content. > > 2020-08-05 02:45:01.802 o.a.s.t.s.AbstractNonblockingServer$FrameBuffer > pool-14-thread-10 [ERROR] Unexpected throwable while invoking! > java.lang.NullPointerException: null > > Attached the storm nimbus and ui error from their logs. > > Please advise. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (STORM-3698) AbstractHdfsBolt does not sync Writers that are purged
[ https://issues.apache.org/jira/browse/STORM-3698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla closed STORM-3698. -- Resolution: Won't Fix Storm 1.x isn't maintained anymore. > AbstractHdfsBolt does not sync Writers that are purged > -- > > Key: STORM-3698 > URL: https://issues.apache.org/jira/browse/STORM-3698 > Project: Apache Storm > Issue Type: Bug > Components: storm-hdfs >Affects Versions: 1.2.2 >Reporter: Max Schmidt >Priority: Critical > > We just discovered when using a SequenceFileBolt (although it might happen > with other implementations as well) that the writers it uses, held in the map > AbstractHdfsBolt.writers are not closed/synced when they are removed from the > map by the removeEldestEntry method. > This leads to data loss. > Can be reproduced by creating a SequenceFileBolt.withMaxOpenFiles(1) and > writing to just two different files. > One will have a size of zero, the other has the data in it. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (STORM-3842) upgrade elasticsearch due to cve
[ https://issues.apache.org/jira/browse/STORM-3842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla resolved STORM-3842. Fix Version/s: 2.6.1 Resolution: Fixed > upgrade elasticsearch due to cve > > > Key: STORM-3842 > URL: https://issues.apache.org/jira/browse/STORM-3842 > Project: Apache Storm > Issue Type: Improvement >Reporter: PJ Fanning >Priority: Major > Fix For: 2.6.1 > > > [https://github.com/advisories/GHSA-3393-hvrj-w7v3] > used in elasticsearch example -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (STORM-3852) Storm 1.2.4 Vulnerability in Grype Scan
[ https://issues.apache.org/jira/browse/STORM-3852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla closed STORM-3852. -- Resolution: Won't Fix Storm 1.x isn't maintained anymore. > Storm 1.2.4 Vulnerability in Grype Scan > --- > > Key: STORM-3852 > URL: https://issues.apache.org/jira/browse/STORM-3852 > Project: Apache Storm > Issue Type: Improvement >Affects Versions: 1.2.4 >Reporter: Indranil Roy Chowdhury >Priority: Major > Attachments: Storm 1.2.4 VA Analysis.xls > > > [ Grype|https://github.com/anchore/grype] scan done on Storm 1.2.4 > distribution identifies several vulnerabilities due dependent jars of several > modules. Please refer to attached xls workbook for a detailed listing. > Summary of all CVEs are as below. Mitigating critical and high > vulnerabilities are much needed for production deployment of storm. Please > investigate and advise how the critical and high defects can be addressed at > minimum. > ||Severity||Count|| > |Critical|63| > |High|122| > |Medium|43| > |Low|7| > *NOTE* : Over 90% of reported issues are originating from Storm external > folder artifacts. Without considering artifacts in external folder the > reported summary is as below. > ||Severity||Count|| > |Critical|14| > |High|31| > |Medium|24| > |Low|4| > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (STORM-3985) Upgrade dependencies to ones based on Jakarta EE APIs
[ https://issues.apache.org/jira/browse/STORM-3985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla updated STORM-3985: --- Affects Version/s: 2.6.2 > Upgrade dependencies to ones based on Jakarta EE APIs > - > > Key: STORM-3985 > URL: https://issues.apache.org/jira/browse/STORM-3985 > Project: Apache Storm > Issue Type: Dependency upgrade >Affects Versions: 2.6.2 >Reporter: Alexandre Vermeerbergen >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (STORM-4002) Security Vulnerability - Action Required: “Incorrect Permission Assignment for Critical Resource” vulnerability in some components of org.apache.storm
[
https://issues.apache.org/jira/browse/STORM-4002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Zowalla closed STORM-4002.
--
Resolution: Won't Fix
Storm 1.x isn't maintained anymore.
> Security Vulnerability - Action Required: “Incorrect Permission Assignment
> for Critical Resource” vulnerability in some components of org.apache.storm
> ---
>
> Key: STORM-4002
> URL: https://issues.apache.org/jira/browse/STORM-4002
> Project: Apache Storm
> Issue Type: Bug
> Components: storm-kafka, storm-starter
>Affects Versions: 1.1.0, 1.1.1, 1.2.0, 1.1.2, 1.2.1, 1.1.3, 1.2.2
>Reporter: Yiheng Cao
>Priority: Major
>
> I think the method
> org.apache.hadoop.mapreduce.filecache.ClientDistributedCacheManager.checkPermissionOfOther(FileSystem
> fs, Path path, FsAction action, Map statCache) may have an
> “Incorrect Permission Assignment for Critical Resource”vulnerability which is
> vulnerable in in some components of org.apache.storm. It shares similarities
> to a recent CVE disclosure _CVE-2017-3166_ in the project _"apache/hadoop"_
> project. The influencing components are listed below:
> # org.apache.storm:storm-kafka-examples in the versions between 1.1.0 and
> 1.2.4.
> # org.apache.storm:storm-starter in the versions of 1.1.2-1.1.3 and
> 1.2.0-1.2.2
> The source vulnerability information is as follows:
> !https://mail.google.com/mail/u/0?ui=2=35947afd70=0.1=msg-f:1782522681557497681=18bccaef464fb751=fimg=ip=s0-l75-ft=ANGjdJ_bBS_0CMiL9kNUgnr95IJelNJAQJp906nnAonpFswrxMbSt1EVV1S2q6kq_ur-YE-1H49gOCjMGqFYtm5xBOS_EBOZci8ukIw2Hn8kM-9OIKVIxXrlhcRm6LA=emb=ii_lmt56kbv0|width=1,height=1!!https://mail.google.com/mail/u/0?ui=2=35947afd70=0.2=msg-f:1782522681557497681=18bccaef464fb751=fimg=ip=s0-l75-ft=ANGjdJ-8wPNUdQ35WBKaadck2X1lP34blTQ_qiyhu5T7l0G8T4cboSCiFNgfxaCQZZsK-Pm3ebzj4JSWBs558OxWHJPM1uJqKlMvPMhpx9J0TiojhC85DNqeLu3dr2Q=emb=ii_lmt6415i0|width=1,height=1!!https://mail.google.com/mail/u/0?ui=2=35947afd70=0.0.1=msg-f:1782522681557497681=18bccaef464fb751=fimg=ip=s0-l75-ft=ANGjdJ9XERxykP1zaB9Codaz3lisQ9gKwLHXnEIHP4p4oUcINmdFEWTJAWeDMfayncBsWIBj_kc2cAKHx4c7InMtKL98nDb2Dnt3TpfGLQCcJhdFsSBhemVA14CI0rA=emb=ii_loxzzieb0|width=1,height=1!
> *Vulnerability Detail:*
> *CVE Identifier:* CVE-2017-3166
> {*}Description{*}: In Apache Hadoop versions 2.6.1 to 2.6.5, 2.7.0 to 2.7.3,
> and 3.0.0-alpha1, if a file in an encryption zone with access permissions
> that make it world readable is localized via YARN's localization mechanism,
> that file will be stored in a world-readable location and can be shared
> freely with any application that requests to localize that file.
> *Reference:*[ |http://goog_608275719/]
> [https://nvd.nist.gov/vuln/detail/CVE-2017-3166]
> {*}Patch{*}:
> [https://github.com/apache/hadoop/commit/a47d8283b136aab5b9fa4c18e6f51fa799d91a29]
> *Vulnerability Description:* The vulnerability is present in the class
> org.apache.hadoop.mapreduce.filecache.ClientDistributedCacheManager of
> method checkPermissionOfOther(FileSystem fs, Path path, FsAction action,
> Map statCache) , which is responsible for checking the
> permissions of other files in the distributed cache.. {*}But t{*}{*}he check
> snippet is similar to the vulnerable snippet for CVE-2017-3166{*} and may
> have the same consequence as CVE-2017-3166: {*}a file in an encryption zone
> with access permissions will be stored in a world-readable location and can
> be freely shared with any application that requests the file to be
> localized{*}. Therefore, maybe you need to fix the vulnerability with much
> the same fix code as the CVE-2017-3166 patch.
> Considering the potential risks it may have, I am willing to cooperate
> with you to verify, address, and report the identified vulnerability promptly
> through responsible means. If you require any further information or
> assistance, please do not hesitate to reach out to me. Thank you and look
> forward to hearing from you soon.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (STORM-4057) Fix Worker Termination in K8S with Security Context
[ https://issues.apache.org/jira/browse/STORM-4057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla closed STORM-4057. -- > Fix Worker Termination in K8S with Security Context > --- > > Key: STORM-4057 > URL: https://issues.apache.org/jira/browse/STORM-4057 > Project: Apache Storm > Issue Type: Bug >Affects Versions: 2.6.1 >Reporter: Richard Zowalla >Priority: Major > Fix For: 2.6.3 > > Time Spent: 50m > Remaining Estimate: 0h > > https://lists.apache.org/thread/p79msxdkpzt3d57ycf1cpl8gn3j6tqkg -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Reopened] (STORM-4057) Fix Worker Termination in K8S with Security Context
[ https://issues.apache.org/jira/browse/STORM-4057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla reopened STORM-4057: > Fix Worker Termination in K8S with Security Context > --- > > Key: STORM-4057 > URL: https://issues.apache.org/jira/browse/STORM-4057 > Project: Apache Storm > Issue Type: Bug >Affects Versions: 2.6.1 >Reporter: Richard Zowalla >Priority: Major > Fix For: 2.6.2 > > Time Spent: 50m > Remaining Estimate: 0h > > https://lists.apache.org/thread/p79msxdkpzt3d57ycf1cpl8gn3j6tqkg -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (STORM-4057) Fix Worker Termination in K8S with Security Context
[ https://issues.apache.org/jira/browse/STORM-4057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla resolved STORM-4057. Resolution: Fixed > Fix Worker Termination in K8S with Security Context > --- > > Key: STORM-4057 > URL: https://issues.apache.org/jira/browse/STORM-4057 > Project: Apache Storm > Issue Type: Bug >Affects Versions: 2.6.1 >Reporter: Richard Zowalla >Priority: Major > Fix For: 2.6.3 > > Time Spent: 50m > Remaining Estimate: 0h > > https://lists.apache.org/thread/p79msxdkpzt3d57ycf1cpl8gn3j6tqkg -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (STORM-4057) Fix Worker Termination in K8S with Security Context
[ https://issues.apache.org/jira/browse/STORM-4057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla updated STORM-4057: --- Fix Version/s: 2.6.3 (was: 2.6.2) > Fix Worker Termination in K8S with Security Context > --- > > Key: STORM-4057 > URL: https://issues.apache.org/jira/browse/STORM-4057 > Project: Apache Storm > Issue Type: Bug >Affects Versions: 2.6.1 >Reporter: Richard Zowalla >Priority: Major > Fix For: 2.6.3 > > Time Spent: 50m > Remaining Estimate: 0h > > https://lists.apache.org/thread/p79msxdkpzt3d57ycf1cpl8gn3j6tqkg -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (STORM-4057) Fix Worker Termination in K8S with Security Context
[ https://issues.apache.org/jira/browse/STORM-4057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla resolved STORM-4057. Resolution: Fixed > Fix Worker Termination in K8S with Security Context > --- > > Key: STORM-4057 > URL: https://issues.apache.org/jira/browse/STORM-4057 > Project: Apache Storm > Issue Type: Bug >Affects Versions: 2.6.1 >Reporter: Richard Zowalla >Priority: Major > Fix For: 2.6.2 > > Time Spent: 50m > Remaining Estimate: 0h > > https://lists.apache.org/thread/p79msxdkpzt3d57ycf1cpl8gn3j6tqkg -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (STORM-4058) Provide ClusterMetrics via a Prometheus Preparable Reporter
[ https://issues.apache.org/jira/browse/STORM-4058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla closed STORM-4058. -- Fix Version/s: 2.7.0 Resolution: Fixed > Provide ClusterMetrics via a Prometheus Preparable Reporter > --- > > Key: STORM-4058 > URL: https://issues.apache.org/jira/browse/STORM-4058 > Project: Apache Storm > Issue Type: New Feature >Reporter: Richard Zowalla >Assignee: Richard Zowalla >Priority: Major > Fix For: 2.7.0, 2.6.3 > > Time Spent: 0.5h > Remaining Estimate: 0h > > as the title says. Prepare basic metrics via a pushgateway client for > prometheus -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (STORM-4059) Provide Topology / Other Metrics via a Prometheus Preparable Reporter
Richard Zowalla created STORM-4059: -- Summary: Provide Topology / Other Metrics via a Prometheus Preparable Reporter Key: STORM-4059 URL: https://issues.apache.org/jira/browse/STORM-4059 Project: Apache Storm Issue Type: New Feature Reporter: Richard Zowalla Fix For: 2.7.0, 2.6.3 as the title says -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (STORM-4058) Provide ClusterMetrics via a Prometheus Preparable Reporter
Richard Zowalla created STORM-4058: -- Summary: Provide ClusterMetrics via a Prometheus Preparable Reporter Key: STORM-4058 URL: https://issues.apache.org/jira/browse/STORM-4058 Project: Apache Storm Issue Type: New Feature Reporter: Richard Zowalla Assignee: Richard Zowalla Fix For: 2.6.3 as the title says. Prepare basic metrics via a pushgateway client for prometheus -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (STORM-4057) Fix Worker Termination in K8S with Security Context
Richard Zowalla created STORM-4057: -- Summary: Fix Worker Termination in K8S with Security Context Key: STORM-4057 URL: https://issues.apache.org/jira/browse/STORM-4057 Project: Apache Storm Issue Type: Bug Affects Versions: 2.6.1 Reporter: Richard Zowalla Fix For: 2.6.2 https://lists.apache.org/thread/p79msxdkpzt3d57ycf1cpl8gn3j6tqkg -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (STORM-3768) Zero Values for Assigned Mem (MB) in Topology Summary and Used Mem (MB) in Supervisor Summary
[ https://issues.apache.org/jira/browse/STORM-3768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17848910#comment-17848910 ] Richard Zowalla commented on STORM-3768: Is this still an issue? Have you tried 2.6.2 ? > Zero Values for Assigned Mem (MB) in Topology Summary and Used Mem (MB) in > Supervisor Summary > - > > Key: STORM-3768 > URL: https://issues.apache.org/jira/browse/STORM-3768 > Project: Apache Storm > Issue Type: Bug > Components: storm-ui >Affects Versions: 2.3.0 > Environment: Linux storm 4.9.0-15-amd64 #1 SMP Debian 4.9.258-1 > (2021-03-08) x86_64 > OpenJDK 64-Bit Server VM (build 13.0.2+8, mixed mode, sharing) > Python 2.7.13 / Python3 3.5.3 >Reporter: Jonas Krauß >Priority: Major > Attachments: supervisor_zero_values_overview.jpg, > topology_values_overview.jpg, worker_values_topology.jpg, > zero_value_topology.jpg > > > We have recently built storm 2.3.0-SNAPSHOT from git with commit hash > 4a1eea700766da2f175ac7eaba6064f0d7f0ff03 because we needed the bugfix in > STORM-3652. > It seems in this built information about the sum of the used memory is lost > (it was working before in 2.2.0, release version). Individual > topologies/components still get their memory assignment displayed, but the > total is missing. This affects the root view (*index.html*) of the UI, where > information is missing in the *supervisor section* (displayed value for used > mem is zero), as well as the topology view (*topology.html*, displayed value > for assigned mem in *topology summary* is zero). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (STORM-4037) confluent maven resolver may not be necessary any more
[ https://issues.apache.org/jira/browse/STORM-4037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla resolved STORM-4037. Fix Version/s: 2.6.2 Resolution: Fixed > confluent maven resolver may not be necessary any more > -- > > Key: STORM-4037 > URL: https://issues.apache.org/jira/browse/STORM-4037 > Project: Apache Storm > Issue Type: Bug >Reporter: PJ Fanning >Priority: Major > Fix For: 2.6.2 > > > After https://github.com/apache/storm/pull/3627, the repository ref at > https://github.com/apache/storm/blob/d8ab31aa5c296d018c783cb159e1ccaf288ecc1c/external/storm-hdfs/pom.xml#L41 > may not be necessary. > It is best to only use non standard maven repos when absolutely necessary. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (STORM-4056) Build with -Pnative on MacOS
Richard Zowalla created STORM-4056: -- Summary: Build with -Pnative on MacOS Key: STORM-4056 URL: https://issues.apache.org/jira/browse/STORM-4056 Project: Apache Storm Issue Type: Dependency upgrade Affects Versions: 2.6.2 Reporter: Richard Zowalla Building with macOS is currently not supported if -Pnative is added to the list of profiles. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (STORM-4055) ConcurrentModificationException on KafkaConsumer when running topology with Metrics Reporters
[
https://issues.apache.org/jira/browse/STORM-4055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17843001#comment-17843001
]
Richard Zowalla commented on STORM-4055:
Thanks for the report. Since you have already dived into the code, would you be
willing to provide a PR to fix ?
> ConcurrentModificationException on KafkaConsumer when running topology with
> Metrics Reporters
> -
>
> Key: STORM-4055
> URL: https://issues.apache.org/jira/browse/STORM-4055
> Project: Apache Storm
> Issue Type: Bug
> Components: storm-kafka-client
>Affects Versions: 2.6.1
>Reporter: Anthony Castrati
>Priority: Major
>
> After a recent upgrade to storm-kafka-client on storm server 2.6.1, we are
> seeing ConcurrentModificationException in our topology at runtime. I believe
> this is due to the re-use of a KafkaConsumer instance between the KafkaSpout
> and the
> KafkaOffsetPartitionMetrics which were added some time between 2.4.0 and
> 2.6.1.
>
> h3. Steps to Reproduce:
> Configure a topology with a basic KafkaSpout. Configure the topology with one
> of the metrics loggers. We used our own custom one, but reproduced it with
> ConsoleStormReporter as well. The JMXReporter did not reproduce the issue for
> us, but we did not dig into why.
> *reporter config:*
> {{topology.metrics.reporters: [}}
> {{ {}}
> {{ "filter": {}}
> {{ "expression": ".*",}}
> {{ "class": "org.apache.storm.metrics2.filters.RegexFilter"}}
> {{ },}}
> {{ "report.period": 15,}}
> {{ "report.period.units": "SECONDS",}}
> {{ "class": "org.apache.storm.metrics2.reporters.ConsoleStormReporter"}}
> }
> {{]}}
> h3. Stacktrace:
> {quote}[ERROR] Exception thrown from NewRelicReporter#report. Exception was
> suppressed.
> java.util.ConcurrentModificationException: KafkaConsumer is not safe for
> multi-threaded access. currentThread(name:
> metrics-newRelicReporter-1-thread-1, id: 24) otherThread(id: 40)
> at
> org.apache.kafka.clients.consumer.KafkaConsumer.acquire(KafkaConsumer.java:2484)
> ~[stormjar.jar:?]
> at
> org.apache.kafka.clients.consumer.KafkaConsumer.acquireAndEnsureOpen(KafkaConsumer.java:2465)
> ~[stormjar.jar:?]
> at
> org.apache.kafka.clients.consumer.KafkaConsumer.beginningOffsets(KafkaConsumer.java:2144)
> ~[stormjar.jar:?]
> at
> org.apache.kafka.clients.consumer.KafkaConsumer.beginningOffsets(KafkaConsumer.java:2123)
> ~[stormjar.jar:?]
> at
> org.apache.storm.kafka.spout.metrics2.KafkaOffsetPartitionMetrics.getBeginningOffsets(KafkaOffsetPartitionMetrics.java:181)
> ~[stormjar.jar:?]
> at
> org.apache.storm.kafka.spout.metrics2.KafkaOffsetPartitionMetrics$2.getValue(KafkaOffsetPartitionMetrics.java:93)
> ~[stormjar.jar:?]
> at
> org.apache.storm.kafka.spout.metrics2.KafkaOffsetPartitionMetrics$2.getValue(KafkaOffsetPartitionMetrics.java:90)
> ~[stormjar.jar:?]
> at
> com.codahale.metrics.newrelic.transformer.GaugeTransformer.transform(GaugeTransformer.java:60)
> ~[stormjar.jar:?]
> at
> com.codahale.metrics.newrelic.NewRelicReporter.lambda$transform$0(NewRelicReporter.java:154)
> ~[stormjar.jar:?]
> at java.base/java.util.stream.ReferencePipeline$7$1.accept(Unknown
> Source) ~[?:?]
> at
> java.base/java.util.Collections$UnmodifiableMap$UnmodifiableEntrySet.lambda$entryConsumer$0(Unknown
> Source) ~[?:?]
> at java.base/java.util.TreeMap$EntrySpliterator.forEachRemaining(Unknown
> Source) ~[?:?]
> at
> java.base/java.util.Collections$UnmodifiableMap$UnmodifiableEntrySet$UnmodifiableEntrySetSpliterator.forEachRemaining(Unknown
> Source) ~[?:?]
> at java.base/java.util.stream.AbstractPipeline.copyInto(Unknown Source)
> ~[?:?]
> at java.base/java.util.stream.AbstractPipeline.wrapAndCopyInto(Unknown
> Source) ~[?:?]
> at
> java.base/java.util.stream.ForEachOps$ForEachOp.evaluateSequential(Unknown
> Source) ~[?:?]
> at
> java.base/java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateSequential(Unknown
> Source) ~[?:?]
> at java.base/java.util.stream.AbstractPipeline.evaluate(Unknown Source)
> ~[?:?]
> at java.base/java.util.stream.ReferencePipeline.forEach(Unknown Source)
> ~[?:?]
> at java.base/java.util.stream.ReferencePipeline$7$1.accept(Unknown
> Source) ~[?:?]
> at
> java.base/java.util.Spliterators$ArraySpliterator.forEachRemaining(Unknown
> Source) ~[?:?]
> at java.base/java.util.stream.AbstractPipeline.copyInto(Unknown Source)
> ~[?:?]
> at java.base/java.util.stream.AbstractPipeline.wrapAndCopyInto(Unknown
> Source) ~[?:?]
> at
> java.base/java.util.stream.ReduceOps$ReduceOp.evaluateSequential(Unknown
> Source) ~[?:?]
> at java.base/java.util.stream.AbstractPipeline.evaluate(Unknown Source)
> ~[?:?]
> at
[jira] [Closed] (STORM-4054) Add Worker CPU Metric
[ https://issues.apache.org/jira/browse/STORM-4054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla closed STORM-4054. -- Resolution: Fixed > Add Worker CPU Metric > - > > Key: STORM-4054 > URL: https://issues.apache.org/jira/browse/STORM-4054 > Project: Apache Storm > Issue Type: Improvement >Reporter: Richard Zowalla >Assignee: Aaron Gresch >Priority: Minor > Fix For: 2.6.3 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Allow reporting of worker cpu usage if no cgroups are configured. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (STORM-4053) Add Hadoop client API dependency back to storm-hdfs
[ https://issues.apache.org/jira/browse/STORM-4053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla closed STORM-4053. -- Fix Version/s: 2.6.3 Assignee: Richard Zowalla Resolution: Fixed > Add Hadoop client API dependency back to storm-hdfs > --- > > Key: STORM-4053 > URL: https://issues.apache.org/jira/browse/STORM-4053 > Project: Apache Storm > Issue Type: Task > Components: storm-hdfs >Affects Versions: 2.6.2 >Reporter: Julien Nioche >Assignee: Richard Zowalla >Priority: Major > Fix For: 2.6.3 > > Time Spent: 1h 10m > Remaining Estimate: 0h > > See https://github.com/apache/incubator-stormcrawler/pull/1189 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (STORM-4054) Add Worker CPU Metric
Richard Zowalla created STORM-4054: -- Summary: Add Worker CPU Metric Key: STORM-4054 URL: https://issues.apache.org/jira/browse/STORM-4054 Project: Apache Storm Issue Type: Improvement Reporter: Richard Zowalla Assignee: Aaron Gresch Fix For: 2.6.3 Allow reporting of worker cpu usage if no cgroups are configured. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (STORM-4052) Simplify/Remove double delete/lookup in heartbeat cleanup code
[ https://issues.apache.org/jira/browse/STORM-4052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla closed STORM-4052. -- Resolution: Fixed > Simplify/Remove double delete/lookup in heartbeat cleanup code > -- > > Key: STORM-4052 > URL: https://issues.apache.org/jira/browse/STORM-4052 > Project: Apache Storm > Issue Type: Bug >Affects Versions: 2.6.1, 2.6.2 >Reporter: Richard Zowalla >Priority: Major > Fix For: 2.6.3 > > Time Spent: 20m > Remaining Estimate: 0h > > This changes slightly simplifies the heartbeat cleanup code so it no longer > tries to delete the heartbeat files twice. It also removes an unneeded > directory listing (and possible race) by truncating the versions list and > using it for removal instead of for keeping. > Removing the double delete attempt is important because it removes a lookup > for now non-existent files. Looking up non existent files, especially highly > unique (like timestamped) ones can adversely affect many operating systems as > these lookups are cached as negative dentries. > [https://lwn.net/Articles/814535/] > When cleanup runs, it iterates over the heartbeat directory that contains a > token and version file for each heartbeat. It calls deleteVersion for each > file in the directory which attempts to delete both files associated with the > heartbeat. As deleteVersion already deletes both when it first iterates over > the token file, the iteration for the version file has nothing to do. > Before removing, the deleteVersion code checks for the existence of these now > non existent files. On linux (and other OSs) a lookup for a non-existent path > will create a negative dentry in the operating system's cache. On some > configurations this cache can grow effectively unbounded leading to > performance issues. On newer systems this cache is better managed, but this > will still dilute an otherwise useful OS cache with useless entries. > > Copied from [https://github.com/apache/storm/pull/3635] (Author: sammac) > > > > > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (STORM-4052) Simplify/Remove double delete/lookup in heartbeat cleanup code
Richard Zowalla created STORM-4052: -- Summary: Simplify/Remove double delete/lookup in heartbeat cleanup code Key: STORM-4052 URL: https://issues.apache.org/jira/browse/STORM-4052 Project: Apache Storm Issue Type: Bug Affects Versions: 2.6.2, 2.6.1 Reporter: Richard Zowalla Fix For: 2.6.3 This changes slightly simplifies the heartbeat cleanup code so it no longer tries to delete the heartbeat files twice. It also removes an unneeded directory listing (and possible race) by truncating the versions list and using it for removal instead of for keeping. Removing the double delete attempt is important because it removes a lookup for now non-existent files. Looking up non existent files, especially highly unique (like timestamped) ones can adversely affect many operating systems as these lookups are cached as negative dentries. [https://lwn.net/Articles/814535/] When cleanup runs, it iterates over the heartbeat directory that contains a token and version file for each heartbeat. It calls deleteVersion for each file in the directory which attempts to delete both files associated with the heartbeat. As deleteVersion already deletes both when it first iterates over the token file, the iteration for the version file has nothing to do. Before removing, the deleteVersion code checks for the existence of these now non existent files. On linux (and other OSs) a lookup for a non-existent path will create a negative dentry in the operating system's cache. On some configurations this cache can grow effectively unbounded leading to performance issues. On newer systems this cache is better managed, but this will still dilute an otherwise useful OS cache with useless entries. Copied from [https://github.com/apache/storm/pull/3635] (Author: sammac) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (STORM-4051) Scheduler needs to include acker memory for topology resources
[ https://issues.apache.org/jira/browse/STORM-4051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla closed STORM-4051. -- Resolution: Fixed > Scheduler needs to include acker memory for topology resources > -- > > Key: STORM-4051 > URL: https://issues.apache.org/jira/browse/STORM-4051 > Project: Apache Storm > Issue Type: Bug >Reporter: Aaron Gresch >Assignee: Aaron Gresch >Priority: Major > Fix For: 2.6.3 > > Time Spent: 20m > Remaining Estimate: 0h > > The scheduler has a bug where acker memory is not considered in the > scheduling estimate. The case I found was where a topology should fit on two > supervisors, but the cluster has 1 available and 2 blacklisted. The scheduler > thinks the topology should fit on one supervisor and fails to schedule, but > also fails to release a supervisor from the blacklist, resulting in the > topology never getting scheduled. > With this fix, the scheduler properly detects the topology will need to be > scheduled on two supervisors and releases one from the blacklist and > schedules successfully. > Switched some scheduling logs from trace to debug to make debugging > scheduling issues easier. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (STORM-4051) Scheduler needs to include acker memory for topology resources
Richard Zowalla created STORM-4051: -- Summary: Scheduler needs to include acker memory for topology resources Key: STORM-4051 URL: https://issues.apache.org/jira/browse/STORM-4051 Project: Apache Storm Issue Type: Bug Reporter: Aaron Gresch Assignee: Aaron Gresch Fix For: 2.6.3 The scheduler has a bug where acker memory is not considered in the scheduling estimate. The case I found was where a topology should fit on two supervisors, but the cluster has 1 available and 2 blacklisted. The scheduler thinks the topology should fit on one supervisor and fails to schedule, but also fails to release a supervisor from the blacklist, resulting in the topology never getting scheduled. With this fix, the scheduler properly detects the topology will need to be scheduled on two supervisors and releases one from the blacklist and schedules successfully. Switched some scheduling logs from trace to debug to make debugging scheduling issues easier. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (STORM-4050) rocksdbjni:8.10.0
[ https://issues.apache.org/jira/browse/STORM-4050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla closed STORM-4050. -- Resolution: Fixed > rocksdbjni:8.10.0 > -- > > Key: STORM-4050 > URL: https://issues.apache.org/jira/browse/STORM-4050 > Project: Apache Storm > Issue Type: Dependency upgrade >Reporter: Richard Zowalla >Assignee: Julien Nioche >Priority: Major > Fix For: 2.6.2 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (STORM-4048) netty 4.1.107.Final
[ https://issues.apache.org/jira/browse/STORM-4048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla closed STORM-4048. -- Resolution: Fixed > netty 4.1.107.Final > > > Key: STORM-4048 > URL: https://issues.apache.org/jira/browse/STORM-4048 > Project: Apache Storm > Issue Type: Dependency upgrade >Reporter: Richard Zowalla >Assignee: Julien Nioche >Priority: Major > Fix For: 2.6.2 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (STORM-4048) netty 4.1.107.Final
Richard Zowalla created STORM-4048: -- Summary: netty 4.1.107.Final Key: STORM-4048 URL: https://issues.apache.org/jira/browse/STORM-4048 Project: Apache Storm Issue Type: Dependency upgrade Reporter: Richard Zowalla Assignee: Julien Nioche Fix For: 2.6.2 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (STORM-4050) rocksdbjni:8.10.0
Richard Zowalla created STORM-4050: -- Summary: rocksdbjni:8.10.0 Key: STORM-4050 URL: https://issues.apache.org/jira/browse/STORM-4050 Project: Apache Storm Issue Type: Dependency upgrade Reporter: Richard Zowalla Assignee: Julien Nioche Fix For: 2.6.2 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (STORM-4047) jackson 2.16.1
[ https://issues.apache.org/jira/browse/STORM-4047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla closed STORM-4047. -- Resolution: Fixed > jackson 2.16.1 > -- > > Key: STORM-4047 > URL: https://issues.apache.org/jira/browse/STORM-4047 > Project: Apache Storm > Issue Type: Dependency upgrade >Reporter: Richard Zowalla >Assignee: Julien Nioche >Priority: Major > Fix For: 2.6.2 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (STORM-4049) snakeyaml:2.2
Richard Zowalla created STORM-4049: -- Summary: snakeyaml:2.2 Key: STORM-4049 URL: https://issues.apache.org/jira/browse/STORM-4049 Project: Apache Storm Issue Type: Dependency upgrade Reporter: Richard Zowalla Assignee: Julien Nioche Fix For: 2.6.2 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (STORM-4049) snakeyaml:2.2
[ https://issues.apache.org/jira/browse/STORM-4049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla closed STORM-4049. -- Resolution: Fixed > snakeyaml:2.2 > - > > Key: STORM-4049 > URL: https://issues.apache.org/jira/browse/STORM-4049 > Project: Apache Storm > Issue Type: Dependency upgrade >Reporter: Richard Zowalla >Assignee: Julien Nioche >Priority: Major > Fix For: 2.6.2 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (STORM-4047) jackson 2.16.1
Richard Zowalla created STORM-4047: -- Summary: jackson 2.16.1 Key: STORM-4047 URL: https://issues.apache.org/jira/browse/STORM-4047 Project: Apache Storm Issue Type: Dependency upgrade Reporter: Richard Zowalla Assignee: Julien Nioche Fix For: 2.6.2 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (STORM-4046) caffeine:3.1.8
Richard Zowalla created STORM-4046: -- Summary: caffeine:3.1.8 Key: STORM-4046 URL: https://issues.apache.org/jira/browse/STORM-4046 Project: Apache Storm Issue Type: Dependency upgrade Reporter: Richard Zowalla Assignee: Julien Nioche -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (STORM-4045) log4j2 2.23.0
Richard Zowalla created STORM-4045: -- Summary: log4j2 2.23.0 Key: STORM-4045 URL: https://issues.apache.org/jira/browse/STORM-4045 Project: Apache Storm Issue Type: Dependency upgrade Reporter: Richard Zowalla Assignee: Julien Nioche -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (STORM-4045) log4j2 2.23.0
[ https://issues.apache.org/jira/browse/STORM-4045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla closed STORM-4045. -- Fix Version/s: 2.6.2 Resolution: Fixed > log4j2 2.23.0 > -- > > Key: STORM-4045 > URL: https://issues.apache.org/jira/browse/STORM-4045 > Project: Apache Storm > Issue Type: Dependency upgrade >Reporter: Richard Zowalla >Assignee: Julien Nioche >Priority: Major > Fix For: 2.6.2 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (STORM-4044) commons-lang3:3.14.0
[ https://issues.apache.org/jira/browse/STORM-4044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla closed STORM-4044. -- Resolution: Fixed > commons-lang3:3.14.0 > > > Key: STORM-4044 > URL: https://issues.apache.org/jira/browse/STORM-4044 > Project: Apache Storm > Issue Type: Dependency upgrade >Reporter: Richard Zowalla >Assignee: Julien Nioche >Priority: Major > Fix For: 2.6.2 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (STORM-4046) caffeine:3.1.8
[ https://issues.apache.org/jira/browse/STORM-4046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla closed STORM-4046. -- Fix Version/s: 2.6.2 Resolution: Fixed > caffeine:3.1.8 > -- > > Key: STORM-4046 > URL: https://issues.apache.org/jira/browse/STORM-4046 > Project: Apache Storm > Issue Type: Dependency upgrade >Reporter: Richard Zowalla >Assignee: Julien Nioche >Priority: Major > Fix For: 2.6.2 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (STORM-4044) commons-lang3:3.14.0
Richard Zowalla created STORM-4044: -- Summary: commons-lang3:3.14.0 Key: STORM-4044 URL: https://issues.apache.org/jira/browse/STORM-4044 Project: Apache Storm Issue Type: Dependency upgrade Reporter: Richard Zowalla Assignee: Julien Nioche Fix For: 2.6.2 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (STORM-4043) commons-io:2.14.0
[ https://issues.apache.org/jira/browse/STORM-4043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla closed STORM-4043. -- Resolution: Fixed > commons-io:2.14.0 > - > > Key: STORM-4043 > URL: https://issues.apache.org/jira/browse/STORM-4043 > Project: Apache Storm > Issue Type: Dependency upgrade >Reporter: Richard Zowalla >Assignee: Julien Nioche >Priority: Major > Fix For: 2.6.2 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (STORM-4043) commons-io:2.14.0
Richard Zowalla created STORM-4043: -- Summary: commons-io:2.14.0 Key: STORM-4043 URL: https://issues.apache.org/jira/browse/STORM-4043 Project: Apache Storm Issue Type: Dependency upgrade Reporter: Richard Zowalla Assignee: Julien Nioche Fix For: 2.6.2 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (STORM-4030) Dependency upgrades
[
https://issues.apache.org/jira/browse/STORM-4030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Zowalla closed STORM-4030.
--
Resolution: Fixed
> Dependency upgrades
> ---
>
> Key: STORM-4030
> URL: https://issues.apache.org/jira/browse/STORM-4030
> Project: Apache Storm
> Issue Type: Task
>Affects Versions: 2.6.1
>Reporter: Julien Nioche
>Assignee: Julien Nioche
>Priority: Minor
> Fix For: 2.6.2
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> {code:java}
> mvn versions:display-dependency-updates
> "-Dmaven.version.ignore=.*-M.*,.*-alpha.*,.*-beta.*,.*-BETA.*,.*-b.*,.*.ALPHA.*"
> | grep '\->' | sort | uniq{code}
> {{shows a large number of upgradable dependencies.}}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Reopened] (STORM-4030) Dependency upgrades
[
https://issues.apache.org/jira/browse/STORM-4030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Zowalla reopened STORM-4030:
> Dependency upgrades
> ---
>
> Key: STORM-4030
> URL: https://issues.apache.org/jira/browse/STORM-4030
> Project: Apache Storm
> Issue Type: Task
>Affects Versions: 2.6.1
>Reporter: Julien Nioche
>Assignee: Julien Nioche
>Priority: Minor
> Fix For: 2.7.0
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> {code:java}
> mvn versions:display-dependency-updates
> "-Dmaven.version.ignore=.*-M.*,.*-alpha.*,.*-beta.*,.*-BETA.*,.*-b.*,.*.ALPHA.*"
> | grep '\->' | sort | uniq{code}
> {{shows a large number of upgradable dependencies.}}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (STORM-4038) Cleanup Hadoop Dependencies
[ https://issues.apache.org/jira/browse/STORM-4038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla closed STORM-4038. -- Resolution: Fixed > Cleanup Hadoop Dependencies > --- > > Key: STORM-4038 > URL: https://issues.apache.org/jira/browse/STORM-4038 > Project: Apache Storm > Issue Type: Improvement >Affects Versions: 2.6.1 >Reporter: Richard Zowalla >Assignee: Richard Zowalla >Priority: Major > Fix For: 2.6.2 > > Time Spent: 20m > Remaining Estimate: 0h > > hadoop pulls in a lot of stuff we do not actually need. might be good to > prune / exclude -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (STORM-4029) Bump org.apache.commons:commons-compress from 1.21 to 1.26.
[ https://issues.apache.org/jira/browse/STORM-4029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla closed STORM-4029. -- Resolution: Fixed > Bump org.apache.commons:commons-compress from 1.21 to 1.26. > --- > > Key: STORM-4029 > URL: https://issues.apache.org/jira/browse/STORM-4029 > Project: Apache Storm > Issue Type: Dependency upgrade >Affects Versions: 2.6.1 >Reporter: Richard Zowalla >Assignee: Richard Zowalla >Priority: Major > Fix For: 2.6.2 > > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Reopened] (STORM-4029) Bump org.apache.commons:commons-compress from 1.21 to 1.26.
[ https://issues.apache.org/jira/browse/STORM-4029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla reopened STORM-4029: > Bump org.apache.commons:commons-compress from 1.21 to 1.26. > --- > > Key: STORM-4029 > URL: https://issues.apache.org/jira/browse/STORM-4029 > Project: Apache Storm > Issue Type: Dependency upgrade >Affects Versions: 2.6.1 >Reporter: Richard Zowalla >Assignee: Richard Zowalla >Priority: Major > Fix For: 2.7.0 > > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Reopened] (STORM-4038) Cleanup Hadoop Dependencies
[ https://issues.apache.org/jira/browse/STORM-4038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla reopened STORM-4038: > Cleanup Hadoop Dependencies > --- > > Key: STORM-4038 > URL: https://issues.apache.org/jira/browse/STORM-4038 > Project: Apache Storm > Issue Type: Improvement >Affects Versions: 2.6.1 >Reporter: Richard Zowalla >Assignee: Richard Zowalla >Priority: Major > Fix For: 2.7.0 > > Time Spent: 20m > Remaining Estimate: 0h > > hadoop pulls in a lot of stuff we do not actually need. might be good to > prune / exclude -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (STORM-4030) Dependency upgrades
[
https://issues.apache.org/jira/browse/STORM-4030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Zowalla updated STORM-4030:
---
Fix Version/s: 2.6.2
(was: 2.7.0)
> Dependency upgrades
> ---
>
> Key: STORM-4030
> URL: https://issues.apache.org/jira/browse/STORM-4030
> Project: Apache Storm
> Issue Type: Task
>Affects Versions: 2.6.1
>Reporter: Julien Nioche
>Assignee: Julien Nioche
>Priority: Minor
> Fix For: 2.6.2
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> {code:java}
> mvn versions:display-dependency-updates
> "-Dmaven.version.ignore=.*-M.*,.*-alpha.*,.*-beta.*,.*-BETA.*,.*-b.*,.*.ALPHA.*"
> | grep '\->' | sort | uniq{code}
> {{shows a large number of upgradable dependencies.}}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (STORM-4038) Cleanup Hadoop Dependencies
[ https://issues.apache.org/jira/browse/STORM-4038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla updated STORM-4038: --- Fix Version/s: 2.6.2 (was: 2.7.0) > Cleanup Hadoop Dependencies > --- > > Key: STORM-4038 > URL: https://issues.apache.org/jira/browse/STORM-4038 > Project: Apache Storm > Issue Type: Improvement >Affects Versions: 2.6.1 >Reporter: Richard Zowalla >Assignee: Richard Zowalla >Priority: Major > Fix For: 2.6.2 > > Time Spent: 20m > Remaining Estimate: 0h > > hadoop pulls in a lot of stuff we do not actually need. might be good to > prune / exclude -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (STORM-4029) Bump org.apache.commons:commons-compress from 1.21 to 1.26.
[ https://issues.apache.org/jira/browse/STORM-4029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla updated STORM-4029: --- Fix Version/s: 2.6.2 (was: 2.7.0) > Bump org.apache.commons:commons-compress from 1.21 to 1.26. > --- > > Key: STORM-4029 > URL: https://issues.apache.org/jira/browse/STORM-4029 > Project: Apache Storm > Issue Type: Dependency upgrade >Affects Versions: 2.6.1 >Reporter: Richard Zowalla >Assignee: Richard Zowalla >Priority: Major > Fix For: 2.6.2 > > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (STORM-4042) Clojure 1.11.2
[ https://issues.apache.org/jira/browse/STORM-4042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla closed STORM-4042. -- Resolution: Fixed > Clojure 1.11.2 > -- > > Key: STORM-4042 > URL: https://issues.apache.org/jira/browse/STORM-4042 > Project: Apache Storm > Issue Type: Dependency upgrade >Affects Versions: 2.6.1 >Reporter: Richard Zowalla >Assignee: Richard Zowalla >Priority: Major > Fix For: 2.6.2 > > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (STORM-4041) Zookeeper 3.9.2
[ https://issues.apache.org/jira/browse/STORM-4041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla closed STORM-4041. -- Resolution: Fixed > Zookeeper 3.9.2 > --- > > Key: STORM-4041 > URL: https://issues.apache.org/jira/browse/STORM-4041 > Project: Apache Storm > Issue Type: Dependency upgrade >Reporter: Richard Zowalla >Assignee: Richard Zowalla >Priority: Major > Fix For: 2.6.2 > > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (STORM-4042) Clojure 1.11.2
Richard Zowalla created STORM-4042: -- Summary: Clojure 1.11.2 Key: STORM-4042 URL: https://issues.apache.org/jira/browse/STORM-4042 Project: Apache Storm Issue Type: Dependency upgrade Affects Versions: 2.6.1 Reporter: Richard Zowalla Assignee: Richard Zowalla Fix For: 2.6.2 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (STORM-4041) Zookeeper 3.9.2
Richard Zowalla created STORM-4041: -- Summary: Zookeeper 3.9.2 Key: STORM-4041 URL: https://issues.apache.org/jira/browse/STORM-4041 Project: Apache Storm Issue Type: Dependency upgrade Reporter: Richard Zowalla Assignee: Richard Zowalla Fix For: 2.6.2 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (STORM-4040) Nimbus fails to start up on older CPUs (RocksDB v7.x.x onwards)
[ https://issues.apache.org/jira/browse/STORM-4040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla closed STORM-4040. -- Fix Version/s: 2.6.2 Resolution: Fixed > Nimbus fails to start up on older CPUs (RocksDB v7.x.x onwards) > --- > > Key: STORM-4040 > URL: https://issues.apache.org/jira/browse/STORM-4040 > Project: Apache Storm > Issue Type: Documentation > Components: documentation >Affects Versions: 2.5.0 > Environment: CPU is pre-Haswell >Reporter: Scott Moore >Assignee: Scott Moore >Priority: Minor > Fix For: 2.6.2 > > Time Spent: 20m > Remaining Estimate: 0h > > When Nimbus start-up and storm_rocks already contains data, the JVM will > encounter an illegal instruction exception if the CPU is pre-Haswell era. > This can be seen on such a CPU by deploying a running topology then > restarting Nimbus. It will fail to startup because the JVM will have crashed > when RocksDB reads the state from storm_rocks folder. (You can recover from > this by deleting the storm_rocks folder - Nimbus will then startup ok ... > until the next time it restarts!) > The issue is that RocksDB v7.x.x or higher (so, applies to Storm 2.5.0 > onwards from this commit > [https://github.com/apache/storm/commit/d7b4c084a89961a4060edb2e755491a21015c200]) > is a C++ component built for modern CPUs. The fix for this is to downgrade > RocksDB to pre v7.x.x (or you can build your own version of v7+ from source > with certain compiler options set) > You can find other reports of this - e.g. > [https://github.com/facebook/rocksdb/issues/11096] or > [https://github.com/trezor/blockbook/issues/684] > This is not a bug in Storm, of course. Nor is it a bug - more a 'minimum > requirements'. > So I have a pull request to suggest workarounds for this in the > Troubleshooting guide. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (STORM-4038) Cleanup Hadoop Dependencies
[ https://issues.apache.org/jira/browse/STORM-4038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla closed STORM-4038. -- Resolution: Fixed > Cleanup Hadoop Dependencies > --- > > Key: STORM-4038 > URL: https://issues.apache.org/jira/browse/STORM-4038 > Project: Apache Storm > Issue Type: Improvement >Affects Versions: 2.6.1 >Reporter: Richard Zowalla >Assignee: Richard Zowalla >Priority: Major > Fix For: 2.7.0 > > Time Spent: 20m > Remaining Estimate: 0h > > hadoop pulls in a lot of stuff we do not actually need. might be good to > prune / exclude -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (STORM-4038) Cleanup Hadoop Dependencies
Richard Zowalla created STORM-4038: -- Summary: Cleanup Hadoop Dependencies Key: STORM-4038 URL: https://issues.apache.org/jira/browse/STORM-4038 Project: Apache Storm Issue Type: Improvement Affects Versions: 2.6.1 Reporter: Richard Zowalla Assignee: Richard Zowalla Fix For: 2.7.0 hadoop pulls in a lot of stuff we do not actually need. might be good to prune / exclude -- This message was sent by Atlassian Jira (v8.20.10#820010)
