[
https://issues.apache.org/jira/browse/AMBARI-25892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
guluo updated AMBARI-25892:
---------------------------
Description:
NamedTasksSubscriptions and NamedTasksSubscribeListener print logs to
ambari-server.log frequently. As follows
The log contents are as follows.
{code:java}
2023-03-11 20:05:28,144 INFO [clientOutboundChannel-4543]
NamedTasksSubscriptions:117 - Task subscriptions were removed for sessionId =
b4c4fb2b-9f7f-19a3-c1bf-1ec01252b268
2023-03-11 20:05:28,144 INFO [clientOutboundChannel-4543]
NamedTasksSubscribeListener:72 - API disconnect was arrived with sessionId =
b4c4fb2b-9f7f-19a3-c1bf-1ec01252b268
2023-03-11 20:05:38,143 INFO [clientOutboundChannel-4543]
NamedTasksSubscriptions:117 - Task subscriptions were removed for sessionId =
683b6e57-9e67-9e65-3ad5-c728b21c0528
2023-03-11 20:05:38,144 INFO [clientOutboundChannel-4543]
NamedTasksSubscribeListener:72 - API disconnect was arrived with sessionId =
683b6e57-9e67-9e65-3ad5-c728b21c0528
2023-03-11 20:05:38,144 INFO [clientOutboundChannel-4543]
NamedTasksSubscriptions:117 - Task subscriptions were removed for sessionId =
baacf4e4-00c9-0d4e-6992-c8494e6038bc
2023-03-11 20:05:38,144 INFO [clientOutboundChannel-4543]
NamedTasksSubscribeListener:72 - API disconnect was arrived with sessionId =
baacf4e4-00c9-0d4e-6992-c8494e6038bc
2023-03-11 20:05:48,143 INFO [clientOutboundChannel-4543]
NamedTasksSubscriptions:117 - Task subscriptions were removed for sessionId =
206e6bc3-e84a-9eca-3cc3-015ba4b527bc
2023-03-11 20:05:48,144 INFO [clientOutboundChannel-4543]
NamedTasksSubscribeListener:72 - API disconnect was arrived with sessionId =
206e6bc3-e84a-9eca-3cc3-015ba4b527bc
2023-03-11 20:05:48,144 INFO [clientOutboundChannel-4543]
NamedTasksSubscriptions:117 - Task subscriptions were removed for sessionId =
297fc85e-8b29-677c-a0f1-2d15296b1a3b
2023-03-11 20:05:48,144 INFO [clientOutboundChannel-4543]
NamedTasksSubscribeListener:72 - API disconnect was arrived with sessionId =
297fc85e-8b29-677c-a0f1-2d15296b1a3b
2023-03-11 20:06:08,145 INFO [clientOutboundChannel-4543]
NamedTasksSubscriptions:117 - Task subscriptions were removed for sessionId =
4ce2bcb1-4321-fdc6-b320-2b1b6118988e
2023-03-11 20:06:08,145 INFO [clientOutboundChannel-4543]
NamedTasksSubscribeListener:72 - API disconnect was arrived with sessionId =
4ce2bcb1-4321-fdc6-b320-2b1b6118988e
2023-03-11 20:06:08,146 INFO [clientOutboundChannel-4543]
NamedTasksSubscriptions:117 - Task subscriptions were removed for sessionId =
e9d4cf8e-293d-e89c-b11f-24f5a3efd761
2023-03-11 20:06:08,146 INFO [clientOutboundChannel-4543]
NamedTasksSubscribeListener:72 - API disconnect was arrived with sessionId =
e9d4cf8e-293d-e89c-b11f-24f5a3efd761
2023-03-11 20:06:18,145 INFO [clientOutboundChannel-4543]
NamedTasksSubscriptions:117 - Task subscriptions were removed for sessionId =
176c41d0-ff90-ff7a-3015-aca0a40c792b
2023-03-11 20:06:18,145 INFO [clientOutboundChannel-4543]
NamedTasksSubscribeListener:72 - API disconnect was arrived with sessionId =
176c41d0-ff90-ff7a-3015-aca0a40c792b
...{code}
I think these logs is less important for positioning issue about ambari-server,
even sometimes interfere with us.
So, I suggest that adjusting its log level from info to debug
was:
NamedTasksSubscriptions and NamedTasksSubscribeListener print logs to
ambari-server.log frequently. As follows
The log contents are as follows.
{code:java}
2023-03-11 20:05:28,144 INFO [clientOutboundChannel-4543]
NamedTasksSubscriptions:117 - Task subscriptions were removed for sessionId =
b4c4fb2b-9f7f-19a3-c1bf-1ec01252b268
2023-03-11 20:05:28,144 INFO [clientOutboundChannel-4543]
NamedTasksSubscribeListener:72 - API disconnect was arrived with sessionId =
b4c4fb2b-9f7f-19a3-c1bf-1ec01252b268
...{code}
I think these logs is less important for positioning issue about ambari-server,
even sometimes interfere with us.
So, I suggest that adjusting its log level from info to debug
> NamedTasksSubscriptions and NamedTasksSubscribeListener print logs frequently
> -----------------------------------------------------------------------------
>
> Key: AMBARI-25892
> URL: https://issues.apache.org/jira/browse/AMBARI-25892
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-sever
> Affects Versions: trunk
> Environment: ambari trunk
> centos7
> Reporter: guluo
> Priority: Minor
>
> NamedTasksSubscriptions and NamedTasksSubscribeListener print logs to
> ambari-server.log frequently. As follows
> The log contents are as follows.
> {code:java}
> 2023-03-11 20:05:28,144 INFO [clientOutboundChannel-4543]
> NamedTasksSubscriptions:117 - Task subscriptions were removed for sessionId =
> b4c4fb2b-9f7f-19a3-c1bf-1ec01252b268
> 2023-03-11 20:05:28,144 INFO [clientOutboundChannel-4543]
> NamedTasksSubscribeListener:72 - API disconnect was arrived with sessionId =
> b4c4fb2b-9f7f-19a3-c1bf-1ec01252b268
> 2023-03-11 20:05:38,143 INFO [clientOutboundChannel-4543]
> NamedTasksSubscriptions:117 - Task subscriptions were removed for sessionId =
> 683b6e57-9e67-9e65-3ad5-c728b21c0528
> 2023-03-11 20:05:38,144 INFO [clientOutboundChannel-4543]
> NamedTasksSubscribeListener:72 - API disconnect was arrived with sessionId =
> 683b6e57-9e67-9e65-3ad5-c728b21c0528
> 2023-03-11 20:05:38,144 INFO [clientOutboundChannel-4543]
> NamedTasksSubscriptions:117 - Task subscriptions were removed for sessionId =
> baacf4e4-00c9-0d4e-6992-c8494e6038bc
> 2023-03-11 20:05:38,144 INFO [clientOutboundChannel-4543]
> NamedTasksSubscribeListener:72 - API disconnect was arrived with sessionId =
> baacf4e4-00c9-0d4e-6992-c8494e6038bc
> 2023-03-11 20:05:48,143 INFO [clientOutboundChannel-4543]
> NamedTasksSubscriptions:117 - Task subscriptions were removed for sessionId =
> 206e6bc3-e84a-9eca-3cc3-015ba4b527bc
> 2023-03-11 20:05:48,144 INFO [clientOutboundChannel-4543]
> NamedTasksSubscribeListener:72 - API disconnect was arrived with sessionId =
> 206e6bc3-e84a-9eca-3cc3-015ba4b527bc
> 2023-03-11 20:05:48,144 INFO [clientOutboundChannel-4543]
> NamedTasksSubscriptions:117 - Task subscriptions were removed for sessionId =
> 297fc85e-8b29-677c-a0f1-2d15296b1a3b
> 2023-03-11 20:05:48,144 INFO [clientOutboundChannel-4543]
> NamedTasksSubscribeListener:72 - API disconnect was arrived with sessionId =
> 297fc85e-8b29-677c-a0f1-2d15296b1a3b
> 2023-03-11 20:06:08,145 INFO [clientOutboundChannel-4543]
> NamedTasksSubscriptions:117 - Task subscriptions were removed for sessionId =
> 4ce2bcb1-4321-fdc6-b320-2b1b6118988e
> 2023-03-11 20:06:08,145 INFO [clientOutboundChannel-4543]
> NamedTasksSubscribeListener:72 - API disconnect was arrived with sessionId =
> 4ce2bcb1-4321-fdc6-b320-2b1b6118988e
> 2023-03-11 20:06:08,146 INFO [clientOutboundChannel-4543]
> NamedTasksSubscriptions:117 - Task subscriptions were removed for sessionId =
> e9d4cf8e-293d-e89c-b11f-24f5a3efd761
> 2023-03-11 20:06:08,146 INFO [clientOutboundChannel-4543]
> NamedTasksSubscribeListener:72 - API disconnect was arrived with sessionId =
> e9d4cf8e-293d-e89c-b11f-24f5a3efd761
> 2023-03-11 20:06:18,145 INFO [clientOutboundChannel-4543]
> NamedTasksSubscriptions:117 - Task subscriptions were removed for sessionId =
> 176c41d0-ff90-ff7a-3015-aca0a40c792b
> 2023-03-11 20:06:18,145 INFO [clientOutboundChannel-4543]
> NamedTasksSubscribeListener:72 - API disconnect was arrived with sessionId =
> 176c41d0-ff90-ff7a-3015-aca0a40c792b
> ...{code}
> I think these logs is less important for positioning issue about
> ambari-server, even sometimes interfere with us.
> So, I suggest that adjusting its log level from info to debug
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org
