Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: Create synchronization task error #174

Open
guhezhu01 opened this issue Feb 6, 2025 · 8 comments
Open

[Bug]: Create synchronization task error #174

guhezhu01 opened this issue Feb 6, 2025 · 8 comments

Comments

@guhezhu01
Copy link

Current Behavior

When I create a synchronization task using CDC, the following error occurs:[2025/02/06 15:31:12.349 +08:00] [WARN] [[email protected]/call.go:35] ["retrying of unary invoker failed"] [target=etcd-endpoints://0xc000a016c0/xx.xx.xx.xxx:2379] [attempt=0] [error="rpc error: code = Unauthenticated desc = etcdserver: invalid auth token"]
[2025/02/06 15:31:12.617 +08:00] [WARN] [server/cdc_impl.go:860] ["fail to new replicate meta"] [task_id=7f76782fe75840a2a0ea1a47753a68f7] [error="etcdserver: user name is empty"]
[2025/02/06 15:31:12.626 +08:00] [INFO] [server/cdc_impl.go:408] ["create request done"]
[2025/02/06 15:31:12.626 +08:00] [WARN] [server/cdc_impl.go:410] ["fail to create cdc task"] [req="{"kafka_connect_param":{"address":"","topic":"","enable_sasl":false,"sasl":{}},"milvus_connect_param":{"host":"1xx.1xx.1xx.1xx","port":19530,"enable_tls":false,"username":"cdc","password":"milvuscdc","uri":"","dial_config":{},"channel_num":0,"ignore_partition":false,"connect_timeout":10},"collection_infos":[{"name":"*","positions":null}],"db_collections":null,"rpc_channel_info":{"name":"","position":""},"extra_info":{"enable_user_role":false},"buffer_config":{"period":0,"size":0},"name_mapping":null,"disable_auto_start":false,"positions":null}"] [error="fail to new replicate meta"]
[2025/02/06 15:31:12.626 +08:00] [WARN] [server/server.go:108] ["fail to handle the create request, error: fail to new replicate meta"] [error="fail to new replicate meta"]

Expected Behavior

CDC configuration file

cdc.txt

Steps To Reproduce

No response

Environment

No response

Anything else?

No response

@SimFG
Copy link
Collaborator

SimFG commented Feb 6, 2025

According to the configuration file provided, there should be an error in the configuration sourceConfig. replicateChan.
You can fix it according to the following tips:

# milvus replicate channel name, which is `{msgChannel.chanNamePrefix.cluster}/{msgChannel.chanNamePrefix.replicateMsg}` in the milvus.yaml file
replicateChan: by-dev-replicate-msg

For more configuration details, please refer to: https://github.com/zilliztech/milvus-cdc/blob/main/doc/cdc-usage.md#configuration

@guhezhu01
Copy link
Author

I did not find this configuration item '{msgChannel. chanNameInitialize. cluster}/{msgChannel. chanNameInitialize. reproxeeMsg}' in the milvus. yaml configuration file. How should I configure it. We use Helm cluster installation

@jaime0815
Copy link
Collaborator

@guhezhu01 you can refer this doc https://milvus.io/docs/configure-helm.md?tab=component to set heml chart configuration

@SimFG
Copy link
Collaborator

SimFG commented Feb 6, 2025

You can also try to enter the milvus container directly, view the milvus.yaml file, and find the above two configuration items

@guhezhu01
Copy link
Author

guhezhu01 commented Feb 11, 2025

I am in Milvus The YAML configuration file has modified the parameter as follows:
msgChannel:
chanNamePrefix:
cluster: by-dev-replicate-msg-02
However, executing the synchronization task still generates errors:
[server/server.go:129] ["request receive"] [type=create] [data="{"kafka_connect_param":{"address":"","topic":"","enable_sasl":false,"sasl":{}},"milvus_connect_param":{"host":"","port":0,"enable_tls":false,"uri":"http://10.1xx.1xx.xx:19530","dial_config":{},"channel_num":0,"ignore_partition":false,"connect_timeout":10},"collection_infos":[{"name":"","positions":null}],"db_collections":null,"rpc_channel_info":{"name":"","position":""},"extra_info":{"enable_user_role":false},"buffer_config":{"period":0,"size":0},"name_mapping":null,"disable_auto_start":false,"positions":null}"]
[2025/02/11 15:56:18.068 +08:00] [WARN] [server/cdc_impl.go:860] ["fail to new replicate meta"] [task_id=50ccc07e0f504f45b06b437755c2f917] [error="etcdserver: user name is empty"]
[2025/02/11 15:56:18.076 +08:00] [INFO] [server/cdc_impl.go:408] ["create request done"]
[2025/02/11 15:56:18.076 +08:00] [WARN] [server/cdc_impl.go:410] ["fail to create cdc task"] [req="{"kafka_connect_param":{"address":"","topic":"","enable_sasl":false,"sasl":{}},"milvus_connect_param":{"host":"","port":0,"enable_tls":false,"uri":"http://10.1xx.1xx.xxx:19530","token":"root:Milvus","dial_config":{},"channel_num":0,"ignore_partition":false,"connect_timeout":10},"collection_infos":[{"name":"
","positions":null}],"db_collections":null,"rpc_channel_info":{"name":"","position":""},"extra_info":{"enable_user_role":false},"buffer_config":{"period":0,"size":0},"name_mapping":null,"disable_auto_start":false,"positions":null}"] [error="fail to new replicate meta"]
[2025/02/11 15:56:18.077 +08:00] [WARN] [server/server.go:108] ["fail to handle the create request, error: fail to new replicate meta"] [error="fail to new replicate meta"]

@SimFG
Copy link
Collaborator

SimFG commented Feb 11, 2025

It seems to be a configuration problem. From the log, the collection_infos in the create request is empty. Also, confirm whether the complete log is provided. You can refer to the document first and see if it works properly without modifying anything.

@guhezhu01
Copy link
Author

guhezhu01 commented Feb 11, 2025

The created request collective_infos contains content
curl -X POST http://localhost:8444/cdc
-H "Content-Type: application/json"
-d '{
"request_type": "create",
"request_data": {
"milvus_connect_param": {
"uri": "http://10.108.1xx.xx:19530",
"token":"root:Milvus",
"connect_timeout": 10
},
"collection_infos": [
{
"name": "*"
}
]
}
}'

cdc.log

@SimFG
Copy link
Collaborator

SimFG commented Feb 12, 2025

Image
It seems that the cdc service cannot connect to the etcd service. You can try to communicate with the etcd service on the machine where the cdc is located. It seems to me that the network between containers cannot communicate.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants