Guodong
Guodong
Hi @karenc-bq, According to my test and comparison between the China region and US region, the clusterInstanceHostPattern option won't help much. Please refer to the different between the below two...
Hi @sergiyvamz Thanks for the quick response. Would you please double confirm if the clusterInstanceHostPattern you mentioned support Aurora failover? According to my test, it doesn't work, that was why...
Hello again @sergiyvamz, thanks for your update. Please pay attention to the Aurora endpoint pattern in China regions at my first post. The point here is the section 'cluster-ctfz3i8jkise' (it...
Hello @sergiyvamz Cluster writer endpoint: guodonb-aurora-mysql57.cluster-ctfz3i8jkise.rds.cn-northwest-1.amazonaws.com.cn Cluster reader endpoint: guodonb-aurora-mysql57.cluster-ro-ctfz3i8jkise.rds.cn-northwest-1.amazonaws.com.cn Instance endpoint: guodonb-aurora-mysql57-instance-1.ctfz3i8jkise.rds.cn-northwest-1.amazonaws.com.cn guodonb-aurora-mysql57-instance-1-cn-northwest-1a.ctfz3i8jkise.rds.cn-northwest-1.amazonaws.com.cn guodonb-aurora-mysql57-instance-2-cn-northwest-1b.ctfz3i8jkise.rds.cn-northwest-1.amazonaws.com.cn
Hi @sergiyvamz I believe the DNS resolution is working fine, I was able to update and select data from the cluster. Please download the TRACE log generated with a failover...
Hi @sergiyvamz Try again please.