Open hildebrandt opened 8 years ago
@hildebrandt have you solved the issue?
@shamil Unfortunately I did not. I think it necessary to create a Google Cloud implementation. But I did not the time to play with the Google Cloud Storage API.
Would appreciate PR for adding GCS (and/or Azure) support.
I'm trying to setup Apache Zookeper with Netflix Exhibitor on Google Container Engine (Kubernetes). I would prefer to use Google Cloud Storage (instead of Amazon S3) to share configuration.
Google Cloud Storage offers a migration strategy from Amazon S3. Please see: https://cloud.google.com/storage/docs/migrating
I enabled "interoperability access" in my Google Cloud Console, created new key and saved the credentials in a file called "/opt/exhibitor/credentials.properties". I have also created a new bucket called "exhibitor".
My start script looks like this:
During the startup I can see the following log message:
It seems like the endpoint was correctly changed from Amazon S3 to Google Storage.
The Automatic Instance Management tries to change the server list and I can see the following log message:
I checked the bucket content in the Google Cloud Console and I can see a new file called "shared-config". The file contains the Exhibitor properties. It seems like Exhibitor is able to communicate with Google Cloud Storage.
But when Automatic Instance Management tries to change the server list a second time then I get the following log messages:
It seems like after creating the file on Google Cloud Storage the system is in some kind of "locked" modus.
I tried to delete the generated file on Google Cloud Storage but unfortunately it does not help. Exhibitor simply creates the file again and is locked again on the second request.
Do you have any idea what is going on? Is Google Cloud Storage not 100% compatible with Amazon S3 or did I something wrong?
Any help is highly appreciated. Many greetings from Germany.