Commit disabled

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Commit disabled

Villacorta, David (Arlington)
Just want to confirm, given the following config settings at solrconfig.xml:

<autoCommit>
      <maxTime>${solr.autoCommit.maxTime:15000}</maxTime>
      <openSearcher>false</openSearcher>
    </autoCommit>

<autoSoftCommit>
      <maxTime>${solr.autoSoftCommit.maxTime:-1}</maxTime>
</autoSoftCommit>

Solr index will not be updated unless created item in Sitecore is manually indexed, right?

Regards
David Villacorta

Notice of Confidentiality
This email contains confidential material prepared for the intended addressees only and it may contain intellectual property of Willis Towers Watson, its affiliates or a third party. This material may not be suitable for, and we accept no responsibility for, use in any context or for any purpose other than for the intended context and purpose. If you are not the intended recipient or if we did not authorize your receipt of this material, any use, distribution or copying of this material is strictly prohibited and may be unlawful. If you have received this communication in error, please return it to the original sender with the subject heading "Received in error," then delete any copies.

You may receive direct marketing communications from Willis Towers Watson. If so, you have the right to opt out of these communications. You can opt out of these communications or request a copy of Willis Towers Watson's privacy notice by emailing [hidden email]<mailto:[hidden email]>.


This e-mail has come to you from Willis Towers Watson US LLC
Reply | Threaded
Open this post in threaded view
|

Re: Commit disabled

Emir Arnautović
Hi David,
Index will get updated (hard commit is happening every 15s) but changes will not be visible until you explicitly commit or you reload core. Note that Solr restart reloads cores.

HTH,
Emir
--
Monitoring - Log Management - Alerting - Anomaly Detection
Solr & Elasticsearch Consulting Support Training - http://sematext.com/



> On 8 Nov 2019, at 12:19, Villacorta, David (Arlington) <[hidden email]> wrote:
>
> Just want to confirm, given the following config settings at solrconfig.xml:
>
> <autoCommit>
>      <maxTime>${solr.autoCommit.maxTime:15000}</maxTime>
>      <openSearcher>false</openSearcher>
>    </autoCommit>
>
> <autoSoftCommit>
>      <maxTime>${solr.autoSoftCommit.maxTime:-1}</maxTime>
> </autoSoftCommit>
>
> Solr index will not be updated unless created item in Sitecore is manually indexed, right?
>
> Regards
> David Villacorta
>
> Notice of Confidentiality
> This email contains confidential material prepared for the intended addressees only and it may contain intellectual property of Willis Towers Watson, its affiliates or a third party. This material may not be suitable for, and we accept no responsibility for, use in any context or for any purpose other than for the intended context and purpose. If you are not the intended recipient or if we did not authorize your receipt of this material, any use, distribution or copying of this material is strictly prohibited and may be unlawful. If you have received this communication in error, please return it to the original sender with the subject heading "Received in error," then delete any copies.
>
> You may receive direct marketing communications from Willis Towers Watson. If so, you have the right to opt out of these communications. You can opt out of these communications or request a copy of Willis Towers Watson's privacy notice by emailing [hidden email]<mailto:[hidden email]>.
>
>
> This e-mail has come to you from Willis Towers Watson US LLC

Reply | Threaded
Open this post in threaded view
|

RE: Commit disabled

Villacorta, David (Arlington)
Thanks for the feedback

Is there a config setting that can be used for explicit commit? I was thinking the <autoCommit> should be handling this already?
In our issue, the changes will only be reflected back to sitecore once we manually indexed  the item with changes

Regards
David Villacorta

-----Original Message-----
From: Emir Arnautović [mailto:[hidden email]]
Sent: Friday, November 08, 2019 7:53 PM
To: [hidden email]
Subject: Re: Commit disabled

Hi David,
Index will get updated (hard commit is happening every 15s) but changes will not be visible until you explicitly commit or you reload core. Note that Solr restart reloads cores.

HTH,
Emir
--
Monitoring - Log Management - Alerting - Anomaly Detection Solr & Elasticsearch Consulting Support Training - https://urldefense.proofpoint.com/v2/url?u=http-3A__sematext.com_&d=DwIFAg&c=3NBXXUKukgVIjVXwt0Rin6h0GAxIKZespWWvcJx4w9c&r=hHHYgXsMRB8bPM5zNhKSH56W7zaV_SQcrmlwXd5ocLI0qfMw_ySz2DWVBjaVtE7v&m=Elg8qsST_TFKjg7Ti53TOSeAEzjrdqn_9X5gqbLJezw&s=5I_RPlXE6z0MGcaCMeNTekm90bN2m81prJ5pJUQFxEo&e=



> On 8 Nov 2019, at 12:19, Villacorta, David (Arlington) <[hidden email]> wrote:
>
> Just want to confirm, given the following config settings at solrconfig.xml:
>
> <autoCommit>
>      <maxTime>${solr.autoCommit.maxTime:15000}</maxTime>
>      <openSearcher>false</openSearcher>
>    </autoCommit>
>
> <autoSoftCommit>
>      <maxTime>${solr.autoSoftCommit.maxTime:-1}</maxTime>
> </autoSoftCommit>
>
> Solr index will not be updated unless created item in Sitecore is manually indexed, right?
>
> Regards
> David Villacorta
>
> Notice of Confidentiality
> This email contains confidential material prepared for the intended addressees only and it may contain intellectual property of Willis Towers Watson, its affiliates or a third party. This material may not be suitable for, and we accept no responsibility for, use in any context or for any purpose other than for the intended context and purpose. If you are not the intended recipient or if we did not authorize your receipt of this material, any use, distribution or copying of this material is strictly prohibited and may be unlawful. If you have received this communication in error, please return it to the original sender with the subject heading "Received in error," then delete any copies.
>
> You may receive direct marketing communications from Willis Towers Watson. If so, you have the right to opt out of these communications. You can opt out of these communications or request a copy of Willis Towers Watson's privacy notice by emailing [hidden email]<mailto:[hidden email]>.
>
>
> This e-mail has come to you from Willis Towers Watson US LLC

Notice of Confidentiality
This email contains confidential material prepared for the intended addressees only and it may contain intellectual property of Willis Towers Watson, its affiliates or a third party. This material may not be suitable for, and we accept no responsibility for, use in any context or for any purpose other than for the intended context and purpose. If you are not the intended recipient or if we did not authorize your receipt of this material, any use, distribution or copying of this material is strictly prohibited and may be unlawful. If you have received this communication in error, please return it to the original sender with the subject heading "Received in error," then delete any copies.

You may receive direct marketing communications from Willis Towers Watson. If so, you have the right to opt out of these communications. You can opt out of these communications or request a copy of Willis Towers Watson's privacy notice by emailing [hidden email]<mailto:[hidden email]>.


This e-mail has come to you from Willis Towers Watson US LLC
Reply | Threaded
Open this post in threaded view
|

Re: Commit disabled

Erick Erickson
Please explain the use case more fully, as what you’re asking makes little sense.

You say “manually indexed the item with changes”. How does that change get to Solr? The autocommit settings are all about how long it takes a doc _after_ it’s indexed in Solr to be searchable. How it gets to Solr has nothing to do with these settings.

Here’s more than you want to know about commits: https://lucidworks.com/post/understanding-transaction-logs-softcommit-and-commit-in-sorlcloud/

Also, you mentioned Sitecore, which uses Solr. Perhaps this more a question for Sitecore?

Best,
Erick

> On Nov 8, 2019, at 7:53 AM, Villacorta, David (Arlington) <[hidden email]> wrote:
>
> Thanks for the feedback
>
> Is there a config setting that can be used for explicit commit? I was thinking the <autoCommit> should be handling this already?
> In our issue, the changes will only be reflected back to sitecore once we manually indexed  the item with changes
>
> Regards
> David Villacorta
>
> -----Original Message-----
> From: Emir Arnautović [mailto:[hidden email]]
> Sent: Friday, November 08, 2019 7:53 PM
> To: [hidden email]
> Subject: Re: Commit disabled
>
> Hi David,
> Index will get updated (hard commit is happening every 15s) but changes will not be visible until you explicitly commit or you reload core. Note that Solr restart reloads cores.
>
> HTH,
> Emir
> --
> Monitoring - Log Management - Alerting - Anomaly Detection Solr & Elasticsearch Consulting Support Training - https://urldefense.proofpoint.com/v2/url?u=http-3A__sematext.com_&d=DwIFAg&c=3NBXXUKukgVIjVXwt0Rin6h0GAxIKZespWWvcJx4w9c&r=hHHYgXsMRB8bPM5zNhKSH56W7zaV_SQcrmlwXd5ocLI0qfMw_ySz2DWVBjaVtE7v&m=Elg8qsST_TFKjg7Ti53TOSeAEzjrdqn_9X5gqbLJezw&s=5I_RPlXE6z0MGcaCMeNTekm90bN2m81prJ5pJUQFxEo&e=
>
>
>
>> On 8 Nov 2019, at 12:19, Villacorta, David (Arlington) <[hidden email]> wrote:
>>
>> Just want to confirm, given the following config settings at solrconfig.xml:
>>
>> <autoCommit>
>>     <maxTime>${solr.autoCommit.maxTime:15000}</maxTime>
>>     <openSearcher>false</openSearcher>
>>   </autoCommit>
>>
>> <autoSoftCommit>
>>     <maxTime>${solr.autoSoftCommit.maxTime:-1}</maxTime>
>> </autoSoftCommit>
>>
>> Solr index will not be updated unless created item in Sitecore is manually indexed, right?
>>
>> Regards
>> David Villacorta
>>
>> Notice of Confidentiality
>> This email contains confidential material prepared for the intended addressees only and it may contain intellectual property of Willis Towers Watson, its affiliates or a third party. This material may not be suitable for, and we accept no responsibility for, use in any context or for any purpose other than for the intended context and purpose. If you are not the intended recipient or if we did not authorize your receipt of this material, any use, distribution or copying of this material is strictly prohibited and may be unlawful. If you have received this communication in error, please return it to the original sender with the subject heading "Received in error," then delete any copies.
>>
>> You may receive direct marketing communications from Willis Towers Watson. If so, you have the right to opt out of these communications. You can opt out of these communications or request a copy of Willis Towers Watson's privacy notice by emailing [hidden email]<mailto:[hidden email]>.
>>
>>
>> This e-mail has come to you from Willis Towers Watson US LLC
>
> Notice of Confidentiality
> This email contains confidential material prepared for the intended addressees only and it may contain intellectual property of Willis Towers Watson, its affiliates or a third party. This material may not be suitable for, and we accept no responsibility for, use in any context or for any purpose other than for the intended context and purpose. If you are not the intended recipient or if we did not authorize your receipt of this material, any use, distribution or copying of this material is strictly prohibited and may be unlawful. If you have received this communication in error, please return it to the original sender with the subject heading "Received in error," then delete any copies.
>
> You may receive direct marketing communications from Willis Towers Watson. If so, you have the right to opt out of these communications. You can opt out of these communications or request a copy of Willis Towers Watson's privacy notice by emailing [hidden email]<mailto:[hidden email]>.
>
>
> This e-mail has come to you from Willis Towers Watson US LLC