Skip to content
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

QFS on S3, sepcify endpoint #217

Open
MourIdri opened this issue May 11, 2017 · 2 comments
Open

QFS on S3, sepcify endpoint #217

MourIdri opened this issue May 11, 2017 · 2 comments

Comments

@MourIdri
Copy link

Hi, I would like to store on my object storage which is not aws but minio for instance.
Can you update the documentation to specify the endpoint ? thanks

@kstinsonqc
Copy link
Contributor

The endpoint currently used is http[s]://., where the hostName defaults to s3.amazonaws.com.

You can override hostName by setting the configuration property chunkServer.diskQueue.hostName, using the same object-store-directory-prefix that is used for the bucketName.

Some caveats:
This endpoint used is an implementation detail and may change in the future.
We have done testing only with S3 and not any S3-lookalikes such as minio..

@MourIdri
Copy link
Author

Thanks for the update. plz keep updated the documentation. S3-likes ( think about ceph) does make a lot of sens, however, the performance with Mapreduce associated with object store is a problem. QFs does answer this challenge. I use Minio for test purposes since minio APi and Ceph APi are very similar.
From the business point of view, it might open a lot of doors, sticking with AWS S3 will close a lot.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants