Hi Kevin, good point and I am not really sure about how “disable.configEdit” is set in our setup, but with it being set and the directory not being writable deliberately, the log message would still appear, see https://issues.apache.org/jira/browse/SOLR-15375. The message happens with each core creation and normally does not cause issues.
At least lack of this message shows that there must be something happening (or maybe not happening) between “AutoCommit Soft” and “Cannot write to config directory”. I was just hoping there might be ideas what that could be. Stefan From: Kevin Risden <kris...@apache.org> Date: Tuesday, 10. October 2023 at 17:40 To: users@solr.apache.org <users@solr.apache.org> Subject: Re: Solr 9.2.1: Creation of Core "Hangs" [Sie erhalten nicht häufig E-Mails von kris...@apache.org. Weitere Informationen, warum dies wichtig ist, finden Sie unter https://aka.ms/LearnAboutSenderIdentification ] I don't really have a good idea, but the next log line is: [ blueprint_helios_comments] o.a.s.r.ManagedResourceStorage Cannot write > to config directory /opt/solr-9.2.1/server/solr/configsets/elastic/conf ; > switching to use InMemory storage instead. Do you have permissions on "/opt/solr-9.2.1/server/solr/configsets/elastic/conf" setup correctly? Kevin Risden On Tue, Oct 10, 2023 at 10:45 AM Pieper, Stefan <stefan.pie...@coremedia.com.invalid> wrote: > Hello, > > > > We experienced a problem when creating a core via a request on Solr 9.2.1. > It seems that the core creation for “blueprint_helios_comments“ just > “hangs”. Consequently, with subsequent external requests to create the same > core (since it does not seem to be there yet), Solr detects that the core > creation is already in progress and returns an error. > > > > This is what Solr’s log tells me: > > > > [ blueprint_helios_comments] o.a.s.s.HttpSolrCall [admin] webapp=null > path=/admin/cores > params={core=blueprint_helios_comments&action=STATUS&indexInfo=false&wt=javabin&version=2} > status=0 QTime=1 > > [ blueprint_helios_comments] o.a.s.h.a.CoreAdminOperation core create > command > name=blueprint_helios_comments&action=CREATE&configSet=elastic&wt=javabin&version=2&dataDir=data > > [ blueprint_helios_comments] o.a.s.c.SolrConfig Using Lucene > MatchVersion: 9.4.0 > > [ blueprint_helios_comments] o.a.s.s.IndexSchema Schema name=elastic > > [ blueprint_helios_comments] o.a.s.s.IndexSchema Loaded schema > elastic/1.6 with uniqueid field id > > [ blueprint_helios_comments] o.a.s.c.CoreContainer Creating SolrCore > 'blueprint_helios_comments' using configuration from configset > /opt/solr-9.2.1/server/solr/configsets/elastic, trusted=true > > [ blueprint_helios_comments] o.a.s.c.CachingDirectoryFactory > solr.data.home = /var/solr/data > > [ blueprint_helios_comments] o.a.s.c.SolrCore Opening new SolrCore at > [/var/solr/data/blueprint_helios_comments], > dataDir=[/var/solr/data/blueprint_helios_comments/data/] > > [ blueprint_helios_comments] o.a.s.j.SolrRequestAuthorizer Creating a > new SolrRequestAuthorizer > > [ blueprint_helios_comments] o.a.s.u.UpdateHandler Using UpdateLog > implementation: org.apache.solr.update.UpdateLog > > [ blueprint_helios_comments] o.a.s.u.UpdateLog Initializing UpdateLog: > dataDir= defaultSyncLevel=FLUSH numRecordsToKeep=100 maxNumLogsToKeep=10 > numVersionBuckets=65536 > > [ blueprint_helios_comments] o.a.s.u.CommitTracker Hard AutoCommit: if > uncommitted for 15000ms; > > [ blueprint_helios_comments] o.a.s.u.CommitTracker Soft AutoCommit: if > uncommitted for 3000ms; > > > > The creation stops after “Soft AutoCommit”. During the same run of Solr > and our test suite, other cores are created successfully. > > > > With the next run of the same software on empty directories and attempt to > create the core, everything succeeds: > > > > [ blueprint_helios_comments] o.a.s.s.HttpSolrCall [admin] webapp=null > path=/admin/cores > params={core=blueprint_helios_comments&action=STATUS&indexInfo=false&wt=javabin&version=2} > status=0 QTime=1 > > [ blueprint_helios_comments] o.a.s.h.a.CoreAdminOperation core create > command > name=blueprint_helios_comments&action=CREATE&configSet=elastic&wt=javabin&version=2&dataDir=data > > [ blueprint_helios_comments] o.a.s.c.SolrConfig Using Lucene > MatchVersion: 9.4.0 > > [ blueprint_helios_comments] o.a.s.s.IndexSchema Schema name=elastic > > [ blueprint_helios_comments] o.a.s.s.IndexSchema Loaded schema > elastic/1.6 with uniqueid field id > > [ blueprint_helios_comments] o.a.s.c.CoreContainer Creating SolrCore > 'blueprint_helios_comments' using configuration from configset > /opt/solr-9.2.1/server/solr/configsets/elastic, trusted=true > > [ blueprint_helios_comments] o.a.s.c.CachingDirectoryFactory > solr.data.home = /var/solr/data > > [ blueprint_helios_comments] o.a.s.c.SolrCore Opening new SolrCore at > [/var/solr/data/blueprint_helios_comments], > dataDir=[/var/solr/data/blueprint_helios_comments/data/] > > [ blueprint_helios_comments] o.a.s.j.SolrRequestAuthorizer Creating a > new SolrRequestAuthorizer > > [ blueprint_helios_comments] o.a.s.u.UpdateHandler Using UpdateLog > implementation: org.apache.solr.update.UpdateLog > > [ blueprint_helios_comments] o.a.s.u.UpdateLog Initializing UpdateLog: > dataDir= defaultSyncLevel=FLUSH numRecordsToKeep=100 maxNumLogsToKeep=10 > numVersionBuckets=65536 > > [ blueprint_helios_comments] o.a.s.u.CommitTracker Hard AutoCommit: if > uncommitted for 15000ms; > > [ blueprint_helios_comments] o.a.s.u.CommitTracker Soft AutoCommit: if > uncommitted for 3000ms; > > [ blueprint_helios_comments] o.a.s.r.ManagedResourceStorage Cannot write > to config directory /opt/solr-9.2.1/server/solr/configsets/elastic/conf ; > switching to use InMemory storage instead. > > [ blueprint_helios_comments] o.a.s.s.s.Suggester init: > {threshold=5.0E-4, name=text, > classname=org.apache.solr.spelling.suggest.Suggester, > lookupImpl=org.apache.solr.spelling.suggest.fst.WFSTLookupFactory, > field=text} > > [ blueprint_helios_comments] o.a.s.h.ReplicationHandler Commits will be > reserved for 10000 ms > > [ blueprint_helios_comments] o.a.s.u.UpdateLog Could not find max > version in index or recent updates, using new clock 1779334761811017728 > > > > I can’t recall having seen this issue before nor can I reproduce it, but > I’d like to ask whether this behaviour is known (couldn’t find a Jira issue > or mail thread connected to this) or anybody has an idea what might be > going wrong. > > > > Thanks! > > Stefan > > > > -- > > Stefan Pieper > Senior Software Engineer > > [image: A picture containing graphics, graphic design, font, logo > Description automatically generated] <https://www.coremedia.com/> > > > > *Elevate Experience. Drive Impact.* > > > E-Mail: stefan.pie...@coremedia.com > > *www.coremedia.com* <https://www.coremedia.com/> > > [image: A pink and red letter on a black background Description > automatically generated with low confidence] > <https://www.linkedin.com/company/coremedia-corp/>[image: A logo of a > camera Description automatically generated with low confidence] > <https://www.instagram.com/coremediacc/>[image: A picture containing > colorfulness, screenshot, graphics, red Description automatically generated] > <https://www.youtube.com/channel/UC3u29ExYv1263SfUBWnsgdQ>[image: A pink > bird with wings Description automatically generated with low confidence] > <https://twitter.com/coremedia?lang=en> > > [image: signature_667434842] > <https://resources.ecovadis.com/library/ecovadis-medals-recognizing-our-customers-achievements> > > > -------------------------------------------------------------------------------- > > CoreMedia GmbH > > Rödingsmarkt 9, 20459 Hamburg, Germany > > Managing Director: Sören Stamer > > Commercial Register: Amtsgericht Hamburg, HRB 162480 > > > -------------------------------------------------------------------------------- > > >
