[jira] [Created] (STORM-3982) Update README.md, DOAP/RDF and Dev section in POM
Richard Zowalla created STORM-3982: -- Summary: Update README.md, DOAP/RDF and Dev section in POM Key: STORM-3982 URL: https://issues.apache.org/jira/browse/STORM-3982 Project: Apache Storm Issue Type: Documentation Reporter: Richard Zowalla Assignee: Richard Zowalla Fix For: 2.6.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (STORM-3981) Negative Acknowledge not implemented for Pulsar Storm Adapter
Karunam goyal created STORM-3981:
Summary: Negative Acknowledge not implemented for Pulsar Storm
Adapter
Key: STORM-3981
URL: https://issues.apache.org/jira/browse/STORM-3981
Project: Apache Storm
Issue Type: Bug
Reporter: Karunam goyal
[https://github.com/apache/storm/blob/a837e6add1fee99115eb426077f6e62fd406eea2/external/storm-pulsar/src/main/java/org/apache/pulsar/storm/PulsarSpout.java]
v2.11.0 pulsar-storm
There is no way to negatively acknowledge the consumer and the registry method
for DeadLetterPolicy is broken
{{ConsumerConfigurationData subscriptionConfig = new
ConsumerConfigurationData<>();
subscriptionConfig.setSubscriptionInitialPosition(SubscriptionInitialPosition.Earliest);
subscriptionConfig.setSubscriptionType(SubscriptionType.Shared);
subscriptionConfig.setDeadLetterPolicy(DeadLetterPolicy.builder()
.deadLetterTopic(viestiSourceConfig.getDeadLetterTopic()).build());}}
{{PulsarSpoutV2 pulsarSpout = new PulsarSpoutV2( spoutConfiguration,
((ClientBuilderImpl) createBuilder(viestiSourceConfig))
.getClientConfigurationData() .clone(), subscriptionConfig);}}
This above code doesnt stick while creating PulsarSpout.
{{static class SpoutConsumer implements PulsarSpoutConsumer {}}
{{private Consumer consumer;}}
{{public SpoutConsumer(Consumer consumer) \{
this.consumer = consumer;
}
public Message receive(int timeout, TimeUnit unit) throws
PulsarClientException \{
return this.consumer.receive(timeout, unit);
}
public void acknowledgeAsync(Message msg) \{
this.consumer.acknowledgeAsync(msg);
}
public void close() throws PulsarClientException \{
this.consumer.close();
}
public void unsubscribe() throws PulsarClientException \{
this.consumer.unsubscribe();
}
}}}
Also there is no Mechanism to negativelyAcknowledge a message.
*Expected behavior*
While Setting DeadletterPolicy It should not drop it while serialising.
Negative Acks support should be there
*Desktop (please complete the following information):*
MacOs Ventura 13.4.1
java version "1.8.0_333"
Java(TM) SE Runtime Environment (build 1.8.0_333-b02)
Java HotSpot(TM) 64-Bit Server VM (build 25.333-b02, mixed mode)
Apache Storm 2.2.1
Trying to consume from Pulsar Topic in Apache Storm
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (STORM-3980) Updates developer docs and removing obsolete content
[ https://issues.apache.org/jira/browse/STORM-3980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla closed STORM-3980. -- Resolution: Fixed > Updates developer docs and removing obsolete content > - > > Key: STORM-3980 > URL: https://issues.apache.org/jira/browse/STORM-3980 > Project: Apache Storm > Issue Type: Improvement >Affects Versions: 2.5.0 >Reporter: Richard Zowalla >Assignee: Richard Zowalla >Priority: Major > Fix For: 2.6.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (STORM-3980) Updates developer docs and removing obsolete content
Richard Zowalla created STORM-3980: -- Summary: Updates developer docs and removing obsolete content Key: STORM-3980 URL: https://issues.apache.org/jira/browse/STORM-3980 Project: Apache Storm Issue Type: Improvement Affects Versions: 2.5.0 Reporter: Richard Zowalla Assignee: Richard Zowalla Fix For: 2.6.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (STORM-2708) View Logs by single point. With using Docker swarm
[ https://issues.apache.org/jira/browse/STORM-2708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julien Nioche resolved STORM-2708. -- Resolution: Duplicate > View Logs by single point. With using Docker swarm > -- > > Key: STORM-2708 > URL: https://issues.apache.org/jira/browse/STORM-2708 > Project: Apache Storm > Issue Type: Question >Reporter: Ivan >Priority: Major > Attachments: Screenshot from 2017-08-26 22-04-44.png, Screenshot from > 2017-08-26 22-05-29.png, Screenshot from 2017-08-26 22-06-09.png > > > Use Storm on Docker swarm system and I should debugging system. I need get > log information from whole storm system by single point. I can get log-file > from host machines where deployed containers, but i want use easy single > access point. > I know about storm logviewer, I think it is that what I need. But I cant tune > system. > I see docker containers like: a63c6da1dc17, fe2efd0149b4 (you can see at > Screenshot from 2017-08-26 22-04-44.png) > I can income to this host and see something like Screenshot from 2017-08-26 > 22-05-29.png > When I click "log" link (fe2efd0149b4 (log)) i get Screenshot from 2017-08-26 > 22-06-09.png > How I can get logs, search in logs from storm system with use Docker? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (STORM-3979) JUnit 5.10.0
Richard Zowalla created STORM-3979: -- Summary: JUnit 5.10.0 Key: STORM-3979 URL: https://issues.apache.org/jira/browse/STORM-3979 Project: Apache Storm Issue Type: Dependency upgrade Affects Versions: 2.5.0 Reporter: Richard Zowalla Assignee: Richard Zowalla Fix For: 2.6.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (STORM-3979) JUnit 5.10.0
[ https://issues.apache.org/jira/browse/STORM-3979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla closed STORM-3979. -- Resolution: Fixed done in https://issues.apache.org/jira/browse/STORM-3961 > JUnit 5.10.0 > > > Key: STORM-3979 > URL: https://issues.apache.org/jira/browse/STORM-3979 > Project: Apache Storm > Issue Type: Dependency upgrade >Affects Versions: 2.5.0 >Reporter: Richard Zowalla >Assignee: Richard Zowalla >Priority: Major > Fix For: 2.6.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (STORM-3977) Minidev JSON 2.5.0
Richard Zowalla created STORM-3977: -- Summary: Minidev JSON 2.5.0 Key: STORM-3977 URL: https://issues.apache.org/jira/browse/STORM-3977 Project: Apache Storm Issue Type: Dependency upgrade Affects Versions: 2.5.0 Reporter: Richard Zowalla Assignee: Richard Zowalla Fix For: 2.6.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (STORM-3976) j2html 1.6.0
[ https://issues.apache.org/jira/browse/STORM-3976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla closed STORM-3976. -- Resolution: Fixed done in https://issues.apache.org/jira/browse/STORM-3961 > j2html 1.6.0 > > > Key: STORM-3976 > URL: https://issues.apache.org/jira/browse/STORM-3976 > Project: Apache Storm > Issue Type: Dependency upgrade >Affects Versions: 2.5.0 >Reporter: Richard Zowalla >Assignee: Richard Zowalla >Priority: Major > Fix For: 2.6.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (STORM-3978) Rep,ace json-simple with minidev json
[ https://issues.apache.org/jira/browse/STORM-3978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla closed STORM-3978. -- Resolution: Fixed done in https://issues.apache.org/jira/browse/STORM-3961 > Rep,ace json-simple with minidev json > - > > Key: STORM-3978 > URL: https://issues.apache.org/jira/browse/STORM-3978 > Project: Apache Storm > Issue Type: Task >Affects Versions: 2.5.0 >Reporter: Richard Zowalla >Assignee: Richard Zowalla >Priority: Major > Fix For: 2.6.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (STORM-3978) Rep,ace json-simple with minidev json
Richard Zowalla created STORM-3978: -- Summary: Rep,ace json-simple with minidev json Key: STORM-3978 URL: https://issues.apache.org/jira/browse/STORM-3978 Project: Apache Storm Issue Type: Task Affects Versions: 2.5.0 Reporter: Richard Zowalla Assignee: Richard Zowalla Fix For: 2.6.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (STORM-3977) Minidev JSON 2.5.0
[ https://issues.apache.org/jira/browse/STORM-3977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla closed STORM-3977. -- Resolution: Fixed done in https://issues.apache.org/jira/browse/STORM-3961 > Minidev JSON 2.5.0 > -- > > Key: STORM-3977 > URL: https://issues.apache.org/jira/browse/STORM-3977 > Project: Apache Storm > Issue Type: Dependency upgrade >Affects Versions: 2.5.0 >Reporter: Richard Zowalla >Assignee: Richard Zowalla >Priority: Major > Fix For: 2.6.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (STORM-3975) Dropwizard 1.3.29
Richard Zowalla created STORM-3975: -- Summary: Dropwizard 1.3.29 Key: STORM-3975 URL: https://issues.apache.org/jira/browse/STORM-3975 Project: Apache Storm Issue Type: Dependency upgrade Affects Versions: 2.5.0 Reporter: Richard Zowalla Assignee: Richard Zowalla Fix For: 2.6.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (STORM-3974) Jersey 2.40
[ https://issues.apache.org/jira/browse/STORM-3974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla closed STORM-3974. -- Resolution: Fixed done in https://issues.apache.org/jira/browse/STORM-3961 > Jersey 2.40 > --- > > Key: STORM-3974 > URL: https://issues.apache.org/jira/browse/STORM-3974 > Project: Apache Storm > Issue Type: Dependency upgrade >Affects Versions: 2.5.0 >Reporter: Richard Zowalla >Assignee: Richard Zowalla >Priority: Major > Fix For: 2.6.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (STORM-3976) j2html 1.6.0
Richard Zowalla created STORM-3976: -- Summary: j2html 1.6.0 Key: STORM-3976 URL: https://issues.apache.org/jira/browse/STORM-3976 Project: Apache Storm Issue Type: Dependency upgrade Affects Versions: 2.5.0 Reporter: Richard Zowalla Assignee: Richard Zowalla Fix For: 2.6.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (STORM-3974) Jersey 2.40
Richard Zowalla created STORM-3974: -- Summary: Jersey 2.40 Key: STORM-3974 URL: https://issues.apache.org/jira/browse/STORM-3974 Project: Apache Storm Issue Type: Dependency upgrade Affects Versions: 2.5.0 Reporter: Richard Zowalla Assignee: Richard Zowalla Fix For: 2.6.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (STORM-3975) Dropwizard 1.3.29
[ https://issues.apache.org/jira/browse/STORM-3975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla closed STORM-3975. -- Resolution: Fixed done in https://issues.apache.org/jira/browse/STORM-3961 > Dropwizard 1.3.29 > - > > Key: STORM-3975 > URL: https://issues.apache.org/jira/browse/STORM-3975 > Project: Apache Storm > Issue Type: Dependency upgrade >Affects Versions: 2.5.0 >Reporter: Richard Zowalla >Assignee: Richard Zowalla >Priority: Major > Fix For: 2.6.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (STORM-3973) log4j2 2.20.0
Richard Zowalla created STORM-3973: -- Summary: log4j2 2.20.0 Key: STORM-3973 URL: https://issues.apache.org/jira/browse/STORM-3973 Project: Apache Storm Issue Type: Dependency upgrade Affects Versions: 2.5.0 Reporter: Richard Zowalla Assignee: Richard Zowalla Fix For: 2.6.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (STORM-3973) log4j2 2.20.0
[ https://issues.apache.org/jira/browse/STORM-3973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla closed STORM-3973. -- Resolution: Fixed done in https://issues.apache.org/jira/browse/STORM-3961 > log4j2 2.20.0 > - > > Key: STORM-3973 > URL: https://issues.apache.org/jira/browse/STORM-3973 > Project: Apache Storm > Issue Type: Dependency upgrade >Affects Versions: 2.5.0 >Reporter: Richard Zowalla >Assignee: Richard Zowalla >Priority: Major > Fix For: 2.6.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (STORM-3972) commons-lang3 3.13.0
[ https://issues.apache.org/jira/browse/STORM-3972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17761626#comment-17761626 ] Richard Zowalla commented on STORM-3972: done in https://issues.apache.org/jira/browse/STORM-3961 > commons-lang3 3.13.0 > > > Key: STORM-3972 > URL: https://issues.apache.org/jira/browse/STORM-3972 > Project: Apache Storm > Issue Type: Dependency upgrade >Affects Versions: 2.5.0 >Reporter: Richard Zowalla >Assignee: Richard Zowalla >Priority: Major > Fix For: 2.6.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (STORM-3972) commons-lang3 3.13.0
[ https://issues.apache.org/jira/browse/STORM-3972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla closed STORM-3972. -- Resolution: Fixed > commons-lang3 3.13.0 > > > Key: STORM-3972 > URL: https://issues.apache.org/jira/browse/STORM-3972 > Project: Apache Storm > Issue Type: Dependency upgrade >Affects Versions: 2.5.0 >Reporter: Richard Zowalla >Assignee: Richard Zowalla >Priority: Major > Fix For: 2.6.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (STORM-3972) commons-lang3 3.13.0
Richard Zowalla created STORM-3972: -- Summary: commons-lang3 3.13.0 Key: STORM-3972 URL: https://issues.apache.org/jira/browse/STORM-3972 Project: Apache Storm Issue Type: Dependency upgrade Affects Versions: 2.5.0 Reporter: Richard Zowalla Assignee: Richard Zowalla Fix For: 2.6.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (STORM-3961) Modernize Storm UI's 3rd party dependencies
[ https://issues.apache.org/jira/browse/STORM-3961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla closed STORM-3961. -- Fix Version/s: 2.6.0 Resolution: Fixed > Modernize Storm UI's 3rd party dependencies > --- > > Key: STORM-3961 > URL: https://issues.apache.org/jira/browse/STORM-3961 > Project: Apache Storm > Issue Type: Dependency upgrade >Affects Versions: 2.5.0 >Reporter: Richard Zowalla >Assignee: Richard Zowalla >Priority: Major > Fix For: 2.6.0 > > Time Spent: 1h > Remaining Estimate: 0h > > Java dependencies only. > Bootstrap / JQuery etc are a separate topic. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (STORM-3970) storm-sql-core in fails to build Eclipse for generated java code
[ https://issues.apache.org/jira/browse/STORM-3970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla closed STORM-3970. -- Fix Version/s: 2.6.0 Resolution: Fixed > storm-sql-core in fails to build Eclipse for generated java code > > > Key: STORM-3970 > URL: https://issues.apache.org/jira/browse/STORM-3970 > Project: Apache Storm > Issue Type: Task > Components: build >Reporter: Bipin Prasad >Assignee: Bipin Prasad >Priority: Major > Fix For: 2.6.0 > > > storm-sql-core extract Parser.jj and then uses javacc to generate java > classes which are then used in the project. > Eclipse does not seem to generate/add these generated classes - leading to > errors. > The project builds properly externally using maven commands. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (STORM-3971) Storm-cassandra shows errors in Eclipse
Bipin Prasad created STORM-3971: --- Summary: Storm-cassandra shows errors in Eclipse Key: STORM-3971 URL: https://issues.apache.org/jira/browse/STORM-3971 Project: Apache Storm Issue Type: Task Components: build Reporter: Bipin Prasad Assignee: Bipin Prasad Errors in Eclipse as reported by Alexandre Vermeerbergen On Thursday, August 31, 2023 at 06:15:55 AM PDT, First set of errors is very strange: in /storm-cassandra/src/test/java/org/apache/storm/cassandra/trident/WeatherBatchSpout.java, I have these imports: import java.util.ArrayList; import java.util.HashMap; import java.util.List; import java.util.Map; import java.util.Random; import java.util.UUID; with all the same errror: "The package java.util is accessible from more than one module: , java.base" => this look like an issue with the notion of Java modules -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (STORM-3970) storm-sql-core in fails to build Eclipse for generated java code
Bipin Prasad created STORM-3970: --- Summary: storm-sql-core in fails to build Eclipse for generated java code Key: STORM-3970 URL: https://issues.apache.org/jira/browse/STORM-3970 Project: Apache Storm Issue Type: Task Components: build Reporter: Bipin Prasad Assignee: Bipin Prasad storm-sql-core extract Parser.jj and then uses javacc to generate java classes which are then used in the project. Eclipse does not seem to generate/add these generated classes - leading to errors. The project builds properly externally using maven commands. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (STORM-3888) HdfsBlobStoreFile set wrong permission for file
[
https://issues.apache.org/jira/browse/STORM-3888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Zowalla resolved STORM-3888.
Fix Version/s: 2.6.0
Resolution: Fixed
> HdfsBlobStoreFile set wrong permission for file
> ---
>
> Key: STORM-3888
> URL: https://issues.apache.org/jira/browse/STORM-3888
> Project: Apache Storm
> Issue Type: Improvement
> Components: blobstore
>Reporter: Zhang Dongsheng
>Priority: Critical
> Fix For: 2.6.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> {code:java}
> public OutputStream getOutputStream() throws IOException {
> FsPermission fileperms = new FsPermission(BLOBSTORE_FILE_PERMISSION);
> try {
> out = fileSystem.create(path, (short)
> this.getMetadata().get_replication_factor());
> fileSystem.setPermission(path, fileperms);
> fileSystem.setReplication(path, (short)
> this.getMetadata().get_replication_factor());
> } catch (IOException e) {
>..
> out = fileSystem.create(path, (short)
> this.getMetadata().get_replication_factor());
> fileSystem.setPermission(path, dirperms);
> fileSystem.setReplication(path, (short)
> this.getMetadata().get_replication_factor());
> }
> ..
> }
> {code}
> We can see that there are permission settings for path in both try and catch,
> but the permission in catch is different from that in try. In catch, the
> permission `dirperms` is given to the file. I think there is a problem here,
> and it should be the same as The permissions in try are consistent.
> Permissions should be set according to the following code
> {code:java}
> public OutputStream getOutputStream() throws IOException {
> FsPermission fileperms = new FsPermission(BLOBSTORE_FILE_PERMISSION);
> try {
> out = fileSystem.create(path, (short)
> this.getMetadata().get_replication_factor());
> fileSystem.setPermission(path, fileperms);
> fileSystem.setReplication(path, (short)
> this.getMetadata().get_replication_factor());
> } catch (IOException e) {
>..
> out = fileSystem.create(path, (short)
> this.getMetadata().get_replication_factor());
> fileSystem.setPermission(path, fileperms);
> fileSystem.setReplication(path, (short)
> this.getMetadata().get_replication_factor());
> }
> ..
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (STORM-3888) HdfsBlobStoreFile set wrong permission for file
[
https://issues.apache.org/jira/browse/STORM-3888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Zowalla closed STORM-3888.
--
> HdfsBlobStoreFile set wrong permission for file
> ---
>
> Key: STORM-3888
> URL: https://issues.apache.org/jira/browse/STORM-3888
> Project: Apache Storm
> Issue Type: Improvement
> Components: blobstore
>Reporter: Zhang Dongsheng
>Priority: Critical
> Fix For: 2.6.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> {code:java}
> public OutputStream getOutputStream() throws IOException {
> FsPermission fileperms = new FsPermission(BLOBSTORE_FILE_PERMISSION);
> try {
> out = fileSystem.create(path, (short)
> this.getMetadata().get_replication_factor());
> fileSystem.setPermission(path, fileperms);
> fileSystem.setReplication(path, (short)
> this.getMetadata().get_replication_factor());
> } catch (IOException e) {
>..
> out = fileSystem.create(path, (short)
> this.getMetadata().get_replication_factor());
> fileSystem.setPermission(path, dirperms);
> fileSystem.setReplication(path, (short)
> this.getMetadata().get_replication_factor());
> }
> ..
> }
> {code}
> We can see that there are permission settings for path in both try and catch,
> but the permission in catch is different from that in try. In catch, the
> permission `dirperms` is given to the file. I think there is a problem here,
> and it should be the same as The permissions in try are consistent.
> Permissions should be set according to the following code
> {code:java}
> public OutputStream getOutputStream() throws IOException {
> FsPermission fileperms = new FsPermission(BLOBSTORE_FILE_PERMISSION);
> try {
> out = fileSystem.create(path, (short)
> this.getMetadata().get_replication_factor());
> fileSystem.setPermission(path, fileperms);
> fileSystem.setReplication(path, (short)
> this.getMetadata().get_replication_factor());
> } catch (IOException e) {
>..
> out = fileSystem.create(path, (short)
> this.getMetadata().get_replication_factor());
> fileSystem.setPermission(path, fileperms);
> fileSystem.setReplication(path, (short)
> this.getMetadata().get_replication_factor());
> }
> ..
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (STORM-3968) Add missing groupId in storm-core/pom.xml for maven-dependency-plugin
[ https://issues.apache.org/jira/browse/STORM-3968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla closed STORM-3968. -- Fix Version/s: 2.6.0 Resolution: Fixed > Add missing groupId in storm-core/pom.xml for maven-dependency-plugin > - > > Key: STORM-3968 > URL: https://issues.apache.org/jira/browse/STORM-3968 > Project: Apache Storm > Issue Type: Task > Components: build >Reporter: Bipin Prasad >Assignee: Bipin Prasad >Priority: Major > Fix For: 2.6.0 > > Time Spent: 20m > Remaining Estimate: 0h > > In storm-core/pom.xml, missing groupId for maven-dependcy-plugin causes > failure to parse the module in eclipse ide -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (STORM-3967) Set generated sources directory for use by IDE like eclipse
[ https://issues.apache.org/jira/browse/STORM-3967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla closed STORM-3967. -- Fix Version/s: 2.6.0 Resolution: Fixed > Set generated sources directory for use by IDE like eclipse > --- > > Key: STORM-3967 > URL: https://issues.apache.org/jira/browse/STORM-3967 > Project: Apache Storm > Issue Type: Task > Components: build >Reporter: Bipin Prasad >Assignee: Bipin Prasad >Priority: Minor > Fix For: 2.6.0 > > Time Spent: 20m > Remaining Estimate: 0h > > When storm is imported as a maven project into Eclipse, the IDE does not > generate, detect or use the generated sources (example storm-sql-core). > Set the generated sources directory in main pom.xml so that all subprojects > can be successfully imported. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (STORM-3969) Update licenses automatically via (python) script
Bipin Prasad created STORM-3969: --- Summary: Update licenses automatically via (python) script Key: STORM-3969 URL: https://issues.apache.org/jira/browse/STORM-3969 Project: Apache Storm Issue Type: Task Components: build Reporter: Bipin Prasad When dependencies are changed in pom files, one of the github actions checks for licenses. On most changes, this fails as the licenses do not match the "expected" values. Add a (python) script to update license files. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (STORM-3968) Add missing groupId in storm-core/pom.xml for maven-dependency-plugin
Bipin Prasad created STORM-3968: --- Summary: Add missing groupId in storm-core/pom.xml for maven-dependency-plugin Key: STORM-3968 URL: https://issues.apache.org/jira/browse/STORM-3968 Project: Apache Storm Issue Type: Task Components: build Reporter: Bipin Prasad Assignee: Bipin Prasad In storm-core/pom.xml, missing groupId for maven-dependcy-plugin causes failure to parse the module in eclipse ide -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (STORM-3967) Set generated sources directory for use by IDE like eclipse
Bipin Prasad created STORM-3967: --- Summary: Set generated sources directory for use by IDE like eclipse Key: STORM-3967 URL: https://issues.apache.org/jira/browse/STORM-3967 Project: Apache Storm Issue Type: Task Components: build Reporter: Bipin Prasad Assignee: Bipin Prasad When storm is imported as a maven project into Eclipse, the IDE does not generate, detect or use the generated sources (example storm-sql-core). Set the generated sources directory in main pom.xml so that all subprojects can be successfully imported. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (STORM-3966) Remove illegal access warning in JDK11 test of storm-sql-hdfs
[
https://issues.apache.org/jira/browse/STORM-3966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bipin Prasad updated STORM-3966:
Description:
sql/storm-sql-hdfs module test warns about illegal access when run under JDK11.
This is due to the following dependcy tree:
+- org.apache.storm:storm-hdfs:jar:2.6.0-SNAPSHOT:provided
| +- org.apache.hadoop:hadoop-auth:jar:2.10.1:provided
to fix Illegal reflective access by
org.apache.hadoop.security.authentication.util.KerberosUtil
(org.apache.hadoop:hadoop-auth:2.10.1)
to method sun.security.krb5.Config.getInstance() add
"add-opens java.security.jgss/sun.security.krb5=ALL-UNNAMED"
was:
sql/storm-sql-core module test warns about illegal access when run under JDK11.
This is due to the following dependcy tree:
{color:#93a1a1} +- org.apache.calcite:calcite-core:jar:1.16.0:compile{color}
{color:#93a1a1} | +-
org.apache.calcite.avatica:avatica-core:jar:1.11.0:compile{color}
{color:#93a1a1} | | \-
com.google.protobuf:protobuf-java:jar:3.3.0:compile{color}
{color:#93a1a1} {color}
{color:#93a1a1} to fix Illegal reflective access by
com.google.protobuf.UnsafeUtil {color}
{color:#93a1a1} (com.google.protobuf:protobuf-java:3.3.0) to field
java.nio.Buffer.address add{color}
{color:#93a1a1} "add-opens java.base/java.nio=ALL-UNNAMED"{color}
> Remove illegal access warning in JDK11 test of storm-sql-hdfs
> -
>
> Key: STORM-3966
> URL: https://issues.apache.org/jira/browse/STORM-3966
> Project: Apache Storm
> Issue Type: Task
> Components: storm-sql
>Reporter: Bipin Prasad
>Assignee: Bipin Prasad
>Priority: Major
>
> sql/storm-sql-hdfs module test warns about illegal access when run under
> JDK11.
> This is due to the following dependcy tree:
> +- org.apache.storm:storm-hdfs:jar:2.6.0-SNAPSHOT:provided
> | +- org.apache.hadoop:hadoop-auth:jar:2.10.1:provided
> to fix Illegal reflective access by
> org.apache.hadoop.security.authentication.util.KerberosUtil
> (org.apache.hadoop:hadoop-auth:2.10.1)
> to method sun.security.krb5.Config.getInstance() add
> "add-opens java.security.jgss/sun.security.krb5=ALL-UNNAMED"
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (STORM-3966) Remove illegal access warning in JDK11 test of storm-sql-hdfs
Bipin Prasad created STORM-3966:
---
Summary: Remove illegal access warning in JDK11 test of
storm-sql-hdfs
Key: STORM-3966
URL: https://issues.apache.org/jira/browse/STORM-3966
Project: Apache Storm
Issue Type: Task
Components: storm-sql
Reporter: Bipin Prasad
Assignee: Bipin Prasad
sql/storm-sql-core module test warns about illegal access when run under JDK11.
This is due to the following dependcy tree:
{color:#93a1a1} +- org.apache.calcite:calcite-core:jar:1.16.0:compile{color}
{color:#93a1a1} | +-
org.apache.calcite.avatica:avatica-core:jar:1.11.0:compile{color}
{color:#93a1a1} | | \-
com.google.protobuf:protobuf-java:jar:3.3.0:compile{color}
{color:#93a1a1} {color}
{color:#93a1a1} to fix Illegal reflective access by
com.google.protobuf.UnsafeUtil {color}
{color:#93a1a1} (com.google.protobuf:protobuf-java:3.3.0) to field
java.nio.Buffer.address add{color}
{color:#93a1a1} "add-opens java.base/java.nio=ALL-UNNAMED"{color}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (STORM-3965) Remove illegal access warning in JDK11 test of storm-sql-core
Bipin Prasad created STORM-3965:
---
Summary: Remove illegal access warning in JDK11 test of
storm-sql-core
Key: STORM-3965
URL: https://issues.apache.org/jira/browse/STORM-3965
Project: Apache Storm
Issue Type: Task
Components: storm-sql
Reporter: Bipin Prasad
Assignee: Bipin Prasad
sql/storm-sql-core module test warns about illegal access when run under JDK11.
This is due to the following dependcy tree:
{color:#93a1a1} +- org.apache.calcite:calcite-core:jar:1.16.0:compile{color}
{color:#93a1a1} | +-
org.apache.calcite.avatica:avatica-core:jar:1.11.0:compile{color}
{color:#93a1a1} | | \-
com.google.protobuf:protobuf-java:jar:3.3.0:compile{color}
{color:#93a1a1} {color}
{color:#93a1a1} to fix Illegal reflective access by
com.google.protobuf.UnsafeUtil {color}
{color:#93a1a1} (com.google.protobuf:protobuf-java:3.3.0) to field
java.nio.Buffer.address add{color}
{color:#93a1a1} "add-opens java.base/java.nio=ALL-UNNAMED"{color}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (STORM-3964) Remove or Update doap_Storm.rdf
Bipin Prasad created STORM-3964: --- Summary: Remove or Update doap_Storm.rdf Key: STORM-3964 URL: https://issues.apache.org/jira/browse/STORM-3964 Project: Apache Storm Issue Type: Task Reporter: Bipin Prasad Storm project includes a file doap_Storm.rdf. This file has not been updated since 2015. The original doap project server [http://usefulinc.com/ns/doap] is not running. The successor to DOAP seems to be here [https://github.com/ewilderj/doap.] Either update or remove https://github.com/apache/storm/blob/master/doap_Storm.rdf -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (STORM-3963) Import and Build Apache Storm in Eclipse
Bipin Prasad created STORM-3963: --- Summary: Import and Build Apache Storm in Eclipse Key: STORM-3963 URL: https://issues.apache.org/jira/browse/STORM-3963 Project: Apache Storm Issue Type: Task Components: build Reporter: Bipin Prasad Assignee: Bipin Prasad Fix For: 2.6.0 Importing Apache Storm into eclipse, shows a bunch of errors and warnings. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (STORM-3962) Update integration page for Kafka links
Bipin Prasad created STORM-3962: --- Summary: Update integration page for Kafka links Key: STORM-3962 URL: https://issues.apache.org/jira/browse/STORM-3962 Project: Apache Storm Issue Type: Task Reporter: Bipin Prasad [This page refers to storm-kafka|https://storm.apache.org/about/integrates.html]. Instead it should refer to the three submodules for kafka storm-kafka-client storm-kafka-migration storm-kafka-monitor -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (STORM-3761) Apache Storm 2.2.0
[ https://issues.apache.org/jira/browse/STORM-3761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla closed STORM-3761. -- Resolution: Not A Problem Plesae try with 2.5.0. It should now be Python3 ready. > Apache Storm 2.2.0 > -- > > Key: STORM-3761 > URL: https://issues.apache.org/jira/browse/STORM-3761 > Project: Apache Storm > Issue Type: Question > Environment: Linux Mint 20.1 >Reporter: Paul A. Gureghian >Priority: Major > > Does Apache Storm 2.2.0 work with Python 3.8 ? > I get a message saying 'version 2.6 is needed. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (STORM-3823) Release Prep fails in storm-client/test/py/test_storm_cli.py
[ https://issues.apache.org/jira/browse/STORM-3823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla closed STORM-3823. -- Fix Version/s: 2.5.0 Resolution: Fixed > Release Prep fails in storm-client/test/py/test_storm_cli.py > > > Key: STORM-3823 > URL: https://issues.apache.org/jira/browse/STORM-3823 > Project: Apache Storm > Issue Type: Bug >Affects Versions: 2.3.0 >Reporter: Bipin Prasad >Assignee: Bipin Prasad >Priority: Major > Fix For: 2.5.0 > > Time Spent: 40m > Remaining Estimate: 0h > > When running the release preparation script via: > *mvn release:prepare -P dist,rat,externals,examples* > the python test script *storm-client/test/py/test_storm_cli.py* fails because > the command generated by storm.py is slightly different than what the test > script expects. > In particular, directories are added to java classpath with a "/*". This is > correct. > However, the test script does not expect this. > Fix the test script storm-client/test/py/test_storm_cli.py to append "/*" to > directories that contain jar files. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (STORM-3961) Modernize Storm UI's 3rd party dependencies
Richard Zowalla created STORM-3961: -- Summary: Modernize Storm UI's 3rd party dependencies Key: STORM-3961 URL: https://issues.apache.org/jira/browse/STORM-3961 Project: Apache Storm Issue Type: Dependency upgrade Affects Versions: 2.5.0 Reporter: Richard Zowalla Assignee: Richard Zowalla Java dependencies only. Bootstrap / JQuery etc are a separate topic. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (STORM-3935) Fix errors/warnings found while generating javadoc in storm-cassandra
[
https://issues.apache.org/jira/browse/STORM-3935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Zowalla closed STORM-3935.
--
Fix Version/s: 2.6.0
Assignee: Richard Zowalla (was: Bipin Prasad)
Resolution: Fixed
> Fix errors/warnings found while generating javadoc in storm-cassandra
> -
>
> Key: STORM-3935
> URL: https://issues.apache.org/jira/browse/STORM-3935
> Project: Apache Storm
> Issue Type: Task
> Components: storm-cassandra
>Reporter: Bipin Prasad
>Assignee: Richard Zowalla
>Priority: Minor
> Fix For: 2.6.0
>
>
> {code:java}
> [INFO] [WARNING] Javadoc Warnings
> [INFO] [WARNING]
> ./storm/external/storm-cassandra/src/main/java/org/apache/storm/cassandra/context/WorkerCtx.java:73:
> warning - Tag @link: reference not found: T
> [INFO] [WARNING]
> ./storm/external/storm-cassandra/src/main/java/org/apache/storm/cassandra/query/impl/ObjectMapperCqlStatementMapper.java:40:
> warning - Tag @link: reference not found:
> com.datastax.driver.mapping.annotations.Table
> [INFO] [WARNING]
> ./storm/external/storm-cassandra/src/main/java/org/apache/storm/cassandra/query/builder/ObjectMapperCqlStatementMapperBuilder.java:33:
> warning - Tag @link: reference not found:
> com.datastax.driver.mapping.annotations.Table
> [INFO] [WARNING]
> ./storm/external/storm-cassandra/src/main/java/org/apache/storm/cassandra/query/builder/ObjectMapperCqlStatementMapperBuilder.java:33:
> warning - Tag @link: reference not found:
> com.datastax.driver.mapping.annotations.Table
> [INFO] [WARNING]
> ./storm/external/storm-cassandra/src/main/java/org/apache/storm/cassandra/query/impl/ObjectMapperCqlStatementMapper.java:40:
> warning - Tag @link: reference not found:
> com.datastax.driver.mapping.annotations.Table
> [INFO] [WARNING]
> ./storm/external/storm-cassandra/src/main/java/org/apache/storm/cassandra/query/impl/ObjectMapperCqlStatementMapper.java:40:
> warning - Tag @link: reference not found:
> com.datastax.driver.mapping.annotations.Table
> [INFO] [WARNING]
> ./storm/external/storm-cassandra/src/main/java/org/apache/storm/cassandra/query/builder/ObjectMapperCqlStatementMapperBuilder.java:33:
> warning - Tag @link: reference not found:
> com.datastax.driver.mapping.annotations.Table
> [INFO] [WARNING]
> ./storm/external/storm-cassandra/src/main/java/org/apache/storm/cassandra/query/builder/ObjectMapperCqlStatementMapperBuilder.java:33:
> warning - Tag @link: reference not found:
> com.datastax.driver.mapping.annotations.Table
> [INFO] [WARNING]
> ./storm/external/storm-cassandra/src/main/java/org/apache/storm/cassandra/query/impl/ObjectMapperCqlStatementMapper.java:40:
> warning - Tag @link: reference not found:
> com.datastax.driver.mapping.annotations.Table
> [INFO] [WARNING]
> ./storm/external/storm-cassandra/src/main/java/org/apache/storm/cassandra/query/impl/ObjectMapperCqlStatementMapper.java:40:
> warning - Tag @link: reference not found:
> com.datastax.driver.mapping.annotations.Table
> [INFO] [WARNING]
> ./storm/external/storm-cassandra/src/main/java/org/apache/storm/cassandra/query/builder/ObjectMapperCqlStatementMapperBuilder.java:33:
> warning - Tag @link: reference not found:
> com.datastax.driver.mapping.annotations.Table
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (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 closed STORM-3932.
--
Fix Version/s: 2.6.0
Assignee: Richard Zowalla (was: Bipin Prasad)
Resolution: Fixed
> 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: Richard Zowalla
>Priority: Minor
> Fix For: 2.6.0
>
>
> 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]
> ./st
[jira] [Closed] (STORM-3933) Fix errors/warnings found while generating javadoc in storm-server
[
https://issues.apache.org/jira/browse/STORM-3933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Zowalla closed STORM-3933.
--
Fix Version/s: 2.6.0
Assignee: Richard Zowalla (was: Bipin Prasad)
Resolution: Fixed
> Fix errors/warnings found while generating javadoc in storm-server
> --
>
> Key: STORM-3933
> URL: https://issues.apache.org/jira/browse/STORM-3933
> Project: Apache Storm
> Issue Type: Task
> Components: storm-server
>Reporter: Bipin Prasad
>Assignee: Richard Zowalla
>Priority: Minor
> Fix For: 2.6.0
>
>
> {code:java}
> [INFO] [WARNING] Javadoc Warnings
> [INFO] [WARNING]
> ./storm/storm-server/src/main/java/org/apache/storm/scheduler/resource/strategies/scheduling/BaseResourceAwareStrategy.java:61:
> warning - Tag @link: can't find NodeSorter(Cluster, TopologyDetails,
> NodeSortType) in
> org.apache.storm.scheduler.resource.strategies.scheduling.sorter.NodeSorter
> [INFO] [WARNING]
> ./storm/storm-server/src/main/java/org/apache/storm/scheduler/resource/strategies/scheduling/ObjectResourcesItem.java:42:
> warning - Tag @link: reference not found:
> NodeSorter#sortObjectResourcesCommon(ObjectResourcesSummary, ExecutorDetails,
> NodeSorter.ExistingScheduleFunc)
> [INFO] [WARNING]
> ./storm/storm-server/src/main/java/org/apache/storm/scheduler/resource/strategies/scheduling/ObjectResourcesItem.java:55:
> warning - Tag @link: reference not found:
> NodeSorter#sortObjectResourcesCommon(ObjectResourcesSummary, ExecutorDetails,
> NodeSorter.ExistingScheduleFunc)
> [INFO] [WARNING]
> ./storm/storm-server/src/main/java/org/apache/storm/scheduler/resource/strategies/scheduling/sorter/NodeSorter.java:92:
> warning - Tag @link: reference not found:
> BaseResourceAwareStrategy.NodeSortType#GENERIC_RAS
> [INFO] [WARNING]
> ./storm/storm-server/src/main/java/org/apache/storm/scheduler/resource/strategies/scheduling/sorter/NodeSorter.java:92:
> warning - Tag @link: reference not found:
> BaseResourceAwareStrategy.NodeSortType#DEFAULT_RAS
> [INFO] [WARNING]
> ./storm/storm-server/src/main/java/org/apache/storm/scheduler/resource/strategies/scheduling/sorter/NodeSorter.java:92:
> warning - Tag @link: reference not found:
> BaseResourceAwareStrategy.NodeSortType#COMMON
> [INFO] [WARNING]
> ./storm/storm-server/src/main/java/org/apache/storm/scheduler/resource/strategies/scheduling/sorter/NodeSorter.java:92:
> warning - Tag @link: reference not found:
> BaseResourceAwareStrategy.NodeSortType
> [INFO] [WARNING]
> ./storm/storm-server/src/main/java/org/apache/storm/scheduler/resource/strategies/scheduling/sorter/NodeSorterHostProximity.java:97:
> warning - Tag @link: reference not found:
> BaseResourceAwareStrategy.NodeSortType#GENERIC_RAS
> [INFO] [WARNING]
> ./storm/storm-server/src/main/java/org/apache/storm/scheduler/resource/strategies/scheduling/sorter/NodeSorterHostProximity.java:97:
> warning - Tag @link: reference not found:
> BaseResourceAwareStrategy.NodeSortType#DEFAULT_RAS
> [INFO] [WARNING]
> ./storm/storm-server/src/main/java/org/apache/storm/scheduler/resource/strategies/scheduling/sorter/NodeSorterHostProximity.java:97:
> warning - Tag @link: reference not found:
> BaseResourceAwareStrategy.NodeSortType#COMMON
> [INFO] [WARNING]
> ./storm/storm-server/src/main/java/org/apache/storm/scheduler/resource/strategies/scheduling/sorter/NodeSorterHostProximity.java:97:
> warning - Tag @link: reference not found:
> BaseResourceAwareStrategy.NodeSortType
> [INFO] [WARNING]
> ./storm/storm-server/src/main/java/org/apache/storm/utils/EnumUtil.java:33:
> warning - @param argument "T" is not a parameter name.
> [INFO] [WARNING]
> ./storm/storm-server/src/main/java/org/apache/storm/utils/EnumUtil.java:33:
> warning - @param argument "U" is not a parameter name.
> [INFO] [WARNING]
> ./storm/storm-server/src/main/java/org/apache/storm/nimbus/AssignmentDistributionService.java:112:
> warning - @param argument "callback" is not a parameter name.
> [INFO] [WARNING]
> ./storm/storm-server/src/main/java/org/apache/storm/nimbus/AssignmentDistributionService.java:200:
> warning - Tag @link: reference not found: NodeAssignments
> [INFO] [WARNING]
> ./storm/storm-server/src/main/java/org/apache/storm/nimbus/LeaderListenerCallback.java:81:
> warning - @LeaderListenerCallback is an unknown tag.
> [INFO] [WARNING]
> ./storm/storm-server/src/main/java/org/apache/storm/nimbus/LeaderLi
[jira] [Closed] (STORM-3936) Fix errors/warnings found while generating javadoc in storm-kafka-client
[
https://issues.apache.org/jira/browse/STORM-3936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Zowalla closed STORM-3936.
--
Fix Version/s: 2.6.0
Assignee: Richard Zowalla (was: Bipin Prasad)
Resolution: Fixed
> Fix errors/warnings found while generating javadoc in storm-kafka-client
>
>
> Key: STORM-3936
> URL: https://issues.apache.org/jira/browse/STORM-3936
> Project: Apache Storm
> Issue Type: Task
> Components: storm-kafka-client
>Reporter: Bipin Prasad
>Assignee: Richard Zowalla
>Priority: Minor
> Fix For: 2.6.0
>
>
> {code:java}
> [INFO] [WARNING] Javadoc Warnings
> [INFO] [WARNING]
> ./storm/external/storm-kafka-client/src/main/java/org/apache/storm/kafka/spout/KafkaTuple.java:27:
> warning - Tag @see cannot be used in inline documentation. It can only be
> used in the following types of documentation: overview, package,
> class/interface, constructor, field, method.
> [INFO] [WARNING]
> ./storm/external/storm-kafka-client/src/main/java/org/apache/storm/kafka/spout/KafkaTuple.java:27:
> warning - Tag @see cannot be used in inline documentation. It can only be
> used in the following types of documentation: overview, package,
> class/interface, constructor, field, method.
> [INFO] [WARNING]
> ./storm/external/storm-kafka-client/src/main/java/org/apache/storm/kafka/spout/subscription/TopicAssigner.java:40:
> warning - @param argument "K" is not a parameter name.
> [INFO] [WARNING]
> ./storm/external/storm-kafka-client/src/main/java/org/apache/storm/kafka/spout/subscription/TopicAssigner.java:40:
> warning - @param argument "V" is not a parameter name.
> [INFO] [WARNING]
> ./storm/external/storm-kafka-client/src/main/java/org/apache/storm/kafka/bolt/KafkaBolt.java:71:
> warning - Tag @see cannot be used in inline documentation. It can only be
> used in the following types of documentation: overview, package,
> class/interface, constructor, field, method.
> [INFO] [WARNING]
> ./storm/external/storm-kafka-client/src/main/java/org/apache/storm/kafka/bolt/KafkaBolt.java:71:
> warning - Tag @see cannot be used in inline documentation. It can only be
> used in the following types of documentation: overview, package,
> class/interface, constructor, field, method.
> [INFO] [WARNING]
> ./storm/external/storm-kafka-client/src/main/java/org/apache/storm/kafka/bolt/KafkaBolt.java:75:
> warning - Tag @see cannot be used in inline documentation. It can only be
> used in the following types of documentation: overview, package,
> class/interface, constructor, field, method.
> [INFO] [WARNING]
> ./storm/external/storm-kafka-client/src/main/java/org/apache/storm/kafka/bolt/KafkaBolt.java:75:
> warning - Tag @see cannot be used in inline documentation. It can only be
> used in the following types of documentation: overview, package,
> class/interface, constructor, field, method.
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (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 closed STORM-3885. -- Resolution: Fixed > 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 >Affects Versions: 2.5.0 >Reporter: Bipin Prasad >Assignee: Richard Zowalla >Priority: Major > Fix For: 2.6.0 > > Time Spent: 1h > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (STORM-3937) Fix errors/warnings found while generating javadoc in storm-starter
[ https://issues.apache.org/jira/browse/STORM-3937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla closed STORM-3937. -- Fix Version/s: 2.6.0 Assignee: Richard Zowalla (was: Bipin Prasad) Resolution: Fixed > Fix errors/warnings found while generating javadoc in storm-starter > --- > > Key: STORM-3937 > URL: https://issues.apache.org/jira/browse/STORM-3937 > Project: Apache Storm > Issue Type: Task > Components: storm-starter >Reporter: Bipin Prasad >Assignee: Richard Zowalla >Priority: Minor > Fix For: 2.6.0 > > Time Spent: 20m > Remaining Estimate: 0h > > [INFO] [WARNING] Javadoc Warnings > [INFO] [WARNING] > ./storm/examples/storm-starter/src/jvm/org/apache/storm/starter/tools/SlidingWindowCounter.java:63: > warning - Tag @link: reference not found: PeriodicSlidingWindowCounter -- 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: --- Affects Version/s: 2.5.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 >Affects Versions: 2.5.0 >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-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-ap
[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/st
[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)
[jira] [Resolved] (STORM-3957) Replace static Community/People page by a link to ASF's https://projects.apache.org/committee.html?storm
[ https://issues.apache.org/jira/browse/STORM-3957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexandre Vermeerbergen resolved STORM-3957. Resolution: Fixed > Replace static Community/People page by a link to ASF's > https://projects.apache.org/committee.html?storm > > > Key: STORM-3957 > URL: https://issues.apache.org/jira/browse/STORM-3957 > Project: Apache Storm > Issue Type: Documentation >Reporter: Alexandre Vermeerbergen >Assignee: Alexandre Vermeerbergen >Priority: Trivial > Time Spent: 2h 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (STORM-3954) Remove Logback pulled in by Zookeeper
[ https://issues.apache.org/jira/browse/STORM-3954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla closed STORM-3954. -- Resolution: Fixed > Remove Logback pulled in by Zookeeper > - > > Key: STORM-3954 > URL: https://issues.apache.org/jira/browse/STORM-3954 > Project: Apache Storm > Issue Type: Bug >Affects Versions: 2.6.0 >Reporter: Richard Zowalla >Assignee: Richard Zowalla >Priority: Major > Fix For: 2.6.0 > > Time Spent: 40m > Remaining Estimate: 0h > > We are using log4j2, so better to replace an additional logging provider > which lurked in by the recent 3.9.0 upgrade. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (STORM-3959) Add Matomo Tracking to Website
Richard Zowalla created STORM-3959: -- Summary: 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 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)
[jira] [Created] (STORM-3958) Capacity to set Storm UI's title in conf/storm.yaml
Alexandre Vermeerbergen created STORM-3958:
--
Summary: 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
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] [Created] (STORM-3957) Replace static Community/People page by a link to ASF'shttps://projects.apache.org/committee.html?storm
Alexandre Vermeerbergen created STORM-3957: -- Summary: Replace static Community/People page by a link to ASF'shttps://projects.apache.org/committee.html?storm Key: STORM-3957 URL: https://issues.apache.org/jira/browse/STORM-3957 Project: Apache Storm Issue Type: Documentation Reporter: Alexandre Vermeerbergen Assignee: Alexandre Vermeerbergen -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (STORM-3957) Replace static Community/People page by a link to ASF's https://projects.apache.org/committee.html?storm
[ https://issues.apache.org/jira/browse/STORM-3957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexandre Vermeerbergen updated STORM-3957: --- Summary: Replace static Community/People page by a link to ASF's https://projects.apache.org/committee.html?storm (was: Replace static Community/People page by a link to ASF'shttps://projects.apache.org/committee.html?storm) > Replace static Community/People page by a link to ASF's > https://projects.apache.org/committee.html?storm > > > Key: STORM-3957 > URL: https://issues.apache.org/jira/browse/STORM-3957 > Project: Apache Storm > Issue Type: Documentation >Reporter: Alexandre Vermeerbergen >Assignee: Alexandre Vermeerbergen >Priority: Trivial > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[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 ] Richard Zowalla updated STORM-3811: --- Fix Version/s: (was: 2.3.1) (was: 1.2.5) (was: 2.2.2) (was: 2.1.2) > Upgrade log4j version to 2.17.1 > --- > > Key: STORM-3811 > URL: https://issues.apache.org/jira/browse/STORM-3811 > Project: Apache Storm > Issue Type: Dependency upgrade >Reporter: Aaron Gresch >Priority: Critical > Fix For: 2.4.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (STORM-2999) Add generics to static type of method parameters and variables where applicable
[ https://issues.apache.org/jira/browse/STORM-2999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla updated STORM-2999: --- Fix Version/s: (was: 3.0.0) > Add generics to static type of method parameters and variables where > applicable > --- > > Key: STORM-2999 > URL: https://issues.apache.org/jira/browse/STORM-2999 > Project: Apache Storm > Issue Type: Improvement >Reporter: Karl-Philipp Richter >Assignee: Derek Dagit >Priority: Minor > Labels: pull-request-available > Time Spent: 1h 10m > Remaining Estimate: 0h > > Adding generics to the static type of method, constructor parameter and > variables always improves type safety, avoids suppression of warnings and > allows to detect design flaws earlier. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (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 updated STORM-3956: --- Fix Version/s: 2.6.0 > 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: 20m > 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] [Created] (STORM-3956) Fix cli monitor component's argument type
Richard Zowalla created STORM-3956: -- Summary: 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 >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 topologycomponent 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] [Closed] (STORM-3949) libthrift 0.18.1
[ https://issues.apache.org/jira/browse/STORM-3949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla closed STORM-3949. -- Resolution: Fixed > libthrift 0.18.1 > > > Key: STORM-3949 > URL: https://issues.apache.org/jira/browse/STORM-3949 > Project: Apache Storm > Issue Type: Dependency upgrade >Affects Versions: 2.5.0 >Reporter: Richard Zowalla >Assignee: Richard Zowalla >Priority: Major > Fix For: 2.6.0 > > Time Spent: 40m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (STORM-3953) Update RELEASING.md
[ https://issues.apache.org/jira/browse/STORM-3953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla resolved STORM-3953. Resolution: Fixed > Update RELEASING.md > --- > > Key: STORM-3953 > URL: https://issues.apache.org/jira/browse/STORM-3953 > Project: Apache Storm > Issue Type: Task > Components: documentation >Reporter: Bipin Prasad >Assignee: Bipin Prasad >Priority: Minor > Fix For: 2.6.0 > > Time Spent: 1h > Remaining Estimate: 0h > > . -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (STORM-3955) Dependabot recommended update to maven-core
[ https://issues.apache.org/jira/browse/STORM-3955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla resolved STORM-3955. Fix Version/s: 2.6.0 Resolution: Fixed > Dependabot recommended update to maven-core > --- > > Key: STORM-3955 > URL: https://issues.apache.org/jira/browse/STORM-3955 > Project: Apache Storm > Issue Type: Task >Reporter: Bipin Prasad >Assignee: Bipin Prasad >Priority: Minor > Fix For: 2.6.0 > > Time Spent: 10m > Remaining Estimate: 0h > > Bump org.apache.maven:maven-core from 3.6.0 to 3.8.1 in > /storm-buildtools/storm-maven-plugins > PR: https://github.com/apache/storm/pull/3567 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (STORM-3950) Modernize storm-jdbc
[ https://issues.apache.org/jira/browse/STORM-3950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla resolved STORM-3950. Resolution: Fixed > Modernize storm-jdbc > > > Key: STORM-3950 > URL: https://issues.apache.org/jira/browse/STORM-3950 > Project: Apache Storm > Issue Type: Dependency upgrade > Components: storm-jdbc >Affects Versions: 2.5.0 >Reporter: Richard Zowalla >Assignee: Richard Zowalla >Priority: Major > Fix For: 2.6.0 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (STORM-3914) Several External Modules as not being tested for JDK 11
[ https://issues.apache.org/jira/browse/STORM-3914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla resolved STORM-3914. Fix Version/s: 2.6.0 Resolution: Fixed > Several External Modules as not being tested for JDK 11 > --- > > Key: STORM-3914 > URL: https://issues.apache.org/jira/browse/STORM-3914 > Project: Apache Storm > Issue Type: Improvement > Components: build >Reporter: Bipin Prasad >Assignee: Richard Zowalla >Priority: Major > Fix For: 2.6.0 > > Time Spent: 20m > Remaining Estimate: 0h > > Github actions for JDK11 "external" does not include several external > modules, however they are included for JDK8 build. > Change the JDK11 github actions. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (STORM-3943) May I ask that you can configure a user password to log in for security verification when visiting storm ui. Check the official website security verification is not ver
[ https://issues.apache.org/jira/browse/STORM-3943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17754821#comment-17754821 ] zfy68 commented on STORM-3943: -- [~alekstorm] > May I ask that you can configure a user password to log in for security > verification when visiting storm ui. Check the official website security > verification is not very clear. storm version 1.2.3 > > > Key: STORM-3943 > URL: https://issues.apache.org/jira/browse/STORM-3943 > Project: Apache Storm > Issue Type: Question > Components: storm-ui >Affects Versions: 1.2.3 > Environment: cluster >Reporter: zfy68 >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (STORM-3955) Dependabot recommended update to maven-core
[ https://issues.apache.org/jira/browse/STORM-3955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bipin Prasad reassigned STORM-3955: --- Assignee: Bipin Prasad > Dependabot recommended update to maven-core > --- > > Key: STORM-3955 > URL: https://issues.apache.org/jira/browse/STORM-3955 > Project: Apache Storm > Issue Type: Task >Reporter: Bipin Prasad >Assignee: Bipin Prasad >Priority: Minor > > Bump org.apache.maven:maven-core from 3.6.0 to 3.8.1 in > /storm-buildtools/storm-maven-plugins > PR: https://github.com/apache/storm/pull/3567 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (STORM-3955) Dependabot recommended update to maven-core
Bipin Prasad created STORM-3955: --- Summary: Dependabot recommended update to maven-core Key: STORM-3955 URL: https://issues.apache.org/jira/browse/STORM-3955 Project: Apache Storm Issue Type: Task Reporter: Bipin Prasad Bump org.apache.maven:maven-core from 3.6.0 to 3.8.1 in /storm-buildtools/storm-maven-plugins PR: https://github.com/apache/storm/pull/3567 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (STORM-3953) Update RELEASING.md
[ https://issues.apache.org/jira/browse/STORM-3953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bipin Prasad updated STORM-3953: Description: . > Update RELEASING.md > --- > > Key: STORM-3953 > URL: https://issues.apache.org/jira/browse/STORM-3953 > Project: Apache Storm > Issue Type: Task > Components: documentation >Reporter: Bipin Prasad >Assignee: Bipin Prasad >Priority: Minor > Fix For: 2.6.0 > > Time Spent: 10m > Remaining Estimate: 0h > > . -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (STORM-3954) Remove Logback pulled in by Zookeeper
Richard Zowalla created STORM-3954: -- Summary: Remove Logback pulled in by Zookeeper Key: STORM-3954 URL: https://issues.apache.org/jira/browse/STORM-3954 Project: Apache Storm Issue Type: Bug Affects Versions: 2.6.0 Reporter: Richard Zowalla Assignee: Richard Zowalla Fix For: 2.6.0 We are using log4j2, so better to replace an additional logging provider which lurked in by the recent 3.9.0 upgrade. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (STORM-3953) Update RELEASING.md
[ https://issues.apache.org/jira/browse/STORM-3953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bipin Prasad reassigned STORM-3953: --- Assignee: Bipin Prasad > Update RELEASING.md > --- > > Key: STORM-3953 > URL: https://issues.apache.org/jira/browse/STORM-3953 > Project: Apache Storm > Issue Type: Task > Components: documentation >Reporter: Bipin Prasad >Assignee: Bipin Prasad >Priority: Minor > Fix For: 2.6.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (STORM-3953) Update RELEASING.md
Bipin Prasad created STORM-3953: --- Summary: Update RELEASING.md Key: STORM-3953 URL: https://issues.apache.org/jira/browse/STORM-3953 Project: Apache Storm Issue Type: Task Components: documentation Reporter: Bipin Prasad Fix For: 2.6.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (STORM-3952) Add github action to deploy storm on AWS EKS
Bipin Prasad created STORM-3952: --- Summary: Add github action to deploy storm on AWS EKS Key: STORM-3952 URL: https://issues.apache.org/jira/browse/STORM-3952 Project: Apache Storm Issue Type: Task Reporter: Bipin Prasad -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (STORM-3951) Add github action to deploy storm on Google Cloud Platform
Bipin Prasad created STORM-3951: --- Summary: Add github action to deploy storm on Google Cloud Platform Key: STORM-3951 URL: https://issues.apache.org/jira/browse/STORM-3951 Project: Apache Storm Issue Type: Task Components: build Reporter: Bipin Prasad -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (STORM-3950) Modernize storm-jdbc
Richard Zowalla created STORM-3950: -- Summary: Modernize storm-jdbc Key: STORM-3950 URL: https://issues.apache.org/jira/browse/STORM-3950 Project: Apache Storm Issue Type: Dependency upgrade Components: storm-jdbc Affects Versions: 2.5.0 Reporter: Richard Zowalla Assignee: Richard Zowalla -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (STORM-3950) Modernize storm-jdbc
[ https://issues.apache.org/jira/browse/STORM-3950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla updated STORM-3950: --- Fix Version/s: 2.6.0 > Modernize storm-jdbc > > > Key: STORM-3950 > URL: https://issues.apache.org/jira/browse/STORM-3950 > Project: Apache Storm > Issue Type: Dependency upgrade > Components: storm-jdbc >Affects Versions: 2.5.0 >Reporter: Richard Zowalla >Assignee: Richard Zowalla >Priority: Major > Fix For: 2.6.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (STORM-3949) libthrift 0.18.1
Richard Zowalla created STORM-3949: -- Summary: libthrift 0.18.1 Key: STORM-3949 URL: https://issues.apache.org/jira/browse/STORM-3949 Project: Apache Storm Issue Type: Dependency upgrade Affects Versions: 2.5.0 Reporter: Richard Zowalla Assignee: Richard Zowalla Fix For: 2.6.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (STORM-3782) Refactor KafkaOffsetMetric to use V2 metrics
[ https://issues.apache.org/jira/browse/STORM-3782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla resolved STORM-3782. Fix Version/s: 2.6.0 Assignee: Rui Li (was: Bipin Prasad) Resolution: Fixed > Refactor KafkaOffsetMetric to use V2 metrics > > > Key: STORM-3782 > URL: https://issues.apache.org/jira/browse/STORM-3782 > Project: Apache Storm > Issue Type: Improvement >Reporter: Rui Li >Assignee: Rui Li >Priority: Minor > Fix For: 2.6.0 > > Time Spent: 1h > Remaining Estimate: 0h > > https://github.com/apache/storm/blob/master/external/storm-kafka-client/src/main/java/org/apache/storm/kafka/spout/metrics/KafkaOffsetMetric.java -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (STORM-3771) Execute doCleanup in its own timer thread without lock
[ https://issues.apache.org/jira/browse/STORM-3771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla resolved STORM-3771. Fix Version/s: 2.6.0 Resolution: Fixed > Execute doCleanup in its own timer thread without lock > -- > > Key: STORM-3771 > URL: https://issues.apache.org/jira/browse/STORM-3771 > Project: Apache Storm > Issue Type: Improvement > Components: storm-server >Reporter: Bipin Prasad >Assignee: Bipin Prasad >Priority: Major > Fix For: 2.6.0 > > Time Spent: 20m > Remaining Estimate: 0h > > _Sometimes doCleanup can take a long time (several minutes) while holding > submitLock. This slows down other "submitLock" dependent activities. Execute > doCleanup without a lock and within its own timer thread. Ignore exception > that may occur inside doCleanup() method._ -- This message was sent by Atlassian Jira (v8.20.10#820010)
