- Más nuevo
- Más votos
- Más comentarios
Review the IAM roles and permissions in detail - ensure the data share role has the redshift:DescribeClusters and redshift: DescribeClusterSnapshots permissions required. Check S3 bucket access - the role needs to Get access to the bucket where data is staged. Verify the security groups allow all traffic between the Redshift clusters on the data share port 5439. Check if both clusters are in the same VPC and availability zone. Cross AZ shares may have issues. Try creating a share between a different producer and consumer cluster. This can help isolate if a specific cluster is having problems. Scale down the data being shared to the minimum - a single table, no incrementals. See if a very small share works. Capture VPC flow logs during the data share to check for any rejected connections
Contenido relevante
OFICIAL DE AWSActualizada hace un año- OFICIAL DE AWSActualizada hace 2 años
- OFICIAL DE AWSActualizada hace 2 años
- OFICIAL DE AWSActualizada hace 6 meses
Few things to try:
Make sure both clusters are in the same AWS account and region. Cross-account and cross-region data shares can cause issues. Check that the IAM roles and permissions are set up correctly between the clusters. The role on the producer cluster needs access to the consumer cluster. Try recreating the data share or set up a new one between the clusters. There may be some metadata corruption on the existing one. Check your VPC and security group configurations on both clusters. There needs to be connectivity and no blocking of ports. Look at the Redshift logs on both clusters for any other related errors or warnings. Try a lower load to rule out any issues with volume - share fewer tables or limit sync frequency.
Creating a new datashare seem to run into the same issue as well