Closed sheltonsuen closed 4 months ago
same error happened
What is the version of sr and what are the specific sql statements?
RisingWave: 1.8 SR version: 3.1 with shared data arch
It may be caused by getting the internal host from the SR front end when accessing the SR back end.
It may be caused by getting the internal host from the SR front end when accessing the SR back end.
what's that mean? I'm not quit understand
It is indeed caused by accessing starrocks http port, can you please provide the specific host and port of sr's fe and cn nodes?
you mean this?
host: fe: starrocks-fe-service.dp-prod cn: starrocks-cn-service.dp-prod
you mean this?
host: fe: starrocks-fe-service.dp-prod cn: starrocks-cn-service.dp-prod
okk, thanks, can you test the connectivity between the rw cn node and the sr cn node direct network?
you mean this? host: fe: starrocks-fe-service.dp-prod cn: starrocks-cn-service.dp-prod
okk, thanks, can you test the connectivity between the rw cn node and the sr cn node direct network?
connectivity is good, and actually the SR sink is fine in dev enviorment, only error in prod, maybe it's a local env problem, I will test it in prod later this weekend
I have tested this case in dev/prod envs, still have this kind error, sames like writing to SR is too slow, and then RW cn nodes keep failling, some time sink to mysql will also cause this kind error and it will recover from failling automaticly
This issue has been open for 60 days with no activity.
If you think it is still relevant today, and needs to be done in the near future, you can comment to update the status, or just manually remove the no-issue-activity
label.
You can also confidently close this issue as not planned to keep our backlog clean. Don't worry if you think the issue is still valuable to continue in the future. It's searchable and can be reopened when it's time. 😄
this can be resolved by add sink_decouple param
Describe the bug
We have setup a cluster with multiple compute nodes, every time we trying to start a starrocks sink, the compute nodes keep failling one by one. Our current RW version is 1.8.
And everytime this error happen, the entir cluster keep failing other tasks will be affacted
Error message/log
To Reproduce
No response
Expected behavior
No response
How did you deploy RisingWave?
Helm charts
The version of RisingWave
1.8
Additional context
No response