[jira] [Resolved] (STORM-3723) ServerUtils.isAnyPosixProcessPidDirAlive might return wrong result
[ https://issues.apache.org/jira/browse/STORM-3723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ethan Li resolved STORM-3723. - Fix Version/s: 2.3.0 Resolution: Fixed Thanks [~bipinprasad]. Merged this into master (9a9596685348e310078fb6b0970a629703465454) > ServerUtils.isAnyPosixProcessPidDirAlive might return wrong result > -- > > Key: STORM-3723 > URL: https://issues.apache.org/jira/browse/STORM-3723 > Project: Apache Storm > Issue Type: Bug > Components: storm-server >Reporter: Bipin Prasad >Assignee: Bipin Prasad >Priority: Minor > Fix For: 2.3.0 > > Time Spent: 1h 10m > Remaining Estimate: 0h > > There is a bug in ServerUtils.isAnyPosixProcessPidDirAlive() and it returns > incorrect value when all the processIds have been reassigned/reused. > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (STORM-3401) There is no ARM CI for Storm
[ https://issues.apache.org/jira/browse/STORM-3401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ethan Li resolved STORM-3401. - Resolution: Fixed Closing this as all subtasks are done > There is no ARM CI for Storm > > > Key: STORM-3401 > URL: https://issues.apache.org/jira/browse/STORM-3401 > Project: Apache Storm > Issue Type: Improvement > Components: build >Reporter: Yikun Jiang >Priority: Major > > Now the CI of storm (in github) is handled by travis-ci. While the test is > running under x86 ARCH, the arm ARCH is missing. This leads an problem that > we don't have a way to test every pull request that if it'll break the storm > deployment on arm or not. > We should add a CI system that support ARM ARCH. Using it, storm can > officially support arm release in the future. Here I'd like to introduce > OpenLab to the community. [OpenLab|https://openlabtesting.org/] is a open > source CI system that can test any open source software on either x86 or arm > ARCH, it's mainly used by github projects. Now some > [projects|https://github.com/theopenlab/openlab-zuul-jobs/blob/master/zuul.d/jobs.yaml] > has integrated it already. Such as containerd (a graduated CNCF project, the > arm build will be triggerd in every PR, > [https://github.com/containerd/containerd/pulls]), terraform and so on. > OpenLab uses the open source CI software [Zuul > |https://github.com/openstack-infra/zuul] for CI system. Zuul is used by > OpenStack community as well. integrating with OpneLab is quite easy using its > github app. All config info is open source as well. > If apache storm community has interested with it, I can help for the > integration. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (STORM-3711) Enable all the modules in ARM CI
[ https://issues.apache.org/jira/browse/STORM-3711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17250756#comment-17250756 ] Ethan Li commented on STORM-3711: - Thanks [~seanlau]. Merged your fix into master (6b3922f8a2ee41d24538213626555d460a3d5415) > Enable all the modules in ARM CI > > > Key: STORM-3711 > URL: https://issues.apache.org/jira/browse/STORM-3711 > Project: Apache Storm > Issue Type: Sub-task >Reporter: liusheng >Assignee: liusheng >Priority: Major > Time Spent: 3h 10m > Remaining Estimate: 0h > > In the https://issues.apache.org/jira/browse/STORM-3681 We have enabled the > ARM 64 CI with only "Client" module configured, because there are some issues > about Travis CI due to its ARM > resources performance, now Travis CI has the new ARM resources > "arm64-graviton2" provided by AWS, please see[1]. Now we can switch to use > the "arm64-graviton2" resources and enable all the modules on ARM CI. > [https://docs.travis-ci.com/user/multi-cpu-architectures] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (STORM-3711) Enable all the modules in ARM CI
[ https://issues.apache.org/jira/browse/STORM-3711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ethan Li resolved STORM-3711. - Fix Version/s: 2.3.0 Resolution: Fixed > Enable all the modules in ARM CI > > > Key: STORM-3711 > URL: https://issues.apache.org/jira/browse/STORM-3711 > Project: Apache Storm > Issue Type: Sub-task >Reporter: liusheng >Assignee: liusheng >Priority: Major > Fix For: 2.3.0 > > Time Spent: 3h 10m > Remaining Estimate: 0h > > In the https://issues.apache.org/jira/browse/STORM-3681 We have enabled the > ARM 64 CI with only "Client" module configured, because there are some issues > about Travis CI due to its ARM > resources performance, now Travis CI has the new ARM resources > "arm64-graviton2" provided by AWS, please see[1]. Now we can switch to use > the "arm64-graviton2" resources and enable all the modules on ARM CI. > [https://docs.travis-ci.com/user/multi-cpu-architectures] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (STORM-3724) Use blobstore dir modtime to avoid update lookups by HDFSBlobstore
Aaron Gresch created STORM-3724: --- Summary: Use blobstore dir modtime to avoid update lookups by HDFSBlobstore Key: STORM-3724 URL: https://issues.apache.org/jira/browse/STORM-3724 Project: Apache Storm Issue Type: Improvement Reporter: Aaron Gresch Assignee: Aaron Gresch We have multiple storm clusters with 100's of supervisors polling for blob updates. This causes high load on our Hadoop namenodes that are also used by multiple other clusters. An improvement would be for the AsyncLocalizer to check the remote blobstore last mod time once and then skip checking each individual blob if it was already checked for the same mod time. -- This message was sent by Atlassian Jira (v8.3.4#803005)
