|
On 15/03/18 10:45, Vik Tara wrote:
On 14/03/18 12:31, Amardeep Singh wrote:
Though
I have now another issue because I am using Multisite setup with
one zone for data and second zone for metadata with elastic
search tier.
http://docs.ceph.com/docs/master/radosgw/elastic-sync-module/
When document is encrypted the metadata is not pushed to
elasticsearch and if document is uploaded without encryption it
works fine.
2018-03-14 15:48:02.397490 7f0b4cbce700 20
cr:s=0x560a726c4000:op=0x560a7276e800:20RGWPutRESTResourceCRI15es_obj_metadataiE:
operate()
2018-03-14 15:48:02.397492 7f0b4cbce700 20
cr:s=0x560a726c4000:op=0x560a7276e800:20RGWPutRESTResourceCRI15es_obj_metadataiE:
operate()
2018-03-14 15:48:02.397633 7f0b4cbce700 20 sending
request to http://192.168.95.60:9200/newbucket/object/ee560b67-c330-4fd0-af50-aefff93735d2.4163.1:testdocument:null
2018-03-14 15:48:02.397653 7f0b4cbce700 20 register_request
mgr=0x560a720d5d58 req_data->id=1759,
easy_handle=0x560a7348a000
2018-03-14 15:48:02.397666 7f0b4cbce700 20 run:
stack=0x560a726c4000 is io blocked
2018-03-14 15:48:02.397685 7f0b4b3cb700 20 link_request
req_data=0x560a727fae00 req_data->id=1758,
easy_handle=0x560a733e6000
2018-03-14 15:48:02.397725 7f0b4b3cb700 20 link_request
req_data=0x560a72f31e00 req_data->id=1759,
easy_handle=0x560a7348a000
2018-03-14 15:48:02.398609 7f0b4b3cb700 10
receive_http_header
2018-03-14 15:48:02.398631 7f0b4b3cb700 10 received
header:HTTP/1.1 100 Continue
2018-03-14 15:48:02.398636 7f0b4b3cb700 10 received
header:HTTP/1.1
2018-03-14 15:48:02.398638 7f0b4b3cb700 10
receive_http_header
2018-03-14 15:48:02.398639 7f0b4b3cb700 10 received header:
2018-03-14 15:48:02.398659 7f0b4b3cb700 10
receive_http_header
2018-03-14 15:48:02.398661 7f0b4b3cb700 10 received
header:HTTP/1.1 100 Continue
2018-03-14 15:48:02.398662 7f0b4b3cb700 10 received
header:HTTP/1.1
2018-03-14 15:48:02.398663 7f0b4b3cb700 10
receive_http_header
2018-03-14 15:48:02.398664 7f0b4b3cb700 10 received header:
2018-03-14 15:48:02.443530 7f0b4b3cb700 10
receive_http_header
2018-03-14 15:48:02.443556 7f0b4b3cb700 10 received
header:HTTP/1.1 400 Bad Request
2018-03-14 15:48:02.443563 7f0b4b3cb700 10
receive_http_header
2018-03-14 15:48:02.443565 7f0b4b3cb700 10 received
header:Warning: 299 Elasticsearch-5.6.2-57e20f3 "Content
type detection for rest requests is deprecated. Specify the
content type using the [Content-Type] header." "Wed, 14 Mar
2018 10:17:35 GMT"
2018-03-14 15:48:02.443574 7f0b4b3cb700 10
receive_http_header
2018-03-14 15:48:02.443575 7f0b4b3cb700 10 received
header:content-type: application/json; charset=UTF-8
2018-03-14 15:48:02.443588 7f0b4b3cb700 10
receive_http_header
2018-03-14 15:48:02.443591 7f0b4b3cb700 10 received
header:content-length: 374
2018-03-14 15:48:02.443594 7f0b4b3cb700 10
receive_http_header
2018-03-14 15:48:02.443595 7f0b4b3cb700 10 received header:
2018-03-14 15:48:02.443663 7f0b4cbce700 20
cr:s=0x560a732f4d20:op=0x560a72fa8000:20RGWPutRESTResourceCRI15es_obj_metadataiE:
operate()
2018-03-14 15:48:02.443675 7f0b4cbce700 5 failed to wait
for op, ret=-22: PUT http://192.168.95.60:9200/newbucket/object/ee560b67-c330-4fd0-af50-aefff93735d2.4163.1:testdocument:null
2018-03-14 15:48:02.443754 7f0b4cbce700 20
cr:s=0x560a732f4d20:op=0x560a72fa8000:20RGWPutRESTResourceCRI15es_obj_metadataiE:
operate() returned r=-22
2018-03-14 15:48:02.443773 7f0b4cbce700 20
cr:s=0x560a732f4d20:op=0x560a7276c800:29RGWElasticHandleRemoteObjCBCR:
operate()
2018-03-14 15:48:02.443787 7f0b4cbce700 20
cr:s=0x560a732f4d20:op=0x560a7276c800:29RGWElasticHandleRemoteObjCBCR:
operate() returned r=-22
2018-03-14 15:48:02.443791 7f0b4cbce700 20
cr:s=0x560a732f4d20:op=0x560a72efb800:27RGWElasticHandleRemoteObjCR:
operate()
This change 7 days ago looks like it deals with the encoding that
ES requires.
https://github.com/ceph/ceph/pull/20707/files/13978bb28b7be809033bf24550b21ed2713ddc9b
I'll make a build that incorporates this commit so you can test it
:)
After testing, it looks like that commit does not solve the issue
with indexing encrypted objects - will raise a bug for this / move
the discussion to the dev list.
|
_______________________________________________
ceph-users mailing list
ceph-users@xxxxxxxxxxxxxx
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
