[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] [Created] (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 very
zfy68 created STORM-3943: Summary: 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 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (STORM-3881) How to dynamically update variable information in memory after the cluster starts storm
zfy68 created STORM-3881: Summary: How to dynamically update variable information in memory after the cluster starts storm Key: STORM-3881 URL: https://issues.apache.org/jira/browse/STORM-3881 Project: Apache Storm Issue Type: Question Components: storm-core Affects Versions: 1.2.3 Reporter: zfy68 _I want to dynamically update some of the memory information in the Bolt processing logic, but the number and concurrency of Bolts are too large. Another way of thinking, can it be achieved by changing the memory of each worker process?_ -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (STORM-1382) Netty Client connection failure error message is too alarming
[
https://issues.apache.org/jira/browse/STORM-1382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17493103#comment-17493103
]
zfy68 commented on STORM-1382:
--
me too
*2022-02-16 08:45:09.834 o.a.s.m.n.Client client-boss-1 [ERROR] connection
attempt 1 to Netty-Client-name/ip:16715 failed: java.net.ConnectException:
Connection refused: fzdpc03/10.20.106.232:16715*
> Netty Client connection failure error message is too alarming
> -
>
> Key: STORM-1382
> URL: https://issues.apache.org/jira/browse/STORM-1382
> Project: Apache Storm
> Issue Type: Bug
> Components: storm-core
>Reporter: Paul Poulosky
>Priority: Major
>
> The error message printed when a netty-client cannot connect to another
> worker is worded in a way that our users are interpreting as a failure with
> storm.
> There are times, such as at topology launch when such messages are normal as
> not all of the workers have been launched on all of the supervisors yet.
> Other times, it is indicative of a failure (uncaught exception, OOM) on
> another worker, but the end user believes that this client is failing, due to
> the error message.
> eg:
> {noformat}
> 2015-12-03 12:28:53.338 b.s.m.n.Client [ERROR] connection attempt 10 to
> Netty-Client-host1.grid.myco.com/10.1.2.3:6710 failed:
> java.net.ConnectException: Connection refused:
> host1.grid.myco.com/10.1.2.3:6710
> {noformat}
> We should change the message to be more informative to our end users as to
> what happened, and it should not be an ERROR, but a Warning, as there are
> occasions when one would expect to see this.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
