ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexey Kuznetsov (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (IGNITE-10552) Web Agent: Improve logging when cluster topology changed
Date Wed, 05 Dec 2018 15:25:00 GMT

    [ https://issues.apache.org/jira/browse/IGNITE-10552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16710172#comment-16710172

Alexey Kuznetsov edited comment on IGNITE-10552 at 12/5/18 3:24 PM:

After my changes Web Agent log now looks like:
[2018-12-05 22:22:37,960][INFO ][main][AgentLauncher] Connecting to: http://localhost:3000
[2018-12-05 22:22:38,067][INFO ][EventThread][AgentLauncher] Connection established.
[2018-12-05 22:22:38,139][INFO ][EventThread][AgentLauncher] Authentication success.
[2018-12-05 22:22:38,467][INFO ][pool-1-thread-1][RestExecutor] Connected to cluster [url=http://localhost:8080]
[2018-12-05 22:22:38,510][INFO ][pool-1-thread-1][ClusterListener] Connection successfully
established to cluster with nodes: [D8A3F026]
[2018-12-05 22:23:08,750][INFO ][pool-1-thread-1][ClusterListener] Cluster topology changed,
new topology: [D8A3F026, DAFDA320]
[2018-12-05 22:23:19,818][WARN ][pool-1-thread-1][RestExecutor] Failed to connect to cluster
[2018-12-05 22:23:20,072][INFO ][pool-1-thread-1][RestExecutor] Connected to cluster [url=http://localhost:8081]
[2018-12-05 22:23:20,072][INFO ][pool-1-thread-1][ClusterListener] Cluster topology changed,
new topology: [DAFDA320]
[2018-12-05 22:23:35,280][INFO ][pool-1-thread-1][ClusterListener] Cluster topology changed,
new topology: [DAFDA320, 8D27EAF1]

Please review.

was (Author: kuaw26):
Please review.

> Web Agent: Improve logging when cluster topology changed
> --------------------------------------------------------
>                 Key: IGNITE-10552
>                 URL: https://issues.apache.org/jira/browse/IGNITE-10552
>             Project: Ignite
>          Issue Type: Task
>          Components: wizards
>            Reporter: Alexey Kuznetsov
>            Assignee: Andrey Novikov
>            Priority: Major
>             Fix For: 2.8
> Web Agent can be configured with several URLs of REST addresses in order to try connect
to next address if current address no longer available.

This message was sent by Atlassian JIRA

View raw message