You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Pavel Tupitsyn (Jira)" <ji...@apache.org> on 2025/12/11 14:09:00 UTC

[jira] [Resolved] (IGNITE-27307) Migration Tools Ignite3ClusterContainer should flush logs in case of a Timeout

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

Pavel Tupitsyn resolved IGNITE-27307.
-------------------------------------
    Resolution: Fixed

> Migration Tools Ignite3ClusterContainer should flush logs in case of a Timeout
> ------------------------------------------------------------------------------
>
>                 Key: IGNITE-27307
>                 URL: https://issues.apache.org/jira/browse/IGNITE-27307
>             Project: Ignite
>          Issue Type: Improvement
>          Components: migration tools
>    Affects Versions: 3.1
>            Reporter: Tiago Marques Godinho
>            Assignee: Tiago Marques Godinho
>            Priority: Major
>              Labels: ignite-3
>             Fix For: 3.2
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> Currently, the Ignite3ClusterContainer, used by the migration tools, is not flushing the container logs buffer. As a result, we are likely losing some valuable debug information in case of errors.
> What to do:
>  * Review the error-handling logic in Ignite3ClusterContainer#start. Make sure the log buffers are flushed in case of errors either explicitly or implicitly by junit.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)