[jira] [Updated] (STORM-3794) storm list displays logs and execution information

2021-09-22 Thread Kaushal Kumar (Jira) 


 [ 
https://issues.apache.org/jira/browse/STORM-3794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kaushal Kumar updated STORM-3794:
-
Description: 
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}
[vagrant@agent1 bin]$ 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 : 
agent1.corp.com:6627
 Topology_name Status Num_tasks Num_workers Uptime_secs Topology_Id Owner 
 

 TestJob_1 ACTIVE 6 1 5263482 TestJob_1-13-1627046008 xyz 
 [vagrant@agent1 bin]${code}{code}
 

  was:
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}
[vagrant@agent1 bin]$ 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 : 
agent1.corp.fairisaac.com:6627
 Topology_name Status Num_tasks Num_workers Uptime_secs Topology_Id Owner 
 

 TestJob_1 ACTIVE 6 1 5263482 TestJob_1-13-1627046008 xyz 
 [vagrant@agent1 bin]${code}{code}
 


> storm list displays logs and execution information
> --
>
> Key: STORM-3794
> URL: https://issues.apache.org/jira/browse/STORM-3794
> 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}
> [vagrant@agent1 bin]$ 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 : 
> agent1.corp.com:6627
>  Topology_name Status Num_tasks Num_workers Uptime_secs Topology_Id Owner 
>  
> 
>  TestJob_1 ACTIVE 6 1 5263482 TestJob_1-13-1627046008 x

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

2021-09-22 Thread Ethan Li (Jira) 


 [ 
https://issues.apache.org/jira/browse/STORM-3785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ethan Li updated STORM-3785:

Component/s: storm-client

> Rate metrics are wrongly divided by 100
> ---
>
> Key: STORM-3785
> URL: https://issues.apache.org/jira/browse/STORM-3785
> Project: Apache Storm
>  Issue Type: Bug
>  Components: storm-client
>Affects Versions: 2.2.0
>Reporter: Rui Li
>Assignee: Rui Li
>Priority: Critical
> Fix For: 2.3.0, 2.2.1
>
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> customers complained about odd behavior of storm rate metrics (m1_rate, etc). 
> It turns out to be a Storm bug:
> https://github.com/apache/storm/blob/master/storm-client/src/jvm/org/apache/storm/executor/Executor.java#L416
> https://github.com/apache/storm/blob/master/storm-client/src/jvm/org/apache/storm/executor/Executor.java#L437



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

2021-09-22 Thread Ethan Li (Jira) 


 [ 
https://issues.apache.org/jira/browse/STORM-3785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ethan Li resolved STORM-3785.
-
Resolution: Fixed

> Rate metrics are wrongly divided by 100
> ---
>
> Key: STORM-3785
> URL: https://issues.apache.org/jira/browse/STORM-3785
> Project: Apache Storm
>  Issue Type: Bug
>Affects Versions: 2.2.0
>Reporter: Rui Li
>Assignee: Rui Li
>Priority: Critical
> Fix For: 2.3.0, 2.2.1
>
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> customers complained about odd behavior of storm rate metrics (m1_rate, etc). 
> It turns out to be a Storm bug:
> https://github.com/apache/storm/blob/master/storm-client/src/jvm/org/apache/storm/executor/Executor.java#L416
> https://github.com/apache/storm/blob/master/storm-client/src/jvm/org/apache/storm/executor/Executor.java#L437



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

2021-09-22 Thread Ethan Li (Jira) 


[ 
https://issues.apache.org/jira/browse/STORM-3785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17418798#comment-17418798
 ] 

Ethan Li commented on STORM-3785:
-

Merged in master: 0c7bbca67db593b82030a7b406a44d54122ce792, 
775d6098a9a7bc8d2242e925457a960ff89faaeb
cherry-picked to 2.2.x-branch: ee6cd75abb4704bc97039f626c1106361518, 
e95af5a967c75ac8c102752d9d6100853d3ace3b

> Rate metrics are wrongly divided by 100
> ---
>
> Key: STORM-3785
> URL: https://issues.apache.org/jira/browse/STORM-3785
> Project: Apache Storm
>  Issue Type: Bug
>Affects Versions: 2.2.0
>Reporter: Rui Li
>Assignee: Rui Li
>Priority: Critical
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> customers complained about odd behavior of storm rate metrics (m1_rate, etc). 
> It turns out to be a Storm bug:
> https://github.com/apache/storm/blob/master/storm-client/src/jvm/org/apache/storm/executor/Executor.java#L416
> https://github.com/apache/storm/blob/master/storm-client/src/jvm/org/apache/storm/executor/Executor.java#L437



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

2021-09-22 Thread Ethan Li (Jira) 


 [ 
https://issues.apache.org/jira/browse/STORM-3785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ethan Li updated STORM-3785:

Fix Version/s: 2.2.1
   2.3.0

> Rate metrics are wrongly divided by 100
> ---
>
> Key: STORM-3785
> URL: https://issues.apache.org/jira/browse/STORM-3785
> Project: Apache Storm
>  Issue Type: Bug
>Affects Versions: 2.2.0
>Reporter: Rui Li
>Assignee: Rui Li
>Priority: Critical
> Fix For: 2.3.0, 2.2.1
>
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> customers complained about odd behavior of storm rate metrics (m1_rate, etc). 
> It turns out to be a Storm bug:
> https://github.com/apache/storm/blob/master/storm-client/src/jvm/org/apache/storm/executor/Executor.java#L416
> https://github.com/apache/storm/blob/master/storm-client/src/jvm/org/apache/storm/executor/Executor.java#L437



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

2021-09-22 Thread Ethan Li (Jira) 


 [ 
https://issues.apache.org/jira/browse/STORM-3785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ethan Li updated STORM-3785:

Affects Version/s: 2.2.0

> Rate metrics are wrongly divided by 100
> ---
>
> Key: STORM-3785
> URL: https://issues.apache.org/jira/browse/STORM-3785
> Project: Apache Storm
>  Issue Type: Bug
>Affects Versions: 2.2.0
>Reporter: Rui Li
>Assignee: Rui Li
>Priority: Critical
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> customers complained about odd behavior of storm rate metrics (m1_rate, etc). 
> It turns out to be a Storm bug:
> https://github.com/apache/storm/blob/master/storm-client/src/jvm/org/apache/storm/executor/Executor.java#L416
> https://github.com/apache/storm/blob/master/storm-client/src/jvm/org/apache/storm/executor/Executor.java#L437



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

2021-09-22 Thread Ethan Li (Jira) 


 [ 
https://issues.apache.org/jira/browse/STORM-3785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ethan Li reassigned STORM-3785:
---

Assignee: Rui Li

> Rate metrics are wrongly divided by 100
> ---
>
> Key: STORM-3785
> URL: https://issues.apache.org/jira/browse/STORM-3785
> Project: Apache Storm
>  Issue Type: Bug
>Reporter: Rui Li
>Assignee: Rui Li
>Priority: Critical
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> customers complained about odd behavior of storm rate metrics (m1_rate, etc). 
> It turns out to be a Storm bug:
> https://github.com/apache/storm/blob/master/storm-client/src/jvm/org/apache/storm/executor/Executor.java#L416
> https://github.com/apache/storm/blob/master/storm-client/src/jvm/org/apache/storm/executor/Executor.java#L437



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (STORM-3794) storm list displays logs and execution information

2021-09-22 Thread Kaushal Kumar (Jira) 


 [ 
https://issues.apache.org/jira/browse/STORM-3794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kaushal Kumar updated STORM-3794:
-
Description: 
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}
[vagrant@agent1 bin]$ 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 : 
agent1.corp.fairisaac.com:6627
 Topology_name Status Num_tasks Num_workers Uptime_secs Topology_Id Owner 
 

 TestJob_1 ACTIVE 6 1 5263482 TestJob_1-13-1627046008 xyz 
 [vagrant@agent1 bin]${code}{code}
 

  was:
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}
[vagrant@agent1 bin]$ 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 : 
agent1.corp.fairisaac.com:6627
 Topology_name Status Num_tasks Num_workers Uptime_secs Topology_Id Owner 
 

 TestJob_1 ACTIVE 6 1 5263482 TestJob_1-13-1627046008 xyz 
 [vagrant@agent1 bin]${code}{code}
 


> storm list displays logs and execution information
> --
>
> Key: STORM-3794
> URL: https://issues.apache.org/jira/browse/STORM-3794
> 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}
> [vagrant@agent1 bin]$ 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 : 
> agent1.corp.fairisaac.com:6627
>  Topology_name Status Num_tasks Num_workers Uptime_secs Topology_Id Owner 
>  
> 
>  TestJob_1 ACTIVE 6 1 5263482 TestJ

[jira] [Updated] (STORM-3794) storm list displays logs and execution information

2021-09-22 Thread Kaushal Kumar (Jira) 


 [ 
https://issues.apache.org/jira/browse/STORM-3794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kaushal Kumar updated STORM-3794:
-
Description: 
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}
[vagrant@agent1 bin]$ 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 : 
agent1.corp.fairisaac.com:6627
 Topology_name Status Num_tasks Num_workers Uptime_secs Topology_Id Owner 
 

 TestJob_1 ACTIVE 6 1 5263482 TestJob_1-13-1627046008 xyz 
 [vagrant@agent1 bin]${code}{code}
 

  was:
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}
[vagrant@agent1 bin]$ 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 : 
agent1.corp.fairisaac.com:6627
Topology_name Status Num_tasks Num_workers Uptime_secs Topology_Id Owner 

TestJob_1 ACTIVE 6 1 5263482 TestJob_1-13-1627046008 xyz 
[vagrant@agent1 bin]${code}


> storm list displays logs and execution information
> --
>
> Key: STORM-3794
> URL: https://issues.apache.org/jira/browse/STORM-3794
> 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}
> [vagrant@agent1 bin]$ 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 : 
> agent1.corp.fairisaac.com:6627
>  Topology_name Status Num_tasks Num_workers Uptime_secs Topology_Id Owner 
>  
> 
>  TestJob_1 ACTIVE 6 1 5263482 TestJob_1-13-1627

[jira] [Created] (STORM-3794) storm list displays logs and execution information

2021-09-22 Thread Kaushal Kumar (Jira) 
Kaushal Kumar created STORM-3794:


 Summary: storm list displays logs and execution information
 Key: STORM-3794
 URL: https://issues.apache.org/jira/browse/STORM-3794
 Project: Apache Storm
  Issue Type: Question
  Components: storm-client
Reporter: Kaushal Kumar


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}
[vagrant@agent1 bin]$ 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 : 
agent1.corp.fairisaac.com:6627
Topology_name Status Num_tasks Num_workers Uptime_secs Topology_Id Owner 

TestJob_1 ACTIVE 6 1 5263482 TestJob_1-13-1627046008 xyz 
[vagrant@agent1 bin]${code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)