mysql 匯入 k8s clusetr的starrocks
- Dominant language
- Java
- Stars
- 17.4k
- Forks
- 5.7k
- PR merge metrics
- No merged PRs in 30d
Description
在寫入be時候會發生
2023-09-25 11:35:08.200 [Thread-1] WARN StarRocksWriterManager - Failed to flush batch data to StarRocks, retry times = 0
java.net.UnknownHostException: starrockscluster-sample-be-0.starrockscluster-sample-be-search.starrocks.svc.cluster.local: 未知的名稱或服務
at java.net.Inet6AddressImpl.lookupAllHostAddr(Native Method) ~[na:1.8.0_382]
at java.net.InetAddress$2.lookupAllHostAddr(InetAddress.java:867) ~[na:1.8.0_382]
at java.net.InetAddress.getAddressesFromNameService(InetAddress.java:1302) ~[na:1.8.0_382]
at java.net.InetAddress$NameServiceAddresses.get(InetAddress.java:815) ~[na:1.8.0_382]
at java.net.InetAddress.getAllByName0(InetAddress.java:1291) ~[na:1.8.0_382]
at java.net.InetAddress.getAllByName(InetAddress.java:1144) ~[na:1.8.0_382]
at java.net.InetAddress.getAllByName(InetAddress.java:1065) ~[na:1.8.0_382]
at com.starrocks.shade.org.apache.http.impl.conn.SystemDefaultDnsResolver.resolve(SystemDefaultDnsResolver.java:45) ~[starrockswriter-1.1.0.jar:na]
請問有甚麼方法可以解決這個問題?
Contributor guide
No contributing guide indexed for this repository
Research direction
Start at StarRocksWriterManager and the StarRocks writer configuration, then reproduce the write in the reported Kubernetes cluster while checking resolution of the reported hostname. Done means the import can write to the BE without the reported UnknownHostException, with the required configuration or fix documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, kubernetes, mysql
- Domain
- databases, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100