Thanks for the reply I moved the 6.8.8 and the JSON parsing error seems gone. I am trying to do a simple request though I have very weird results: --- Request URL = https://xxx.xxx.xxx.xxx:6666/test2?query=name%3D%3Dfile-020 {'Host': 'xxx.xxx.xxx', 'Content-length': '0', 'X-Amz-Content-SHA256': 'UNSIGNED-PAYLOAD', 'X-Amz-Date': '20200512T053711Z', 'Authorization': 'AWS4-HMAC-SHA256 Credential=xxxxxxxxxxxxxxxxxx/20200512/us-east-1/s3/aws4_request, SignedHeaders=host;x-amz-content-sha256;x-amz-date, Signature=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx'} Response Response code: 200 <SearchMetadataResponse><Marker></Marker><IsTruncated>false</IsTruncated></SearchMetadataResponse> SearchMetadataResponse: None Marker: None IsTruncated: false --- ________________________________ From: Cervigni, Luca (Pawsey, Kensington WA) <Luca.Cervigni@csiro.au> Sent: Monday, 11 May 2020 4:34 PM To: Peter Parker <346415320@qq.com>; Luca Cervigni <luca.cervigni@pawsey.org.au> Subject: Re: Re:[ceph-users] Elasticsearch Sync module bug ? Thanks Peter for your reply. Could you point me out to the correct settings to put? I tried as well ES 6.8 without success. I just use the default docker container that the ES documentations points out. Could you give me a little more details? Many thanks Regards, Luca Cervigni ________________________________ From: Peter Parker <346415320@qq.com> Sent: Monday, 11 May 2020 4:00 PM To: Luca Cervigni <luca.cervigni@pawsey.org.au> Subject: Re:[ceph-users] Elasticsearch Sync module bug ? Hi, Luca In my env, ES 7.x is not a valid metadata tier by default for reasons such as index type. but it could be fixed by changing default setting. (I haven't tried) I use ES 6.8 instead and it works fine. ------------------ Original ------------------ From: "Luca Cervigni"<luca.cervigni@pawsey.org.au>; Date: Mon, May 11, 2020 12:27 PM To: "ceph-users"<ceph-users@ceph.io>; Subject: [ceph-users] Elasticsearch Sync module bug ? Hello, I have a two zones cluster. Default zone + a ES sync zone where I would like to index metadata and do searches via the ES tier gateway. Struggling to get this service running (documentation is bad and very, very minimal) I thought that in the end I made it work. The requests are getting correctly to the ES zone, I can see the payload sent to ES with debug rgw = 20, ES returns OK then an error is trigger, apparently a JSON parsing error taking the ES search and giving it back to the user. I tried with Nautilus, Octopus, and different versions of ES, from 6 to 7. I have no possibilities of downgrades as our production cluster is on nautilus. Here the logs: https://pastebin.com/hnj8YysK I would think this is a bug, but would like your opinion. If not a bug how shall I solve this? I am using a handmade S3 tool to query as boto is not supported anymore, obo just does not work, and boto3 cannot send any arbitrary requests anymore. Also I would like to know if those Sync modules are still supported or not. The documentation is very poor and if they still are in the roadmap, it should be improved. Thanks Cheers, Luca Cervigni Pawsey Supercomputing centre _______________________________________________ ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an email to ceph-users-leave@ceph.io