On 9 March 2017 at 02:09, Yehuda Sadeh-Weinraub <ysadehwe@xxxxxxxxxx> wrote: >> more detailed steps: >> >> 1) impl bucket logging HTTP config API >> + GET bucket logging >> + PUT bucket logging >> + store bucket logging config into bucket attribute >> + add new entry(<bucket_name,bucket_logging_status>) to a sharded >> <bucket_logging.X> rados-object's omap in <.rgw.bl> pool >> (<bucket_logging.X>'s omap head store a marker to track >> progress) > I know I was the one to bring up storing this in omap in earlier > discussion, but maybe instead we could just keep it as data on rados > objects, and just append it. There's no need to do a random access to > specific log entries, everything is just being read and written > serially. Hi~ Yehuda. Is there any advantages to perfer rados-object over omap? Or omap has a obvious disadvantages? -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
