[jira] [Commented] (IGNITE-12526) WAL file archiver logging bug

["Mykhaylo Stepanov (Jira)" <ji...@apache.org>]

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

Mykhaylo Stepanov commented on IGNITE-12526:
--------------------------------------------

Sorry for delay, missed this. In my case I am using Ignite embedded to another application, so IgniteInstanceName not set (there can be several apps running on one machine, using different working dirs). But wal file archiver is the part of persistence, and AFAIK can't be disabled. So better just to add null check. Thanks.

> WAL file archiver logging bug
> -----------------------------
>
>                 Key: IGNITE-12526
>                 URL: https://issues.apache.org/jira/browse/IGNITE-12526
>             Project: Ignite
>          Issue Type: Bug
>          Components: persistence
>    Affects Versions: 2.7.6
>            Reporter: Mykhaylo Stepanov
>            Priority: Trivial
>              Labels: easyfix
>
> WAL file archive logs null if instance name not set. Example output:
> {noformat}
> 2020/01/10 20:42:58.355 [wal-file-archiver%null-#84] INFO Copied file{noformat}
>  
> Check for null instance name should be added in FileWriteAheadLogManager.java 
>  
> {code:java}
> private FileArchiver(SegmentAware segmentAware, IgniteLogger log) throws IgniteCheckedException {
>  super(cctx.igniteInstanceName(), "wal-file-archiver%" + cctx.igniteInstanceName(), log,
>  cctx.kernalContext().workersRegistry());
> init(segmentAware);
>  }
> {code}
>  



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