[jira] [Resolved] (STORM-3811) Upgrade log4j version to 2.17.1

[ https://issues.apache.org/jira/browse/STORM-3811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ethan Li resolved STORM-3811. - Resolution: Fixed > Upgrade log4j version to 2.17.1 > --- > >

[jira] [Updated] (STORM-3811) Upgrade log4j version to 2.17.1

[ https://issues.apache.org/jira/browse/STORM-3811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ethan Li updated STORM-3811: Fix Version/s: 2.2.2 2.1.2 > Upgrade log4j version to 2.17.1 >

[jira] [Updated] (STORM-3811) Upgrade log4j version to 2.17.1

[ https://issues.apache.org/jira/browse/STORM-3811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ethan Li updated STORM-3811: Priority: Critical (was: Major) > Upgrade log4j version to 2.17.1 > --- > >

[jira] [Updated] (STORM-3811) Upgrade log4j version to 2.17.1

[ https://issues.apache.org/jira/browse/STORM-3811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ethan Li updated STORM-3811: Issue Type: Dependency upgrade (was: Improvement) > Upgrade log4j version to 2.17.1 >

[jira] [Updated] (STORM-3811) Upgrade log4j version to 2.17.1

[ https://issues.apache.org/jira/browse/STORM-3811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ethan Li updated STORM-3811: Fix Version/s: 1.2.5 > Upgrade log4j version to 2.17.1 > --- > >

[jira] [Closed] (STORM-3810) CVE-2021-44228 Log4J vulnerability

[ https://issues.apache.org/jira/browse/STORM-3810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ethan Li closed STORM-3810. --- Resolution: Duplicate > CVE-2021-44228 Log4J vulnerability > -- > >

[jira] [Closed] (STORM-3808) Bump log4j version to 2.16.0 (original ticket was 2.15.0)

[ https://issues.apache.org/jira/browse/STORM-3808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ethan Li closed STORM-3808. --- > Bump log4j version to 2.16.0 (original ticket was 2.15.0) >

[jira] [Closed] (STORM-3809) CVE-2021-44228 Log4Shell: upgrade log4j2

[ https://issues.apache.org/jira/browse/STORM-3809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ethan Li closed STORM-3809. --- > CVE-2021-44228 Log4Shell: upgrade log4j2 > > > Key:

[jira] [Resolved] (STORM-3808) Bump log4j version to 2.16.0 (original ticket was 2.15.0)

[ https://issues.apache.org/jira/browse/STORM-3808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ethan Li resolved STORM-3808. - Resolution: Duplicate > Bump log4j version to 2.16.0 (original ticket was 2.15.0) >

[jira] [Resolved] (STORM-3809) CVE-2021-44228 Log4Shell: upgrade log4j2

[ https://issues.apache.org/jira/browse/STORM-3809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ethan Li resolved STORM-3809. - Resolution: Duplicate > CVE-2021-44228 Log4Shell: upgrade log4j2 >

[jira] [Updated] (STORM-3811) Upgrade log4j version to 2.17.1

[ https://issues.apache.org/jira/browse/STORM-3811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ethan Li updated STORM-3811: Fix Version/s: 2.3.1 2.4.0 > Upgrade log4j version to 2.17.1 >

[jira] [Updated] (STORM-3811) Upgrade log4j version to 2.17.1

[ https://issues.apache.org/jira/browse/STORM-3811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ethan Li updated STORM-3811: Summary: Upgrade log4j version to 2.17.1 (was: update log4j) > Upgrade log4j version to 2.17.1 >

[jira] [Updated] (STORM-3803) Format large integers in Storm UI with commas for readability

[ https://issues.apache.org/jira/browse/STORM-3803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ethan Li updated STORM-3803: Fix Version/s: 2.4.0 > Format large integers in Storm UI with commas for readability >

[jira] [Resolved] (STORM-3799) Logging user information for blob delete req

[ https://issues.apache.org/jira/browse/STORM-3799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ethan Li resolved STORM-3799. - Fix Version/s: 2.4.0 Resolution: Fixed Thanks [~snikhil5]. Merged to the master branch

[jira] [Updated] (STORM-3693) TimeOut ticks should be addressed to Executor instead of being addressed to a task or broadcasted.

[ https://issues.apache.org/jira/browse/STORM-3693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ethan Li updated STORM-3693: Fix Version/s: (was: 2.2.1) > TimeOut ticks should be addressed to Executor instead of being addressed

[jira] [Updated] (STORM-3767) NPE on getComponentPendingProfileActions

[ https://issues.apache.org/jira/browse/STORM-3767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ethan Li updated STORM-3767: Fix Version/s: 2.1.1 > NPE on getComponentPendingProfileActions >

[jira] [Updated] (STORM-3767) NPE on getComponentPendingProfileActions

[ https://issues.apache.org/jira/browse/STORM-3767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ethan Li updated STORM-3767: Fix Version/s: 2.2.1 > NPE on getComponentPendingProfileActions >

[jira] [Assigned] (STORM-3737) Share Worker Metric Registry For Guice AOP Based Metrics Integeration

[ https://issues.apache.org/jira/browse/STORM-3737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ethan Li reassigned STORM-3737: --- Assignee: Lakshman Sai > Share Worker Metric Registry For Guice AOP Based Metrics Integeration >

[jira] [Resolved] (STORM-3793) Add metric to track backpressure status for a task

[ https://issues.apache.org/jira/browse/STORM-3793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ethan Li resolved STORM-3793. - Resolution: Fixed master: 185107f478c75ec9a78b90d036c9bcd639152494 > Add metric to track backpressure

[jira] [Updated] (STORM-3793) Add metric to track backpressure status for a task

[ https://issues.apache.org/jira/browse/STORM-3793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ethan Li updated STORM-3793: Fix Version/s: 2.3.0 > Add metric to track backpressure status for a task >

[jira] [Resolved] (STORM-3767) NPE on getComponentPendingProfileActions

[ https://issues.apache.org/jira/browse/STORM-3767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ethan Li resolved STORM-3767. - Resolution: Fixed > NPE on getComponentPendingProfileActions >

[jira] [Updated] (STORM-3767) NPE on getComponentPendingProfileActions

[ https://issues.apache.org/jira/browse/STORM-3767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ethan Li updated STORM-3767: Affects Version/s: 2.2.0 2.0.0 2.1.0 > NPE on

[jira] [Updated] (STORM-3767) NPE on getComponentPendingProfileActions

[ https://issues.apache.org/jira/browse/STORM-3767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ethan Li updated STORM-3767: Fix Version/s: 2.3.0 > NPE on getComponentPendingProfileActions >

[jira] [Updated] (STORM-3785) Rate metrics are wrongly divided by 1000000

[ https://issues.apache.org/jira/browse/STORM-3785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ethan Li updated STORM-3785: Component/s: storm-client > Rate metrics are wrongly divided by 100 >

[jira] [Resolved] (STORM-3785) Rate metrics are wrongly divided by 1000000

[ https://issues.apache.org/jira/browse/STORM-3785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ethan Li resolved STORM-3785. - Resolution: Fixed > Rate metrics are wrongly divided by 100 >

[jira] [Commented] (STORM-3785) Rate metrics are wrongly divided by 1000000

[ https://issues.apache.org/jira/browse/STORM-3785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17418798#comment-17418798 ] Ethan Li commented on STORM-3785: - Merged in master: 0c7bbca67db593b82030a7b406a44d54122ce792,

[jira] [Updated] (STORM-3785) Rate metrics are wrongly divided by 1000000

[ https://issues.apache.org/jira/browse/STORM-3785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ethan Li updated STORM-3785: Fix Version/s: 2.2.1 2.3.0 > Rate metrics are wrongly divided by 100 >

[jira] [Updated] (STORM-3785) Rate metrics are wrongly divided by 1000000

[ https://issues.apache.org/jira/browse/STORM-3785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ethan Li updated STORM-3785: Affects Version/s: 2.2.0 > Rate metrics are wrongly divided by 100 >

[jira] [Assigned] (STORM-3785) Rate metrics are wrongly divided by 1000000

[ https://issues.apache.org/jira/browse/STORM-3785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ethan Li reassigned STORM-3785: --- Assignee: Rui Li > Rate metrics are wrongly divided by 100 >

[jira] [Assigned] (STORM-3767) NPE on getComponentPendingProfileActions

[ https://issues.apache.org/jira/browse/STORM-3767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ethan Li reassigned STORM-3767: --- Assignee: Ethan Li > NPE on getComponentPendingProfileActions >

[jira] [Commented] (STORM-3388) Launch workers inside container using runc runtime

[ https://issues.apache.org/jira/browse/STORM-3388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17399964#comment-17399964 ] Ethan Li commented on STORM-3388: - A follow-up bug fix is merged in master branch

[jira] [Resolved] (STORM-3388) Launch workers inside container using runc runtime

[ https://issues.apache.org/jira/browse/STORM-3388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ethan Li resolved STORM-3388. - Fix Version/s: 2.3.0 Resolution: Fixed Filed follow up jiras: STORM-3787 STORM-3788 STORM-3789

[jira] [Created] (STORM-3789) STORM-3388 follow up: answer unresolved questions in comments

Ethan Li created STORM-3789: --- Summary: STORM-3388 follow up: answer unresolved questions in comments Key: STORM-3789 URL: https://issues.apache.org/jira/browse/STORM-3789 Project: Apache Storm

[jira] [Created] (STORM-3788) Add more comments in docker-to-squash.py

Ethan Li created STORM-3788: --- Summary: Add more comments in docker-to-squash.py Key: STORM-3788 URL: https://issues.apache.org/jira/browse/STORM-3788 Project: Apache Storm Issue Type: Story

[jira] [Created] (STORM-3787) Add error messages in worker-launcher c code where it is missing

Ethan Li created STORM-3787: --- Summary: Add error messages in worker-launcher c code where it is missing Key: STORM-3787 URL: https://issues.apache.org/jira/browse/STORM-3787 Project: Apache Storm

[jira] [Commented] (STORM-3388) Launch workers inside container using runc runtime

[ https://issues.apache.org/jira/browse/STORM-3388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17394927#comment-17394927 ] Ethan Li commented on STORM-3388: - Merged to master branch (ce078fcb78dd881f70df0be34e04940a53c38394) >

[jira] [Commented] (STORM-3765) NPE in DRPCSimpleACLAuthorizer.readAclFromConfig when drpc.authorizer.acl has no values

[ https://issues.apache.org/jira/browse/STORM-3765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17338554#comment-17338554 ] Ethan Li commented on STORM-3765: - Merged into master : d5244b8cb06a0f840ad1bf5d3faf74948702fdb9 > NPE

[jira] [Resolved] (STORM-3765) NPE in DRPCSimpleACLAuthorizer.readAclFromConfig when drpc.authorizer.acl has no values

[ https://issues.apache.org/jira/browse/STORM-3765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ethan Li resolved STORM-3765. - Resolution: Fixed > NPE in DRPCSimpleACLAuthorizer.readAclFromConfig when drpc.authorizer.acl has > no

[jira] [Updated] (STORM-3765) NPE in DRPCSimpleACLAuthorizer.readAclFromConfig when drpc.authorizer.acl has no values

[ https://issues.apache.org/jira/browse/STORM-3765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ethan Li updated STORM-3765: Affects Version/s: 2.2.0 2.0.0 2.1.0 > NPE in

[jira] [Updated] (STORM-3765) NPE in DRPCSimpleACLAuthorizer.readAclFromConfig when drpc.authorizer.acl has no values

[ https://issues.apache.org/jira/browse/STORM-3765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ethan Li updated STORM-3765: Fix Version/s: 2.3.0 > NPE in DRPCSimpleACLAuthorizer.readAclFromConfig when drpc.authorizer.acl has > no

[jira] [Created] (STORM-3767) NPE on getComponentPendingProfileActions

Ethan Li created STORM-3767: --- Summary: NPE on getComponentPendingProfileActions Key: STORM-3767 URL: https://issues.apache.org/jira/browse/STORM-3767 Project: Apache Storm Issue Type: Bug

[jira] [Created] (STORM-3765) NPE in DRPCSimpleACLAuthorizer.readAclFromConfig when drpc.authorizer.acl has no values

Ethan Li created STORM-3765: --- Summary: NPE in DRPCSimpleACLAuthorizer.readAclFromConfig when drpc.authorizer.acl has no values Key: STORM-3765 URL: https://issues.apache.org/jira/browse/STORM-3765 Project:

[jira] [Assigned] (STORM-3765) NPE in DRPCSimpleACLAuthorizer.readAclFromConfig when drpc.authorizer.acl has no values

[ https://issues.apache.org/jira/browse/STORM-3765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ethan Li reassigned STORM-3765: --- Assignee: Ethan Li > NPE in DRPCSimpleACLAuthorizer.readAclFromConfig when drpc.authorizer.acl has

[jira] [Resolved] (STORM-3763) Backpressure message ignored by the receiver caused the topology to not progress

[ https://issues.apache.org/jira/browse/STORM-3763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ethan Li resolved STORM-3763. - Fix Version/s: 2.2.1 2.3.0 Resolution: Fixed Merged to master:

[jira] [Updated] (STORM-3763) Backpressure message ignored by the receiver caused the topology to not progress

[ https://issues.apache.org/jira/browse/STORM-3763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ethan Li updated STORM-3763: Description: We have noticed a case where topology is stuck due to the mis-interpretation of backpressure

[jira] [Assigned] (STORM-3763) Backpressure message ignored by the receiver caused the topology to not progress

[ https://issues.apache.org/jira/browse/STORM-3763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ethan Li reassigned STORM-3763: --- Assignee: Ethan Li > Backpressure message ignored by the receiver caused the topology to not >

[jira] [Updated] (STORM-3763) Backpressure message ignored by the receiver caused the topology to not progress

[ https://issues.apache.org/jira/browse/STORM-3763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ethan Li updated STORM-3763: Description: We have noticed a case where topology is stuck due to the mis-interpretation of backpressure

[jira] [Created] (STORM-3763) Backpressure message ignored by the receiver caused the topology to not progress

Ethan Li created STORM-3763: --- Summary: Backpressure message ignored by the receiver caused the topology to not progress Key: STORM-3763 URL: https://issues.apache.org/jira/browse/STORM-3763 Project: Apache

[jira] [Resolved] (STORM-3744) IntelliJ does not find shaded classes

[ https://issues.apache.org/jira/browse/STORM-3744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ethan Li resolved STORM-3744. - Fix Version/s: 2.3.0 Resolution: Fixed Thanks [~bipinprasad] I merged this to master:

[jira] [Resolved] (STORM-3755) While scheduling multiple ackers with executor use best effort basis

[ https://issues.apache.org/jira/browse/STORM-3755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ethan Li resolved STORM-3755. - Resolution: Fixed Thanks [~bipinprasad]. I merges this to master:

[jira] [Updated] (STORM-3757) Update jackson version to 2.10.0

[ https://issues.apache.org/jira/browse/STORM-3757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ethan Li updated STORM-3757: Affects Version/s: 2.2.0 2.0.0 2.1.0 > Update jackson

[jira] [Resolved] (STORM-3757) Update jackson version to 2.10.0

[ https://issues.apache.org/jira/browse/STORM-3757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ethan Li resolved STORM-3757. - Fix Version/s: 2.3.0 Resolution: Fixed [~kishorvpatil] I filed a JIRA for this since I feel we

[jira] [Created] (STORM-3757) Update jackson version to 2.10.0

Ethan Li created STORM-3757: --- Summary: Update jackson version to 2.10.0 Key: STORM-3757 URL: https://issues.apache.org/jira/browse/STORM-3757 Project: Apache Storm Issue Type: Dependency upgrade

[jira] [Updated] (STORM-3704) Cosmetic: columns shifted in "Topology summary" table

[ https://issues.apache.org/jira/browse/STORM-3704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ethan Li updated STORM-3704: Fix Version/s: 2.3.0 > Cosmetic: columns shifted in "Topology summary" table >

[jira] [Resolved] (STORM-3704) Cosmetic: columns shifted in "Topology summary" table

[ https://issues.apache.org/jira/browse/STORM-3704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ethan Li resolved STORM-3704. - Fix Version/s: 2.2.1 2.3.0 Resolution: Fixed Merged this to master :

[jira] [Assigned] (STORM-3704) Cosmetic: columns shifted in "Topology summary" table

[ https://issues.apache.org/jira/browse/STORM-3704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ethan Li reassigned STORM-3704: --- Assignee: Vitaliy Fuks > Cosmetic: columns shifted in "Topology summary" table >

[jira] [Commented] (STORM-3704) Cosmetic: columns shifted in "Topology summary" table

[ https://issues.apache.org/jira/browse/STORM-3704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17303560#comment-17303560 ] Ethan Li commented on STORM-3704: - [~vitaliy.fuks] Thanks for the contribution. I added you as a

[jira] [Comment Edited] (STORM-3735) Kyro serialization fails on some metric tuples when topology.fall.back.on.java.serialization is false

[ https://issues.apache.org/jira/browse/STORM-3735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17268047#comment-17268047 ] Ethan Li edited comment on STORM-3735 at 1/19/21, 5:13 PM: --- With STORM-3682

[jira] [Commented] (STORM-3735) Kyro serialization fails on some metric tuples when topology.fall.back.on.java.serialization is false

[ https://issues.apache.org/jira/browse/STORM-3735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17268047#comment-17268047 ] Ethan Li commented on STORM-3735: - With STORM-3682 (code: https://github.com/apache/storm/pull/3371/), I

[jira] [Resolved] (STORM-3735) Kyro serialization fails on some metric tuples when topology.fall.back.on.java.serialization is false

[ https://issues.apache.org/jira/browse/STORM-3735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ethan Li resolved STORM-3735. - Fix Version/s: 2.3.0 Resolution: Fixed Merged to master

[jira] [Assigned] (STORM-3735) Kyro serialization fails on some metric tuples when topology.fall.back.on.java.serialization is false

[ https://issues.apache.org/jira/browse/STORM-3735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ethan Li reassigned STORM-3735: --- Assignee: Ethan Li > Kyro serialization fails on some metric tuples when >

[jira] [Updated] (STORM-3735) Kyro serialization fails on some metric tuples when topology.fall.back.on.java.serialization is false

[ https://issues.apache.org/jira/browse/STORM-3735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ethan Li updated STORM-3735: Affects Version/s: 2.2.0 2.0.0 2.1.0 > Kyro serialization

[jira] [Created] (STORM-3735) Kyro serialization fails on some metric tuples when topology.fall.back.on.java.serialization is false

Ethan Li created STORM-3735: --- Summary: Kyro serialization fails on some metric tuples when topology.fall.back.on.java.serialization is false Key: STORM-3735 URL: https://issues.apache.org/jira/browse/STORM-3735

[jira] [Resolved] (STORM-3727) SUPERVISOR_SLOTS_PORTS could be list of Longs

[ https://issues.apache.org/jira/browse/STORM-3727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ethan Li resolved STORM-3727. - Fix Version/s: 2.3.0 Resolution: Fixed Thanks [~agresch]. I merged this to master

[jira] [Updated] (STORM-3734) IntegerValidator doesn't force the object type to be Integer

[ https://issues.apache.org/jira/browse/STORM-3734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ethan Li updated STORM-3734: Description: The IntegerValidator allows the non-integer object, like Double(1.0).

[jira] [Created] (STORM-3734) IntegerValidator doesn't force the object type to be Integer

Ethan Li created STORM-3734: --- Summary: IntegerValidator doesn't force the object type to be Integer Key: STORM-3734 URL: https://issues.apache.org/jira/browse/STORM-3734 Project: Apache Storm

[jira] [Resolved] (STORM-3731) Remove unused nashorn import in storm-loadgen:OutputStream.java

[ https://issues.apache.org/jira/browse/STORM-3731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ethan Li resolved STORM-3731. - Fix Version/s: 2.3.0 Resolution: Fixed Thanks [~bipinprasad]. I merged this to master

[jira] [Resolved] (STORM-3729) Assigning memory greater and equal than 2048m will make assgin memory for slot values to 1m

[ https://issues.apache.org/jira/browse/STORM-3729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ethan Li resolved STORM-3729. - Fix Version/s: 2.3.0 Resolution: Fixed Thanks [~Zeahoo]. I merged this to master

[jira] [Assigned] (STORM-3729) Assigning memory greater and equal than 2048m will make assgin memory for slot values to 1m

[ https://issues.apache.org/jira/browse/STORM-3729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ethan Li reassigned STORM-3729: --- Assignee: ZhihaoZheng > Assigning memory greater and equal than 2048m will make assgin memory for

[jira] [Updated] (STORM-3729) Assigning memory greater and equal than 2048m will make assgin memory for slot values to 1m

[ https://issues.apache.org/jira/browse/STORM-3729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ethan Li updated STORM-3729: Affects Version/s: 2.0.0 > Assigning memory greater and equal than 2048m will make assgin memory for >

[jira] [Resolved] (STORM-3650) Ackers and metricComponents are not distributed evenly

[ https://issues.apache.org/jira/browse/STORM-3650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ethan Li resolved STORM-3650. - Fix Version/s: 2.3.0 Resolution: Fixed Thanks [~li530]. I merged this to master

[jira] [Updated] (STORM-3650) Ackers and metricComponents are not distributed evenly

[ https://issues.apache.org/jira/browse/STORM-3650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ethan Li updated STORM-3650: Description: (When resource aware scheudler is used,) System components like ackers or metricComponents

[jira] [Updated] (STORM-3650) Ackers and metricComponents are not distributed evenly

[ https://issues.apache.org/jira/browse/STORM-3650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ethan Li updated STORM-3650: Description: (When resource aware scheduler is used,) System components like ackers or metricComponents

[jira] [Updated] (STORM-3650) Ackers and metricComponents are not distributed evenly

[ https://issues.apache.org/jira/browse/STORM-3650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ethan Li updated STORM-3650: Priority: Major (was: Minor) > Ackers and metricComponents are not distributed evenly >

[jira] [Updated] (STORM-3728) Workers are not able to connect to Pacemaker if pacemaker.auth.method is KERBEROS

[ https://issues.apache.org/jira/browse/STORM-3728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ethan Li updated STORM-3728: Fix Version/s: 2.3.0 > Workers are not able to connect to Pacemaker if pacemaker.auth.method is >

[jira] [Resolved] (STORM-3728) Workers are not able to connect to Pacemaker if pacemaker.auth.method is KERBEROS

[ https://issues.apache.org/jira/browse/STORM-3728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ethan Li resolved STORM-3728. - Resolution: Fixed Merged into master (ab6b6f69a10bf57c1b46a6519d57ca423d99558c) > Workers are not able

[jira] [Updated] (STORM-3728) Workers are not able to connect to Pacemaker if pacemaker.auth.method is KERBEROS

[ https://issues.apache.org/jira/browse/STORM-3728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ethan Li updated STORM-3728: Affects Version/s: 2.2.0 2.0.0 2.1.0 > Workers are not able

[jira] [Commented] (STORM-3725) DRPC spout will crash when any one of DRPC server is down

[ https://issues.apache.org/jira/browse/STORM-3725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17253567#comment-17253567 ] Ethan Li commented on STORM-3725: - Thanks [~li530]. I merged this to master

[jira] [Resolved] (STORM-3725) DRPC spout will crash when any one of DRPC server is down

[ https://issues.apache.org/jira/browse/STORM-3725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ethan Li resolved STORM-3725. - Resolution: Fixed > DRPC spout will crash when any one of DRPC server is down >

[jira] [Updated] (STORM-3725) DRPC spout will crash when any one of DRPC server is down

[ https://issues.apache.org/jira/browse/STORM-3725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ethan Li updated STORM-3725: Fix Version/s: 2.3.0 > DRPC spout will crash when any one of DRPC server is down >

[jira] [Updated] (STORM-3725) DRPC spout will crash when any one of DRPC server is down

[ https://issues.apache.org/jira/browse/STORM-3725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ethan Li updated STORM-3725: Affects Version/s: 2.2.0 2.0.0 2.1.0 > DRPC spout will crash

[jira] [Updated] (STORM-3728) Workers are not able to connect to Pacemaker if pacemaker.auth.method is KERBEROS

[ https://issues.apache.org/jira/browse/STORM-3728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ethan Li updated STORM-3728: Description: When pacemaker.auth.method is KERBEROS,  worker will fail to connect to KERBEROS because of

[jira] [Assigned] (STORM-3728) Workers are not able to connect to Pacemaker if pacemaker.auth.method is KERBEROS

[ https://issues.apache.org/jira/browse/STORM-3728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ethan Li reassigned STORM-3728: --- Assignee: Ethan Li > Workers are not able to connect to Pacemaker if pacemaker.auth.method is >

[jira] [Created] (STORM-3728) Workers are not able to connect to Pacemaker if pacemaker.auth.method is KERBEROS

Ethan Li created STORM-3728: --- Summary: Workers are not able to connect to Pacemaker if pacemaker.auth.method is KERBEROS Key: STORM-3728 URL: https://issues.apache.org/jira/browse/STORM-3728 Project:

[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

[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 >

[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

[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 >

[jira] [Resolved] (STORM-3722) Update committer list

[ https://issues.apache.org/jira/browse/STORM-3722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ethan Li resolved STORM-3722. - Fix Version/s: 2.3.0 Resolution: Fixed Thanks [~bipinprasad]. I merged this to master

[jira] [Updated] (STORM-3708) ConstraintSolverConfig LOG messages should include topology id

[ https://issues.apache.org/jira/browse/STORM-3708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ethan Li updated STORM-3708: Priority: Minor (was: Major) > ConstraintSolverConfig LOG messages should include topology id >

[jira] [Resolved] (STORM-3708) ConstraintSolverConfig LOG messages should include topology id

[ https://issues.apache.org/jira/browse/STORM-3708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ethan Li resolved STORM-3708. - Fix Version/s: 2.3.0 Resolution: Fixed Thanks [~bipinprasad]. I merged this to master

[jira] [Resolved] (STORM-3721) Change child pom.xml reference to parent pom.xml

[ https://issues.apache.org/jira/browse/STORM-3721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ethan Li resolved STORM-3721. - Fix Version/s: 2.3.0 Resolution: Fixed Thanks [~bipinprasad]. I merged this to master

[jira] [Resolved] (STORM-3709) Reject topology submission if missing spout

[ https://issues.apache.org/jira/browse/STORM-3709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ethan Li resolved STORM-3709. - Fix Version/s: 2.3.0 Resolution: Fixed Thanks [~bipinprasad]. I merged this to master

[jira] [Resolved] (STORM-3706) Cluster.needsSchedulingRas always succeeds

[ https://issues.apache.org/jira/browse/STORM-3706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ethan Li resolved STORM-3706. - Fix Version/s: 2.3.0 Resolution: Fixed Thanks [~bipinprasad]. I merged this to master

[jira] [Commented] (STORM-3715) Add Caching to HDFS BlobStore

[ https://issues.apache.org/jira/browse/STORM-3715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17232525#comment-17232525 ] Ethan Li commented on STORM-3715: - Thanks [~kishorvpatil]. I merged this to master

[jira] [Resolved] (STORM-3715) Add Caching to HDFS BlobStore

[ https://issues.apache.org/jira/browse/STORM-3715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ethan Li resolved STORM-3715. - Fix Version/s: 2.3.0 Resolution: Fixed > Add Caching to HDFS BlobStore >

[jira] [Resolved] (STORM-3681) Enable basic Travis ARM CI job

[ https://issues.apache.org/jira/browse/STORM-3681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ethan Li resolved STORM-3681. - Fix Version/s: 2.3.0 Resolution: Fixed > Enable basic Travis ARM CI job >

[jira] [Issue Comment Deleted] (STORM-3681) Enable basic Travis ARM CI job

[ https://issues.apache.org/jira/browse/STORM-3681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ethan Li updated STORM-3681: Comment: was deleted (was: [~seanlau] found that arm64-graviton2 is not supported on travis-ci.org.

[jira] [Commented] (STORM-3401) There is no ARM CI for Storm

[ https://issues.apache.org/jira/browse/STORM-3401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17232435#comment-17232435 ] Ethan Li commented on STORM-3401: - reopened due to unresolved issues in STORM-3711 > There is no ARM CI

[jira] [Reopened] (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 reopened STORM-3711: - [~seanlau] found that arm64-graviton2 is not supported on travis-ci.org. Looking for solutions > Enable

  1   2   3   4   5   6   7   8   9   10   >