[
https://issues.apache.org/jira/browse/IGNITE-17717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17610820#comment-17610820
]
Luchnikov Alexander commented on IGNITE-17717:
----------------------------------------------
I'll try to reproduce the problem on the current master.
The problem was related to ${sys:appId}, in the logger configuration, the file
name was set to fileName="${sys:IGNITE_HOME}/work/log/${sys:appId}.log and when
running ./ignite-cdc.sh, ${sys:appId} was set to "ignite-cdc" and all messages
went to ignite-cdc.log. But after the client node started,
appId was set to "ignite" and messages started going to ignite.log.
> Logging cdc in ignite2ignite mode
> ---------------------------------
>
> Key: IGNITE-17717
> URL: https://issues.apache.org/jira/browse/IGNITE-17717
> Project: Ignite
> Issue Type: Task
> Reporter: Luchnikov Alexander
> Assignee: Nikolay Izhikov
> Priority: Major
> Labels: ise
> Attachments: 3b799724-998a-434b-8ca3-eb9877490ce9.png
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> When using cdc in ignite2ignite mode, there is a problem with logging.
> When running ignite-cdc.sh, the log is written to ignite-cdc.log until the
> ignite client starts, after it starts, the recording continues to ignite.log.
> Probably the problem is related to the replacement of appId at the start of
> the client node.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
