[
https://issues.apache.org/jira/browse/IGNITE-23395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vyacheslav Koptilin reassigned IGNITE-23395:
--------------------------------------------
Assignee: Denis Chudov
> Write logging by the Raft subsystem into a separate file
> --------------------------------------------------------
>
> Key: IGNITE-23395
> URL: https://issues.apache.org/jira/browse/IGNITE-23395
> Project: Ignite
> Issue Type: Improvement
> Components: networking, persistence
> Affects Versions: 3.0
> Reporter: Alexander Belyak
> Assignee: Denis Chudov
> Priority: Critical
> Labels: ignite-3
>
> Raft log on any network error consumes about 1Gb per node / 5 minutes on a
> 3-node cluster!
> # Start 3 node cluter
> # Start creating tables in a loop (create 50 tables, insert 1 rows into each)
> # Kil 1 node
> Expected result:
> The cluster either
> * fails to operate (depending on the configured CMG/MS nodes and killed
> node) or
> * prints a few errors, updates the topology and continues operations.
> Actual result:
> Logs in two remaining nodes contains 20*100Mb files with similar ERRORs:
> * grep "\[ReplicatorGroupImpl\] Fail to check replicator connection to"
> ignite3db* | wc -l
> *2 423 492*
> * grep "\[AbstractClientService\] Fail to connect
> TablesAmountCapacityMultiNodeTest_cluster_1, exception:
> org.apache.ignite.internal.raft.PeerUnavailableException: Peer
> TablesAmountCapacityMultiNodeTest_cluster_1 is unavailable." ignite3db* | wc
> -l
> *2 547 696*
> In just 9 minutes! In each node.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
