Issue an explicit commit to be sure. And as to whether the SSL makes a difference... I'm more going on the theory that you happened to look after the autocommit kicked in on the non-SSL case and before that on the SSL case. Admittedly a shot in the dark.
Browser caching issues, have tripped me up more than once too. Best, Erick On Wed, Jun 1, 2016 at 9:26 AM, Ilan Schwarts <ila...@gmail.com> wrote: > Since its working in non ssl, i dont think its commit issue, it is the same > pc, i just update scheme on zoomeeper to https and un-comment the ssl > settings on solr.in.cmd. > On Jun 1, 2016 7:25 PM, "Ilan Schwarts" <ila...@gmail.com> wrote: > >> If a document was added on both cores/nodes. Doesnt it mean the document >> was successfully added and commited? >> On Jun 1, 2016 7:23 PM, "Erick Erickson" <erickerick...@gmail.com> wrote: >> >>> Did you issue a commit? >>> >>> Best, >>> Erick >>> >>> On Wed, Jun 1, 2016 at 8:15 AM, Ilan Schwarts <ila...@gmail.com> wrote: >>> > Hi all, >>> > I have working enviroment SolrCloud 5.2.1, When i am using without SSL, >>> > after adding a document, I can see on the core's information, Under >>> > "statistics" the Last Modified is working good, it writes "Less than a >>> > minuet". >>> > >>> > But when i set the solrcloud to SSL, after adding the document, it is >>> added >>> > to the collection, but the last modified is not updated. >>> > Is this a bug ? known issue ? >>> > >>> > Update: >>> > After restarting all the cores, the value of Last Modified is valid, >>> But it >>> > happens only after restart and not after update ot collection/index >>> document >>> > >>> > >>> > Thanks >>> > >>> > -- >>> > >>> > >>> > - >>> > Ilan Schwarts >>> > >>> > >>> > >>> > -- >>> > >>> > >>> > - >>> > Ilan Schwarts >>> >>
