Open mikechengwei opened 2 years ago
What's your command line and configuration file to start TiCDC?
For example , i am not specify log-file
argument :
/cdc server --addr=0.0.0.0:8301 --advertise-addr=basic-ticdc-2.basic-ticdc-peer.default.svc:8301 --gc-ttl=86400
BTW, i use tidb operator deploy ticdc , operator can't set the log-file empty,because ticdc not set the default value .Ref: https://github.com/pingcap/tidb-operator/pull/4473
BTW, i use tidb operator deploy ticdc , operator can't set the log-file empty,because ticdc not set the default value .Ref: pingcap/tidb-operator#4473
Without --log-file
, TiCDC should output logs to the std out. I think the documentation needs update.
BTW, i use tidb operator deploy ticdc , operator can't set the log-file empty,because ticdc not set the default value .Ref: pingcap/tidb-operator#4473
Without
--log-file
, TiCDC should output logs to the std out. I think the documentation needs update.
If user not specify log-file using tool ,the log will output to cdc.log
.
I think ticdc should help tiup and tidb operator unify logfile default value. Instead, tiup and operator each have a log file default value standards, which affects the user experience. @overvenus
What did you do?
Test default server log file. Ref https://docs.pingcap.com/zh/tidb/stable/deploy-ticdc.
What did you expect to see?
output log to cdc.log.
What did you see instead?
None
Versions of the cluster
Upstream TiDB cluster version (execute
SELECT tidb_version();
in a MySQL client):Upstream TiKV version (execute
tikv-server --version
):TiCDC version (execute
cdc version
):