[jira] [Updated] (STORM-3960) Read keystore/truststore files in jks or pkcs12 prompt based on extension
[ https://issues.apache.org/jira/browse/STORM-3960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bipin Prasad updated STORM-3960: Summary: Read keystore/truststore files in jks or pkcs12 prompt based on extension (was: Read keystore/truststore files in jks or pkcs prompt based on extension) > Read keystore/truststore files in jks or pkcs12 prompt based on extension > - > > Key: STORM-3960 > URL: https://issues.apache.org/jira/browse/STORM-3960 > Project: Apache Storm > Issue Type: Task > Components: storm-client >Reporter: Bipin Prasad >Assignee: Bipin Prasad >Priority: Major > Fix For: 2.6.0 > > > Storm reads JKS (Java Key Store) format files for key and certificates. Read > pkcs12 format keystore and truststore of TLS connections. Infer file type > from extension without the need to specify the keystore/truststore type. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (STORM-3960) Read keystore/truststore files in jks or pkcs prompt based on extension
[ https://issues.apache.org/jira/browse/STORM-3960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bipin Prasad reassigned STORM-3960: --- Assignee: Bipin Prasad > Read keystore/truststore files in jks or pkcs prompt based on extension > --- > > Key: STORM-3960 > URL: https://issues.apache.org/jira/browse/STORM-3960 > Project: Apache Storm > Issue Type: Task > Components: storm-client >Reporter: Bipin Prasad >Assignee: Bipin Prasad >Priority: Major > Fix For: 2.6.0 > > > Storm reads JKS (Java Key Store) format files for key and certificates. Read > pkcs12 format keystore and truststore of TLS connections. Infer file type > from extension without the need to specify the keystore/truststore type. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (STORM-3960) Read keystore/truststore files in jks or pkcs prompt based on extension
Bipin Prasad created STORM-3960: --- Summary: Read keystore/truststore files in jks or pkcs prompt based on extension Key: STORM-3960 URL: https://issues.apache.org/jira/browse/STORM-3960 Project: Apache Storm Issue Type: Task Components: storm-client Reporter: Bipin Prasad Fix For: 2.6.0 Storm reads JKS (Java Key Store) format files for key and certificates. Read pkcs12 format keystore and truststore of TLS connections. Infer file type from extension without the need to specify the keystore/truststore type. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (STORM-3885) Security fix upgrade com.fasterxml.jackson.core:jackson-databind to 2.15.2
[ https://issues.apache.org/jira/browse/STORM-3885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla updated STORM-3885: --- Fix Version/s: 2.6.0 > Security fix upgrade com.fasterxml.jackson.core:jackson-databind to 2.15.2 > -- > > Key: STORM-3885 > URL: https://issues.apache.org/jira/browse/STORM-3885 > Project: Apache Storm > Issue Type: Dependency upgrade >Reporter: Bipin Prasad >Assignee: Richard Zowalla >Priority: Major > Fix For: 2.6.0 > > Time Spent: 50m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (STORM-3885) Security fix upgrade com.fasterxml.jackson.core:jackson-databind to 2.15.2
[ https://issues.apache.org/jira/browse/STORM-3885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17759007#comment-17759007 ] Richard Zowalla commented on STORM-3885: https://github.com/apache/storm/pull/3571 > Security fix upgrade com.fasterxml.jackson.core:jackson-databind to 2.15.2 > -- > > Key: STORM-3885 > URL: https://issues.apache.org/jira/browse/STORM-3885 > Project: Apache Storm > Issue Type: Dependency upgrade >Reporter: Bipin Prasad >Assignee: Richard Zowalla >Priority: Major > Fix For: 2.6.0 > > Time Spent: 50m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (STORM-3885) Security fix upgrade com.fasterxml.jackson.core:jackson-databind to 2.15.2
[ https://issues.apache.org/jira/browse/STORM-3885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla updated STORM-3885: --- Summary: Security fix upgrade com.fasterxml.jackson.core:jackson-databind to 2.15.2 (was: Security fix upgrade com.fasterxml.jackson.core:jackson-databind to 2.12.6.1) > Security fix upgrade com.fasterxml.jackson.core:jackson-databind to 2.15.2 > -- > > Key: STORM-3885 > URL: https://issues.apache.org/jira/browse/STORM-3885 > Project: Apache Storm > Issue Type: Dependency upgrade >Reporter: Bipin Prasad >Priority: Major > Time Spent: 50m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (STORM-3885) Security fix upgrade com.fasterxml.jackson.core:jackson-databind to 2.15.2
[ https://issues.apache.org/jira/browse/STORM-3885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla reassigned STORM-3885: -- Assignee: Richard Zowalla > Security fix upgrade com.fasterxml.jackson.core:jackson-databind to 2.15.2 > -- > > Key: STORM-3885 > URL: https://issues.apache.org/jira/browse/STORM-3885 > Project: Apache Storm > Issue Type: Dependency upgrade >Reporter: Bipin Prasad >Assignee: Richard Zowalla >Priority: Major > Time Spent: 50m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (STORM-3795) storm list displays logs and execution information
[
https://issues.apache.org/jira/browse/STORM-3795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Zowalla closed STORM-3795.
--
Resolution: Not A Problem
Please use the user@ list to ask such questions. Thanks.
> storm list displays logs and execution information
> --
>
> Key: STORM-3795
> URL: https://issues.apache.org/jira/browse/STORM-3795
> Project: Apache Storm
> Issue Type: Question
> Components: storm-client
>Reporter: Kaushal Kumar
>Priority: Major
>
> We are using storm list command to get the list of running topology along
> with its statuses. The execution response shows few log statements and then a
> table containing the topology details.
> Is there any option available in list command to suppress the meta
> information (Running:... and logs) and only show the topology details.
>
> {code:java}
> $ sudo /opt/storm/bin/storm list
> Running: java -client -Ddaemon.name= -Dstorm.options=
> -Dstorm.home=/opt/storm -Dstorm.log.dir=/opt/storm/logs
> -Djava.library.path=/usr/local/lib:/opt/local/lib:/usr/lib:/usr/lib64
> -Dstorm.conf.file= -cp
> /opt/storm/:/opt/storm/lib/:/opt/storm/extlib/:/opt/storm/extlib-daemon/:/opt/storm/conf:/opt/storm/bin
> org.apache.storm.command.ListTopologies
> 11:18:10.808 [main] INFO o.a.s.v.ConfigValidation - Will use [class
> org.apache.storm.DaemonConfig, class org.apache.storm.Config] for validation
> 11:18:10.897 [main] WARN o.a.s.v.ConfigValidation -
> task.heartbeat.frequency.secs is a deprecated config please see class
> org.apache.storm.Config.TASK_HEARTBEAT_FREQUENCY_SECS for more information.
> 11:18:10.999 [main] INFO o.a.s.u.NimbusClient - Found leader nimbus :
> hostname:6627
> Topology_name Status Num_tasks Num_workers Uptime_secs Topology_Id Owner
>
>
> TestJob_1 ACTIVE 6 1 5263482 TestJob_1-13-1627046008 xyz
> ${code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (STORM-3813) Build Failure
[ https://issues.apache.org/jira/browse/STORM-3813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla closed STORM-3813. -- Resolution: Cannot Reproduce > Build Failure > - > > Key: STORM-3813 > URL: https://issues.apache.org/jira/browse/STORM-3813 > Project: Apache Storm > Issue Type: Bug >Reporter: dori waldman >Priority: Minor > > I follow the getting started steps at > [https://github.com/apache/storm/tree/v2.3.0/examples/storm-starter] > download storm source , > install maven 3.8.4 , and java openJdk 1.8.0_292 > run mvn clean install and it failed , in order to fix it i modify root > pom.xml > > attached below the repositories section that works > > > true > false > central > https://repo1.maven.org/maven2/ > > > true > false > clojars > https://clojars.org/repo/ > > > repository.jboss.org-public > https://repository.jboss.org/nexus/content/groups/public > true > false > > > maven.restlet.org > https://maven.restlet.talend.com > true > false > > > > > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (STORM-3796) How many topologies can create in a cluster?
[ https://issues.apache.org/jira/browse/STORM-3796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla closed STORM-3796. -- Resolution: Not A Problem Please use the user@ list to ask such questions. Thanks. > How many topologies can create in a cluster? > > > Key: STORM-3796 > URL: https://issues.apache.org/jira/browse/STORM-3796 > Project: Apache Storm > Issue Type: Request > Components: storm-sql >Affects Versions: 2.2.0 >Reporter: prabhakaran >Priority: Major > > This is not a bug. I want to know the topologies behaviour. I read many sites > related to Storm's topologies design setup. But, I didn't get clarity. > In my project, I am going to processing more than a million records. So, I > planned to create topologies dynamically based on internal modules. The count > might be reached more than a thousand. My doubt is what is the best way to > manage topologies? How many topologies can be created in a single cluster? > Are there any problems with maintaining multiple topologies? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (STORM-3826) upgrade commons-io due to security issue
[ https://issues.apache.org/jira/browse/STORM-3826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla closed STORM-3826. -- Fix Version/s: 2.5.0 Resolution: Fixed > upgrade commons-io due to security issue > > > Key: STORM-3826 > URL: https://issues.apache.org/jira/browse/STORM-3826 > Project: Apache Storm > Issue Type: Improvement >Reporter: PJ Fanning >Priority: Major > Fix For: 2.5.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > https://github.com/advisories/GHSA-gwrp-pvrq-jmwv -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (STORM-3871) Storm blobstore leak space
[
https://issues.apache.org/jira/browse/STORM-3871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17759001#comment-17759001
]
Richard Zowalla commented on STORM-3871:
Does this happen in Storm 2.5.0 or 2.6.0-SNAPSHOT?
> Storm blobstore leak space
> --
>
> Key: STORM-3871
> URL: https://issues.apache.org/jira/browse/STORM-3871
> Project: Apache Storm
> Issue Type: Bug
> Components: blobstore
>Affects Versions: 2.3.0
> Environment: Storm 2.3.0 in Kubernetes 1.21
> Storm nimbus have 3 empty dir volumes mapped to
> /var/lib/kubelet/pods/.../volumes in a 10GB /var limit.
> Storm has default blob cleanup strategy.
>Reporter: Antoine Tran
>Priority: Major
>
> We observe after 5 days, with 3 nimbus deployed in HA, that the blostore
> keeps growing.
>
> Usually we submit topologies each 10min and it ends in around 10 min. The
> expected result is that the blobstore cleans itself so that topologies older
> than days are removed. But this is not the case, as seen below (done the
> 2022-06-03, expected result: only blob from the current day should appear.
> current behavior: blobs from 2 days ago are still here)
>
> {noformat}
> /space/StormApp/current/bin/storm blobstore list 2>&1 | grep
> o.a.s.c.Blobstore | sort -k7 | perl -anE '$date=localtime($F[6]/1000);shift
> @F;say join " ", $date, @F'
> Wed Jun 1 14:12:43 2022 [main] INFO o.a.s.c.Blobstore -
> dep-apeframework-3.11.3-8f132aef-b401-4fa6-b07e-3588073da824.jar
> 1654092763312 [o::r--, o::rwa, u:class
> org.apache.storm.security.auth.NimbusPrincipal:rwa]
> Wed Jun 1 14:13:43 2022 [main] INFO o.a.s.c.Blobstore -
> dep-apeframework-3.11.3-ae74967a-0def-44a1-8d1b-53a255900239.jar
> 1654092823330 [o::r--, o::rwa, u:class
> org.apache.storm.security.auth.NimbusPrincipal:rwa]
> Wed Jun 1 14:33:00 2022 [main] INFO o.a.s.c.Blobstore -
> dep-apeframework-3.11.3-8fa7edcb-5f8a-4a79-8f8d-8c8fd50dbc9e.jar
> 1654093980305 [o::r--, o::rwa, u:class
> org.apache.storm.security.auth.NimbusPrincipal:rwa]
> Wed Jun 1 15:14:19 2022 [main] INFO o.a.s.c.Blobstore -
> dep-apeframework-3.11.3-9168e429-2cd6-433c-90d9-6db19d564824.jar
> 1654096459069 [o::r--, o::rwa, u:class
> org.apache.storm.security.auth.NimbusPrincipal:rwa]
> Wed Jun 1 16:13:49 2022 [main] INFO o.a.s.c.Blobstore -
> dep-apeframework-3.11.3-9ed7a9fd-2819-4784-a953-c04a65981c59.jar
> 1654100029294 [o::r--, o::rwa, u:class
> org.apache.storm.security.auth.NimbusPrincipal:rwa]
> Wed Jun 1 22:53:29 2022 [main] INFO o.a.s.c.Blobstore -
> dep-apeframework-3.11.3-124b606a-0d2b-44a1-9885-4bb1152a98e7.jar
> 1654124009759 [o::r--, o::rwa, u:class
> org.apache.storm.security.auth.NimbusPrincipal:rwa]
> Wed Jun 1 23:23:59 2022 [main] INFO o.a.s.c.Blobstore -
> dep-apeframework-3.11.3-be7e85b7-3cf1-495a-83a7-6a28da33af57.jar
> 1654125839685 [o::r--, o::rwa, u:class
> org.apache.storm.security.auth.NimbusPrincipal:rwa]
> Wed Jun 1 23:33:43 2022 [main] INFO o.a.s.c.Blobstore -
> dep-apeframework-3.11.3-f799a103-d544-4a31-a680-1d0625fab2b9.jar
> 1654126423302 [o::r--, o::rwa, u:class
> org.apache.storm.security.auth.NimbusPrincipal:rwa]
> Thu Jun 2 01:13:49 2022 [main] INFO o.a.s.c.Blobstore -
> dep-apeframework-3.11.3-3edcef03-f7d6-400e-8076-30dc0e5c4bff.jar
> 1654132429251 [o::r--, o::rwa, u:class
> org.apache.storm.security.auth.NimbusPrincipal:rwa]
> Thu Jun 2 02:03:29 2022 [main] INFO o.a.s.c.Blobstore -
> dep-apeframework-3.11.3-807000a6-0416-4821-b67d-a1e5e433edce.jar
> 1654135409776 [o::r--, o::rwa, u:class
> org.apache.storm.security.auth.NimbusPrincipal:rwa]
> Thu Jun 2 02:13:30 2022 [main] INFO o.a.s.c.Blobstore -
> dep-apeframework-3.11.3-4f7e7439-7788-4b74-81a2-4d6433caed4b.jar
> 1654136010028 [o::r--, o::rwa, u:class
> org.apache.storm.security.auth.NimbusPrincipal:rwa]
> Thu Jun 2 03:03:59 2022 [main] INFO o.a.s.c.Blobstore -
> dep-apeframework-3.11.3-038e17f3-7acd-4c19-a212-a095e6c7adba.jar
> 1654139039870 [o::r--, o::rwa, u:class
> org.apache.storm.security.auth.NimbusPrincipal:rwa]
> Thu Jun 2 07:43:30 2022 [main] INFO o.a.s.c.Blobstore -
> dep-apeframework-3.11.3-b4fb1761-4f97-4ac7-8785-85e2aefbb66c.jar
> 1654155810868 [o::r--, o::rwa, u:class
> org.apache.storm.security.auth.NimbusPrincipal:rwa]
> Thu Jun 2 08:33:49 2022 [main] INFO o.a.s.c.Blobstore -
> dep-apeframework-3.11.3-ac2c4004-d561-44ad-beca-0883ad8980c5.jar
> 1654158829119 [o::r--, o::rwa, u:class
> org.apache.storm.security.auth.NimbusPrincipal:rwa]
> Thu Jun 2 09:44:00 2022 [main] INFO o.a.s.c.Blobstore -
> dep-apeframework-3.11.3-31f8b9b4-8f79-47ef-8728-46127baf04a2.jar
> 1654163040830 [o::r--, o::rwa, u:class
> org.apache.storm.security.auth.NimbusPrincipal:rwa]
> Thu Jun 2 09:53:00 2022 [main] INFO o.a.s.c.Blobstore -
>
[jira] [Commented] (STORM-3882) Continuously worker EventThread shut down when storm is running
[
https://issues.apache.org/jira/browse/STORM-3882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17759000#comment-17759000
]
Richard Zowalla commented on STORM-3882:
Does this also happen with the recent (2.5.0 or 2.6.0-SNAPSHOT) of Storm? We
updated Zookeeper
> Continuously worker EventThread shut down when storm is running
> ---
>
> Key: STORM-3882
> URL: https://issues.apache.org/jira/browse/STORM-3882
> Project: Apache Storm
> Issue Type: Bug
> Components: storm-server
>Affects Versions: 2.4.0
>Reporter: ben
>Priority: Major
>
> Hi everyone,
>
> I have deployed a storm 2.4.0 cluster on my dev machine. However, when I look
> up the worker's log, I found that every half minute, there is a continuously
> zookeeper shutdown phenomenon.
>
> While I have listened the zookeeper port, the connection number is remain the
> same in a long period of time, which represents that the connection between
> storm nimbus and zookeeper is stable.
>
> The log record is attached as below, may I know why this zookeeper shut down
> phenomenon happens? And is it means something failed or it is a normal thing?
>
> Thx!
>
> {code:java}
> 2022-09-19 23:01:28.475 o.a.s.z.ClientZookeeper main [INFO] Starting ZK
> Curator
> 2022-09-19 23:01:28.476 o.a.s.s.o.a.c.f.i.CuratorFrameworkImpl main [INFO]
> Starting
> 2022-09-19 23:01:28.493 o.a.s.s.o.a.z.ZooKeeper main [INFO] Initiating client
> connection, connectString=127.0.0.1:2182 sessionTimeout=2
> watcher=org.apache.storm.shade.org.apache.curator.ConnectionState@528c868
> 2022-09-19 23:01:28.507 o.a.s.s.o.a.z.c.X509Util main [INFO] Setting -D
> jdk.tls.rejectClientInitiatedRenegotiation=true to disable client-initiated
> TLS renegotiation
> 2022-09-19 23:01:28.524 o.a.s.s.o.a.z.ClientCnxnSocket main [INFO]
> jute.maxbuffer value is 4194304 Bytes
> 2022-09-19 23:01:28.539 o.a.s.s.o.a.z.ClientCnxn main [INFO]
> zookeeper.request.timeout value is 0. feature enabled=
> 2022-09-19 23:01:28.561 o.a.s.s.o.a.c.f.i.CuratorFrameworkImpl main [INFO]
> Default schema
> 2022-09-19 23:01:28.564 o.a.s.s.o.a.z.ClientCnxn
> main-SendThread(127.0.0.1:2182) [INFO] Opening socket connection to server
> VM-24-50-centos/127.0.0.1:2182. Will not attempt to authenticate using SASL
> (unknown error)
> 2022-09-19 23:01:28.575 o.a.s.s.o.a.z.ClientCnxn
> main-SendThread(127.0.0.1:2182) [INFO] Socket connection established,
> initiating session, client: /127.0.0.1:51751, server:
> VM-24-50-centos/127.0.0.1:2182
> 2022-09-19 23:01:28.585 o.a.s.s.o.a.z.ClientCnxn
> main-SendThread(127.0.0.1:2182) [INFO] Session establishment complete on
> server VM-24-50-centos/127.0.0.1:2182, sessionid = 0x10b2a6dab680068,
> negotiated timeout = 2
> 2022-09-19 23:01:28.591 o.a.s.s.o.a.c.f.s.ConnectionStateManager
> main-EventThread [INFO] State change: CONNECTED
> 2022-09-19 23:01:28.619 o.a.s.s.o.a.c.f.i.EnsembleTracker main-EventThread
> [INFO] New config event received: {}
> 2022-09-19 23:01:28.620 o.a.s.s.o.a.c.f.i.EnsembleTracker main-EventThread
> [INFO] New config event received: {}
> 2022-09-19 23:01:28.625 o.a.s.s.o.a.c.f.i.CuratorFrameworkImpl
> Curator-Framework-0 [INFO] backgroundOperationsLoop exiting
> 2022-09-19 23:01:28.735 o.a.s.s.o.a.z.ZooKeeper main [INFO] Session:
> 0x10b2a6dab680068 closed
> 2022-09-19 23:01:28.735 o.a.s.s.o.a.z.ClientCnxn main-EventThread [INFO]
> EventThread shut down for session: 0x10b2a6dab680068 {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (STORM-3919) Upgrade Hadoop to version 3
[ https://issues.apache.org/jira/browse/STORM-3919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17758999#comment-17758999 ] Richard Zowalla commented on STORM-3919: This might impact the auth part of Storm > Upgrade Hadoop to version 3 > --- > > Key: STORM-3919 > URL: https://issues.apache.org/jira/browse/STORM-3919 > Project: Apache Storm > Issue Type: Improvement > Components: storm-core >Reporter: Bipin Prasad >Priority: Major > > There are several fixes and enhancements in Hadoop version 3.0.0 that Storm > can benefit from. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (STORM-3924) Support for declaring WorkerHook in Flux topology definitions
[ https://issues.apache.org/jira/browse/STORM-3924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla resolved STORM-3924. Fix Version/s: 2.6.0 Assignee: (was: Bipin Prasad) Resolution: Fixed > Support for declaring WorkerHook in Flux topology definitions > - > > Key: STORM-3924 > URL: https://issues.apache.org/jira/browse/STORM-3924 > Project: Apache Storm > Issue Type: Bug > Components: Flux >Reporter: Bipin Prasad >Priority: Minor > Fix For: 2.6.0 > > Time Spent: 1h 50m > Remaining Estimate: 0h > > Support for declaring WorkerHook in TopologyBuilder was added. Related JIRA: > https://issues.apache.org/jira/browse/STORM-126 (related PR: > [#884|https://github.com/apache/storm/pull/884]). > > Add support for the aforementioned feature for topology definitions submitted > as Flux yaml. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (STORM-3924) Support for declaring WorkerHook in Flux topology definitions
[ https://issues.apache.org/jira/browse/STORM-3924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla closed STORM-3924. -- > Support for declaring WorkerHook in Flux topology definitions > - > > Key: STORM-3924 > URL: https://issues.apache.org/jira/browse/STORM-3924 > Project: Apache Storm > Issue Type: Bug > Components: Flux >Reporter: Bipin Prasad >Priority: Minor > Fix For: 2.6.0 > > Time Spent: 1h 50m > Remaining Estimate: 0h > > Support for declaring WorkerHook in TopologyBuilder was added. Related JIRA: > https://issues.apache.org/jira/browse/STORM-126 (related PR: > [#884|https://github.com/apache/storm/pull/884]). > > Add support for the aforementioned feature for topology definitions submitted > as Flux yaml. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (STORM-3932) Fix errors/warnings found while generating javadoc in storm-client
[
https://issues.apache.org/jira/browse/STORM-3932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Zowalla updated STORM-3932:
---
Summary: Fix errors/warnings found while generating javadoc in storm-client
(was: Fix errors/warnings found while generating javadoc)
> Fix errors/warnings found while generating javadoc in storm-client
> --
>
> Key: STORM-3932
> URL: https://issues.apache.org/jira/browse/STORM-3932
> Project: Apache Storm
> Issue Type: Task
> Components: storm-client
>Reporter: Bipin Prasad
>Assignee: Bipin Prasad
>Priority: Minor
>
> In Storm-client
> {code:java}
> [INFO] [WARNING] Javadoc Warnings
> [INFO] [WARNING]
> ./storm/storm-client/src/jvm/org/apache/storm/utils/DefaultShellLogHandler.java:51:
> warning - Tag @see:illegal character: "123" in "{@link
> ShellLogHandler#setUpContext}"
> [INFO] [WARNING]
> ./storm/storm-client/src/jvm/org/apache/storm/utils/DefaultShellLogHandler.java:51:
> warning - Tag @see:illegal character: "64" in "{@link
> ShellLogHandler#setUpContext}"
> [INFO] [WARNING]
> ./storm/storm-client/src/jvm/org/apache/storm/utils/DefaultShellLogHandler.java:66:
> warning - Tag @see:illegal character: "123" in "{@link ShellLogHandler#log}"
> [INFO] [WARNING]
> ./storm/storm-client/src/jvm/org/apache/storm/utils/DefaultShellLogHandler.java:66:
> warning - Tag @see:illegal character: "64" in "{@link ShellLogHandler#log}"
> [INFO] [WARNING]
> ./storm/storm-client/src/jvm/org/apache/storm/Config.java:139: warning -
> @deprecated: is an unknown tag.
> [INFO] [WARNING]
> ./storm/storm-client/src/jvm/org/apache/storm/Config.java:875: warning -
> Tag @link: reference not found:
> org.apache.storm.scheduler.multitenant.MultitenantScheduler
> [INFO] [WARNING]
> ./storm/storm-client/src/jvm/org/apache/storm/Config.java:875: warning -
> Tag @link: reference not found:
> org.apache.storm.scheduler.multitenant.MultitenantScheduler
> [INFO] [WARNING]
> ./storm/storm-client/src/jvm/org/apache/storm/Config.java:875: warning -
> Tag @link: reference not found:
> org.apache.storm.scheduler.resource.ResourceAwareScheduler
> [INFO] [WARNING]
> ./storm/storm-client/src/jvm/org/apache/storm/Config.java:875: warning -
> Tag @link: reference not found:
> org.apache.storm.scheduler.resource.strategies.scheduling.RoundRobinResourceAwareStrategy
> [INFO] [WARNING]
> ./storm/storm-client/src/jvm/org/apache/storm/Config.java:1275: warning -
> @Deprecated is an unknown tag -- same as a known tag except for case.
> [INFO] [WARNING]
> ./storm/storm-client/src/jvm/org/apache/storm/Config.java:1282: warning -
> @Deprecated is an unknown tag -- same as a known tag except for case.
> [INFO] [WARNING]
> ./storm/storm-client/src/jvm/org/apache/storm/ILocalCluster.java:82:
> warning - @param argument "topologyName" is not a parameter name.
> [INFO] [WARNING]
> ./storm/storm-client/src/jvm/org/apache/storm/ILocalCluster.java:206:
> warning - @param argument "steps" is not a parameter name.
> [INFO] [WARNING]
> ./storm/storm-client/src/jvm/org/apache/storm/topology/TopologyBuilder.java:319:
> warning - @param argument "T" is not a parameter name.
> [INFO] [WARNING]
> ./storm/storm-client/src/jvm/org/apache/storm/topology/TopologyBuilder.java:339:
> warning - @param argument "T" is not a parameter name.
> [INFO] [WARNING]
> ./storm/storm-client/src/jvm/org/apache/storm/cluster/IStateStorage.java:69:
> warning - @return tag cannot be used in method with void return type.
> [INFO] [WARNING]
> ./storm/storm-client/src/jvm/org/apache/storm/cluster/IStormClusterState.java:68:
> warning - Tag @link: reference not found: LeaderListenerCallback
> [INFO] [WARNING]
> ./storm/storm-client/src/jvm/org/apache/storm/cluster/IStormClusterState.java:68:
> warning - Tag @link: reference not found: LeaderListenerCallback
> [INFO] [WARNING]
> ./storm/storm-client/src/jvm/org/apache/storm/cluster/IStormClusterState.java:156:
> warning - @deprecated: is an unknown tag.
> [INFO] [WARNING]
> ./storm/storm-client/src/jvm/org/apache/storm/cluster/IStormClusterState.java:184:
> warning - @deprecated: is an unknown tag.
> [INFO] [WARNING]
> ./storm/storm-client/src/jvm/org/apache/storm/cluster/IStormClusterState.java:191:
> warning - @deprecated: is an unknown tag.
> [INFO] [WARNING]
> ./storm/storm-client/src/jvm/org/apache/storm/cluster/IStormClusterState.java:198:
> warning - @deprecated: is an unknown tag.
> [INFO] [WARNING]
> ./storm/storm-client/src/jvm/org/apache/storm/cluster/IStormClusterState.java:205:
> warning - @deprecated: is an unknown tag.
> [INFO] [WARNING]
> ./storm/storm-client/src/jvm/org/apache/storm/cluster/IStormClusterState.java:68:
>
[jira] [Assigned] (STORM-3958) Capacity to set Storm UI's title in conf/storm.yaml
[
https://issues.apache.org/jira/browse/STORM-3958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Zowalla reassigned STORM-3958:
--
Assignee: Alexandre Vermeerbergen
> Capacity to set Storm UI's title in conf/storm.yaml
> ---
>
> Key: STORM-3958
> URL: https://issues.apache.org/jira/browse/STORM-3958
> Project: Apache Storm
> Issue Type: New Feature
> Components: storm-ui
>Reporter: Alexandre Vermeerbergen
>Assignee: Alexandre Vermeerbergen
>Priority: Minor
> Fix For: 2.6.0
>
>
> I have several Storm clusters to manage (integration test cluster,
> pre-production ones, QA, several productions), and I always find disturbing
> to have the same "Storm UI" title in my web browser's tabs for the Storm UI
> of all these different environments.
> I know it's trivial to update the content of {{public/index.html }}to change
> the {{Storm UI}} line to whatever I'd like, but I feel it
> would be cleaner to have the possibility to set this title in
> {{conf/storm.yaml}} file, for example with {{ui.title}} key.
> Of course {{conf/defaults.yaml}} would need to have an extra line with:
> {{ui.title: "Storm UI"}}
> to avoid any regression for anyone not willing to customize Storm UI's title.
> Also I think that, for consistency, this other place in {{public/index.html}}
> where 'Storm UI' can be found should also get its value from {{ui.title}} key:
> {{ }}
> {{ Storm UI}}
> {{ }}
> If there is no objection to this proposal, then I could self-assign this task.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (STORM-3956) Fix cli monitor component's argument type
[ https://issues.apache.org/jira/browse/STORM-3956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla closed STORM-3956. -- Resolution: Fixed > Fix cli monitor component's argument type > -- > > Key: STORM-3956 > URL: https://issues.apache.org/jira/browse/STORM-3956 > Project: Apache Storm > Issue Type: Bug >Affects Versions: 2.3.0 >Reporter: Richard Zowalla >Priority: Minor > Fix For: 2.6.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > From https://github.com/apache/storm/pull/3423 > The `component` value is a string, not a number, see > [Monitor.java](https://github.com/apache/storm/blob/master/storm-core/src/jvm/org/apache/storm/utils/Monitor.java#L156). > Attempting to use a number throws a stacktrace like such: > ``` > ~/apache-storm-2.3.0/bin/storm monitor -m wordGenerator production-topology > topology component parallelism stream time-diff msemitted > throughput (Kt/s) > Available components for production-topology : > -- > __acker > wordGenerator > intermediateRanker > counter > finalRanker > -- > Exception in thread "main" java.lang.IllegalArgumentException: component: > wordGeneratotor not found > at org.apache.storm.utils.Monitor.metrics(Monitor.java:128) > at org.apache.storm.utils.Monitor.metrics(Monitor.java:83) > at org.apache.storm.command.Monitor$1.run(Monitor.java:53) > at > org.apache.storm.utils.NimbusClient.withConfiguredClient(NimbusClient.java:128) > at > org.apache.storm.utils.NimbusClient.withConfiguredClient(NimbusClient.java:117) > at org.apache.storm.command.Monitor.main(Monitor.java:50) > ``` -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (STORM-3958) Capacity to set Storm UI's title in conf/storm.yaml
[
https://issues.apache.org/jira/browse/STORM-3958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Zowalla updated STORM-3958:
---
Fix Version/s: 2.6.0
> Capacity to set Storm UI's title in conf/storm.yaml
> ---
>
> Key: STORM-3958
> URL: https://issues.apache.org/jira/browse/STORM-3958
> Project: Apache Storm
> Issue Type: New Feature
> Components: storm-ui
>Reporter: Alexandre Vermeerbergen
>Priority: Minor
> Fix For: 2.6.0
>
>
> I have several Storm clusters to manage (integration test cluster,
> pre-production ones, QA, several productions), and I always find disturbing
> to have the same "Storm UI" title in my web browser's tabs for the Storm UI
> of all these different environments.
> I know it's trivial to update the content of {{public/index.html }}to change
> the {{Storm UI}} line to whatever I'd like, but I feel it
> would be cleaner to have the possibility to set this title in
> {{conf/storm.yaml}} file, for example with {{ui.title}} key.
> Of course {{conf/defaults.yaml}} would need to have an extra line with:
> {{ui.title: "Storm UI"}}
> to avoid any regression for anyone not willing to customize Storm UI's title.
> Also I think that, for consistency, this other place in {{public/index.html}}
> where 'Storm UI' can be found should also get its value from {{ui.title}} key:
> {{ }}
> {{ Storm UI}}
> {{ }}
> If there is no objection to this proposal, then I could self-assign this task.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (STORM-2428) Flux-core jar contains unpacked dependencies
[ https://issues.apache.org/jira/browse/STORM-2428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17758857#comment-17758857 ] Richard Zowalla commented on STORM-2428: Current Storm 2 SNAPSHOT only shades commons cli and snakeyaml. > Flux-core jar contains unpacked dependencies > > > Key: STORM-2428 > URL: https://issues.apache.org/jira/browse/STORM-2428 > Project: Apache Storm > Issue Type: Bug > Components: Flux >Affects Versions: 1.1.0, 1.0.3, 1.2.1, 1.2.2 >Reporter: Julien Nioche >Priority: Major > > The jar file for flux-core contains classes from /org/apache/http/. This was > not the case before and causes problems with projects which rely on a > different version of http-client. > I can't see any references to http-client in the pom though. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (STORM-3959) Add Matomo Tracking to Website
[ https://issues.apache.org/jira/browse/STORM-3959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla closed STORM-3959. -- Resolution: Fixed > Add Matomo Tracking to Website > -- > > Key: STORM-3959 > URL: https://issues.apache.org/jira/browse/STORM-3959 > Project: Apache Storm > Issue Type: Improvement >Reporter: Richard Zowalla >Assignee: Richard Zowalla >Priority: Major > Time Spent: 0.5h > Remaining Estimate: 0h > > ASF as a privacy-conform matomo instance for analytics. We should add it to > the website to see how often Storm website is actually used to download > stuff, etc. -- This message was sent by Atlassian Jira (v8.20.10#820010)
