-
Notifications
You must be signed in to change notification settings - Fork 467
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
Static Push can not push to some regions #12267
Comments
Also, in this case the Static Published kept aggressively trying to republish even though it was never going to success. Error handling behavior is tough to get perfect, but in this case where we get a 400 from the AWS S3 API it should just fail. |
I think the problem could be that we are creating a AmazonS3Client without specifying the Region and then the headBucket method says that:
We can use this method: setRegion(Region region) |
might be related to #12187 |
To solve this issue I had to tackle 2 problems:
Some improvements in our logic was required. Hopefully, it will improve the performance as well. PR Core P8: #12320 |
dotCMS/core#12267 Repackaging aws libraries
Important for testing: Different static push scenarios where content is pushed to:
Also, please consider to push more than one host and multilingual content |
PR Core (master): #12324 |
Passed QA. Successfully pushed content to different regions such as us-east-2 / us-west-2 / ca-central-1 / sa-east-1 |
PR core (master): #12448 |
Note to QA: Retest this after upgrade of Hazelcast |
Passed QA. Successfully pushed after Hazelcast upgrade to different regions such as us-east-2 / us-west-2 / ca-central-1 / sa-east-1 |
Static configuration as follows:
https://gist.github.com/chrismccracken/cde1973cf86af04d920d6096dd7420ba
The text was updated successfully, but these errors were encountered: