Hello everyone, I have the same problem using ES 1.4.4.
Did someone came up with a better solution ? Any help would be greatly appreciated. Thank you, Xavier On Monday, December 1, 2014 at 11:21:14 AM UTC+1, Tom wrote: > > Hi, > > i still have same problems with completion suggest duplicates of old and > updates data using ES 1.4.x > Only way that fixed it so far was using _optimize?max_num_segments=1 which > has performance and maybe other impacts i assume. > > Is there another solution than _optimize?max_num_segments=1? > > Thx > Tom > > > Am Montag, 28. April 2014 11:21:49 UTC+2 schrieb Kaspars Sprogis: >> >> Hi, >> >> I have exactly same problem. >> I resolved duplicates and appearance of deleted items by running >> "_optimize?only_expunge_deletes=true" on daily basis. >> >> However i have still problem with updates. Even if data have been updated >> for items in index, they still show old data when searching. >> Only solution i found is running: "_optimize?max_num_segments=1'". >> >> However i have quite a lot of updates and this get me worried, because of >> Alexander's note: >> >>> if you do regular updates on that index, you should not update down to >>> one single segment >> >> >> Alexander Reelsen, could you please advise, why we shouldn't do that or >> does this create some permanent damage for optimization logic or does it >> affects performance for search later? >> What should we do instead? >> >> Thank you. >> >> On Wednesday, April 23, 2014 1:52:16 AM UTC+3, Alexander Reelsen wrote: >>> >>> Hey >>> >>> if you do regular updates on that index, you should not update down to >>> one single segment. Do you have an example, where the updates do not work >>> as expected? >>> >>> >>> --Alex >>> >>> >>> On Tue, Apr 22, 2014 at 10:51 AM, kidkid <[email protected]> wrote: >>> >>>> Hey Alexander, >>>> Thanks for your reply. >>>> Currently I also manual do optimize by running optimize: >>>> host:9200/completion_index/_optimize?max_num_segments=1 >>>> I think it's a work around solution. I would like to make it better. >>>> >>>> Sometime, I also have problem with update payload, when I change >>>> payload, the completion is not change too. >>>> >>>> >>>> On Monday, April 21, 2014 7:26:13 PM UTC+7, Alexander Reelsen wrote: >>>> >>>>> Hey, >>>>> >>>>> the output is used to unify the search results, otherwise the input is >>>>> used. The payload itself is just meta information. >>>>> The main reason, why you see the suggestion twice is, that even though >>>>> a document is deleted and cannot be found anymore, the suggest data >>>>> structures are only cleaned up during merges/optimizations. Running >>>>> optimize should fix this. >>>>> >>>>> Makes sense? >>>>> >>>>> >>>>> --Alex >>>>> >>>>> >>>>> >>>>> On Sun, Apr 13, 2014 at 12:49 PM, kidkid <[email protected]> wrote: >>>>> >>>>>> I have figure out the problem. >>>>>> The main problem is I have used the same output for all input then ES >>>>>> have been wrong in this case. >>>>>> >>>>>> I still trying to improve the performance. I am just test on 64Gb Ram >>>>>> server (32Gb for ES 1.0.1) 24 core. >>>>>> Have only 2 record but it took me 3ms to suggest. >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> On Sunday, April 13, 2014 4:53:21 PM UTC+7, kidkid wrote: >>>>>>> >>>>>>> There are something really strange. >>>>>>> I don't know whether anyone have worked with this such feature or >>>>>>> it's just not-stable feature. >>>>>>> If we do index same input, and different output,payload, then only >>>>>>> one result found. >>>>>>> >>>>>>> Do anyone tell me how could I fix it ? >>>>>>> >>>>>>> >>>>>>> -- >>>>>> You received this message because you are subscribed to the Google >>>>>> Groups "elasticsearch" group. >>>>>> To unsubscribe from this group and stop receiving emails from it, >>>>>> send an email to [email protected]. >>>>>> To view this discussion on the web visit https://groups.google.com/d/ >>>>>> msgid/elasticsearch/f6547a58-c002-4ff3-80c9-2052e1d14ddd% >>>>>> 40googlegroups.com >>>>>> <https://groups.google.com/d/msgid/elasticsearch/f6547a58-c002-4ff3-80c9-2052e1d14ddd%40googlegroups.com?utm_medium=email&utm_source=footer> >>>>>> . >>>>>> >>>>>> For more options, visit https://groups.google.com/d/optout. >>>>>> >>>>> >>>>> -- >>>> You received this message because you are subscribed to the Google >>>> Groups "elasticsearch" group. >>>> To unsubscribe from this group and stop receiving emails from it, send >>>> an email to [email protected]. >>>> To view this discussion on the web visit >>>> https://groups.google.com/d/msgid/elasticsearch/b3bf74ad-c729-4e78-9ebd-364c6c000819%40googlegroups.com >>>> >>>> <https://groups.google.com/d/msgid/elasticsearch/b3bf74ad-c729-4e78-9ebd-364c6c000819%40googlegroups.com?utm_medium=email&utm_source=footer> >>>> . >>>> >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> >>> -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/b06125c6-de2f-4d8f-906d-2b66d35207eb%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
