You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Nikolay Izhikov (Jira)" <ji...@apache.org> on 2022/09/28 16:14:00 UTC
[jira] [Commented] (IGNITE-17717) Logging cdc in ignite2ignite mode
[ https://issues.apache.org/jira/browse/IGNITE-17717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17610644#comment-17610644 ]
Nikolay Izhikov commented on IGNITE-17717:
------------------------------------------
[~AldoRaine] default logging properties leads to correct behaviour.
Can you, please, clarify configuration that leads to exception. !3b799724-998a-434b-8ca3-eb9877490ce9.png!
> 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
>
>
> 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)