Hey we face similar kind of issue . Our version of Solr is 8.5.1.Also we run
as docker containers in ubuntu server.
Could you provide similar solution ?
--
Sent from: https://lucene.472066.n3.nabble.com/Solr-User-f472068.html
Hi everybody,
I'm currently using solr 8.3.1. While working on tests for a solr plugin I'm
writing , I realized that the SolrResourceLoader used by a SolrCore is not
closed, when calling SolrCore.close().
This leads to open file handles. Can anybody explain this behavior?
Be
didn't see it.
>
> When loading / refreshing the Admin UI in 8.5.1, it briefly but *visibly*
> shows a placeholder for the "SolrCore Initialization Failures" error
> message, with a lot of redness. It looks like there is a real problem.
> Obviously the message th
Sorry if this has already been raised, but I didn't see it.
When loading / refreshing the Admin UI in 8.5.1, it briefly but *visibly*
shows a placeholder for the "SolrCore Initialization Failures" error
message, with a lot of redness. It looks like there is a real problem.
Obviou
chance using Internet Explorer? (See
>> https://stackoverflow.com/questions/56262704/solr-solrcore-initialization-failures-core-error
>> )
>>
>> Jan
>>
>> > 5. mar. 2020 kl. 22:03 skrev Ryan W :
>> >
>> > Hi all,
>> >
>> > On my dev server,
wrote:
> v6.6.0 is from 2017 and not supported anymore. You are really encouraged
> to upgrade!
>
> Are you by any chance using Internet Explorer? (See
> https://stackoverflow.com/questions/56262704/solr-solrcore-initialization-failures-core-error
> )
>
> Jan
>
> >
v6.6.0 is from 2017 and not supported anymore. You are really encouraged to
upgrade!
Are you by any chance using Internet Explorer? (See
https://stackoverflow.com/questions/56262704/solr-solrcore-initialization-failures-core-error)
Jan
> 5. mar. 2020 kl. 22:03 skrev Ryan W :
>
&g
Hi all,
On my dev server, in the Solr admin UI, I see...
SolrCore Initialization Failures
{{core}}: {{error}}
Please check your logs for more information
{{exception.msg}}
These appear to be template variables, but they are never populated. They
just dump to the screen. There
"solr-user@lucene.apache.org"
Subject: Unable to run solr | SolrCore Initialization Failures {{Core}}:
{{error}}
Hi,
I am trying to install Solr for my Windows Server 2016 Standard edition. .
While the installation of Solr itself succeeds, I am not able to get it running.
Everytime after installat
it
>> running.
>>
>> Everytime after installation and starting the service
>>
>> “SolrCore Initialization Failures {{Core}}: {{error}}”
>>
>>
>>
>> I am not sure what the error is since it is not very clear. Also, the log
>> files are all em
nstall Solr for my Windows Server 2016 Standard edition. .
> While the installation of Solr itself succeeds, I am not able to get it
> running.
>
> Everytime after installation and starting the service
>
> “SolrCore Initialization Failures {{Core}}: {{error}}”
>
>
>
> I am
Hi,
I am trying to install Solr for my Windows Server 2016 Standard edition. .
While the installation of Solr itself succeeds, I am not able to get it
running.
Everytime after installation and starting the service
“SolrCore Initialization Failures {{Core}}: {{error}}”
I am not sure what the
Hi Sid,
1. Does folder/configuration actually exist (ie: Did you copy the folder to
/opt/solr/server/solr/nutch/conf/ )?
Yes the configuration does exist
2. I noticed you wrote that you are using Nutch 1.5. Is that a typo for
Nutch 1.15?
It was a typo. I am using Nutch 1.15
3. Have you tr
Hi,
I am getting the following error while creating a core in Solr 8.0.0
"ERROR: Error CREATEing SolrCore 'nutch': Unable to create core [nutch]
Caused by: invalid boolean value:"
Command I am using to create the core:
#/opt/solr/bin/solr create -c nutch -d /opt/solr/se
ation Technology
Université d'Ottawa | University of Ottawa
1 Nicholas (801)
613-562-5800 ext. 7512
-Original Message-
From: vishal.thumm...@its.ny.gov [mailto:vishal.thumm...@its.ny.gov]
Sent: April 1, 2019 5:11 PM
To: solr-user@lucene.apache.org
Subject: ERROR: Error CREATEing SolrC
Hi,
I am getting the following error while creating a core in Solr 8.0.0
"ERROR: Error CREATEing SolrCore 'nutch': Unable to create core [nutch]
Caused by: invalid boolean value:"
Command I am using to create the core:
#/opt/solr/bin/solr create -c nutch -d /opt/solr/se
PM
To: vishal patel
Subject: Re: SolrCore Initialization Failures in Solr 8.0.0
You might as well just start over. Solr 8 will not read an index that’s ever
been touched by Solr 6. Actually, it’s Lucene that won’t open the index. So you
have to re-index from scratch into a new collection.
i36>
From: Erick Erickson
Sent: Wednesday, March 27, 2019 9:15:50 PM
To: vishal patel
Subject: Re: SolrCore Initialization Failures in Solr 8.0.0
There is no need whatsoever to make a folder structure. Solr will create the
proper local file system _for_ you wh
successfully up without
making a configsets in solr 6.1.0.
<http://aka.ms/weboutlook>
From: Erick Erickson
Sent: Tuesday, March 26, 2019 8:16 PM
To: solr-user@lucene.apache.org
Subject: Re: SolrCore Initialization Failures in Solr 8.0.0
How did you creat
successfully up without
making a configsets in solr 6.1.0.
Sent from Outlook<http://aka.ms/weboutlook>
From: Erick Erickson
Sent: Tuesday, March 26, 2019 8:16 PM
To: solr-user@lucene.apache.org
Subject: Re: SolrCore Initialization Failures in Solr 8.0.0
H
> [?:1.8.0_45]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> [?:1.8.0_45]
> at java.lang.Thread.run(Thread.java:745) [?:1.8.0_45]
> 2019-03-26 13:06:49.382 ERROR
> (coreContainerWorkExecu
:192.168.100.145:7991_solr) [
] o.a.s.c.CoreContainer Error waiting for SolrCore to be loaded on startup
org.apache.solr.common.SolrException: Unable to create core [product]
at
org.apache.solr.core.CoreContainer.createFromDescriptor(CoreContainer.java:1210)
~[solr-core-8.0.0.jar:8.0.0
So I don't know what to recommend except rebooting.
Solr (actually, Lucene) would _not_ delete that file without
replacing it. There is a great deal of care taken to insure
that the index is consistent and I haven't heard of the
segments file disappearing by itself, some external process
is very l
@Erick Erickson
Thanks for your feedback and support.
segments* file is missing from
/solr/solr-6.4.1/server/solr/coreStore_shard1_replica1/data/index directory.
Erick: Is that directory the one you expect for that replica? This is a
sanity check, as there's no reason it would change magically.
had to reboot server hardware maintenance
> activity and post reboot it stopped working. There was no software upgrade
> done during this activity.
>
> I tried to run checkIndex but it failed to execute.
>
> On the sol
reboot it stopped working. There was no software upgrade
done during this activity.
I tried to run checkIndex but it failed to execute.
On the solr front end I am getting "SolrCore Initialization Failures"
coreStore_shard
On 8/30/2018 3:14 AM, Salvo Bonanno wrote:
The solr version in both enviroment is 7.4.0
Looks that there was a problem using the intPointField type for a key
field in my schema, I've changed the type to string and now everything
works.
Seeing that problem in 7.4.0 definitely sounds like you've
The solr version in both enviroment is 7.4.0
Looks that there was a problem using the intPointField type for a key
field in my schema, I've changed the type to string and now everything
works.
Thanks everyone for the replies.
On Wed, Aug 29, 2018 at 9:39 PM Shawn Heisey wrote:
>
> On 8/29/2018 1
On 8/29/2018 1:27 AM, Salvo Bonanno wrote:
[error]
corename:
org.apache.solr.common.SolrException:org.apache.solr.common.SolrException:
Could not load conf for core corename: Can't load schema
/opt/solr/server/solr/corename/conf/managed-schema: Plugin init
failure for [schema.xml] fieldType "lo
What versions of Solr? Point fields were introduced in around Solr
6.2. It looks like your new server is running some earlier version of
Solr perhaps?
Best,
Erick
On Wed, Aug 29, 2018 at 12:27 AM Salvo Bonanno wrote:
>
> Hello Everyone!
>
> I have a strange problem, I'm trying to move an existing
Hello Everyone!
I have a strange problem, I'm trying to move an existing and working
configuration of Apache Solr from a server to another one.
The configuration is really simple since it's still incomplete, i've
just create the core and create a managed-schema.
The core is running flawlessy on
18:01
> To: solr-user@lucene.apache.org; solr-user
> Subject: RE: Collection reload leaves dangling SolrCore instances
>
> Sounds just like it, i will check it out!
>
> Thanks both!
> Markus
>
>
>
> -Original message-
> > From:Erick Erickson
> >
Thanks for your response.
None of the processes are deleting any index files.
One data directory is only pointed by one core.
We are writing data at a high ingestion rate (100,000 records per second).
Commit happens once every 30 seconds.
Also a periodic service runs to backup the data to our ba
Thanks for your response.
None of the processes are deleting any index files.
One data directory is only pointed by one core.
We are writing data at a high ingestion rate (100,000 records per second).
Commit happens once every 30 seconds.
Also a periodic service runs to backup the data to our ba
l errors.
I've never heard of Solr/Lucene mysteriously deleting index files, so
I suspect something outside of Solr is doing this.
Best,
Erick
On Mon, Jun 11, 2018 at 11:25 AM, shefalid wrote:
> Hi,
>
> I am using solr 7.2.1
> Every now & then some of the cores fail to load
Hi,
I am using solr 7.2.1
Every now & then some of the cores fail to load due to "SolrCore
Initialization Failure".
>From error message it looks like the reason for failure is the core missing
some of the files:
org.apache.solr.common.SolrException:org.apache.solr.common.Sol
Sounds just like it, i will check it out!
Thanks both!
Markus
-Original message-
> From:Erick Erickson
> Sent: Wednesday 2nd May 2018 17:21
> To: solr-user
> Subject: Re: Collection reload leaves dangling SolrCore instances
>
> Markus:
>
> You may we
ction reload. I removed
>> all custom plugins from solrconfig, dumbed the schema down and removed all
>> custom filters and replaced a customized decompounder with Lucene's vanilla
>> filter, and the problem still exists.
>>
>> After collection reload a second SolrC
stom filters and replaced a customized decompounder with Lucene's vanilla
> filter, and the problem still exists.
>
> After collection reload a second SolrCore instance appears for each real core
> in use, each next reload causes the number of instances to grow. The dangling
>
Lucene's vanilla
filter, and the problem still exists.
After collection reload a second SolrCore instance appears for each real core
in use, each next reload causes the number of instances to grow. The dangling
instances are eventually removed except for one or two. When working locally
On 4/13/2017 4:37 AM, Uchit Patel wrote:
> I have recently moved my cores from SOLR 5.1.0 to 6.4.0. I am using windows
> environment. I have large data in cores. I have total 6 cores with total data
> 142 GB. All cores are migrated perfectly but one is giving error:
>
> SolrCore
Hi,
I have recently moved my cores from SOLR 5.1.0 to 6.4.0. I am using windows
environment. I have large data in cores. I have total 6 cores with total data
142 GB. All cores are migrated perfectly but one is giving error:
SolrCore Initialization Failures
- core_name
ut it makes some assumptions.
>
> Best,
> Erick
>
> On Thu, Dec 29, 2016 at 1:53 AM, Leon STRINGER
> wrote:
> > Hi,
> >
> > I'm new to Solr and am trying to set up a newly installed Solr instance.
> >
> > W
1:53 AM, Leon STRINGER
wrote:
> Hi,
>
> I'm new to Solr and am trying to set up a newly installed Solr instance.
>
> When I try to create a core via the web interface I get:
>
> Error CREATEing SolrCore 'new_core': Unable to create core [new_core] Caused
> b
Hi,
I'm new to Solr and am trying to set up a newly installed Solr instance.
When I try to create a core via the web interface I get:
Error CREATEing SolrCore 'new_core': Unable to create core [new_core] Caused by:
QueryElevationComponent missing config file: 'elevate.xml ei
Thanks Eric.
FirstSearcher and newSearcher events open with two separate searchers. For
the external file field case at least, the cache created with the
firstSearcher is not being used after the newSearcher creates another cache
(with same values)
I believe the warming is also per searcher. So,
firstSearcher and newSeacher are definitely per core, they have to be since they
are intended to warm searchers and searchers are per core.
I don't particularly see the benefit of firing them both either. Not
sure which one makes
the most sense though.
Best,
Erick
On Mon, Oct 3, 2016 at 7:10 PM,
I am using external file fields with larger external files and I noticed
Solr Core Reload loads external files twice: firstSearcher and nextSearcher
event.
Does it mean the Core Reload triggers both events? What is the
benefit/reason of triggering both events at the same time? I see this on
V. 4
On 8/23/2016 4:49 AM, Pranaya Behera wrote:
> In the middle of indexing solrcore gets reloaded and causing 503
> error. Here is the stack trace of the issue.
> Error 503
> {metadata={error-class=org.apache.solr.common.SolrException,root-error-class=org.apache.solr.common.SolrEx
Hi,
In the middle of indexing solrcore gets reloaded and causing 503
error. Here is the stack trace of the issue.
[main] ERROR org.apache.solr.client.solrj.impl.CloudSolrClient - Request
to collection product failed due to (503)
org.apache.solr.client.solrj.impl.HttpSolrClient
Thanks!
-Original Message-
From: Joel Bernstein [mailto:joels...@gmail.com]
Sent: 21 July 2016 19:51
To: solr-user@lucene.apache.org
Subject: Re: Reference to SolrCore from SearchComponent
-- This email has reached the Bank via an external source --
There is a SolrCoreAware
There is a SolrCoreAware interface you can implement, which will provide
access to the SolrCore. From there you can add a closeHook to the core.
Joel Bernstein
http://joelsolr.blogspot.com/
On Thu, Jul 21, 2016 at 2:34 PM, Ellis, Tom (Financial Markets IT) <
tom.el...@lloydsbanking.com.inva
Hi There,
I'm in the process of creating a custom SearchComponent. This component will
have a long running thread performing an action to keep a list updated. As
SearchComponents do not seem to have a destroy/close hook, I was wondering if
there is a way of getting a reference to the Sol
Thanks Shawn!
On Thu, May 5, 2016 at 12:14 PM, Shawn Heisey wrote:
> On 5/5/2016 9:52 AM, Garfinkel, David wrote:
> > I'm new to administering Solr, but it is part of my DAM and I'd like to
> > have a better understanding. If I understand correctly I have a field in
> my
> > schema with uuid 194
On 5/5/2016 9:52 AM, Garfinkel, David wrote:
> I'm new to administering Solr, but it is part of my DAM and I'd like to
> have a better understanding. If I understand correctly I have a field in my
> schema with uuid 1948 that is causing an issue right?
The data being indexed contains a field *name
I'm new to administering Solr, but it is part of my DAM and I'd like to
have a better understanding. If I understand correctly I have a field in my
schema with uuid 1948 that is causing an issue right?
--
David Garfinkel
Digital Asset Management/Helpdesk/Systems Support
The Museum of Modern Art
2
() method of handler class. I am not sure how to get the access of
> : SolrCore in the init method.
>
> you can't access the SolrCore during hte init() method, because at the
> time it's called the SolrCore itself is not yet fully initialized.
>
> what you can do is impleme
: But, To make it better, I would like to load this file only once and in the
: init() method of handler class. I am not sure how to get the access of
: SolrCore in the init method.
you can't access the SolrCore during hte init() method, because at the
time it's called the SolrCore
Hi,
I need to load a file in instance's conf directory and this data is going
to be used in handleRequestBody() implementation. As of now, i am loading
the file in the handleRequestBody method like below.
SolrCore solrCore = req.getCore();
solrCore .getResourceLoader().getLines(fileToLoad);
eload a core :
> http://10.7.23.125:8080/solr/admin/cores?action=RELOAD&core=reportCore_201210_r1
>
> However it give out an exception[1].As the exception the SolrCore
> 'collection1' does not exist. I create a default core not with the name
> 'collection1'.
>
Hi users
I get a very werid problem within solr 4.6
I just want to reload a core :
http://10.7.23.125:8080/solr/admin/cores?action=RELOAD&core=reportCore_201210_r1
However it give out an exception[1].As the exception the SolrCore
'collection1' does not exist. I create a de
n this, recently we have added a two new
> fileds in the scheam.xml file. After this additon, I have restarted the
> tomcat service, its throwing the below error message at console,
> Can you please provide your support,
>
>
> Web Console error message here ->
>
> Sol
->
SolrCore Initialization Failures
ecps-collection_shard3_replica1:
java.lang.RuntimeException:java.lang.RuntimeException: Could not start JMX
monitoring
ecps-shard1-replica-1:
java.lang.RuntimeException:java.lang.RuntimeException: Could not start JMX
monitoring
Please check your logs for more informat
Liu Bo,
Changing the permissions fixed the problem. Thank you for helping me.
Best regards, Jim
--
View this message in context:
http://lucene.472066.n3.nabble.com/SolrCore-collection1-is-not-available-due-to-init-failure-tp4094869p4095195.html
Sent from the Solr - User mailing list archive
org.apache.solr.core.SolrCore.(SolrCore.java:821) ... 13 more Caused
by: org.apache.lucene.store.LockObtainFailedException: Lock obtain timed
out:
NativeFSLock@/usr/share/solr-4.5.0/example/solr/
collection1/data/index/write.lock:
java.io.FileNotFoundException:
/usr/share/solr-4.5.0/example/solr/co
7.42, Solr-4.5.0
Snip of the tomcat startup script:
JAVA_HOME="/usr/lib/jvm/java-7-oracle"
JAVA_OPTS="-Xms128M -Xmx128M";
TOMCAT_USER=tomcat;
TOMCAT_PATH=/usr/share/tomcat;
SHUTDOWN_TIME=30
## Tomcat start/stop script ##
export JAVA_HOME
export JAVA_OPTS
type Status
?
Thanks,
Sathish
--
View this message in context:
http://lucene.472066.n3.nabble.com/Refering-SOLRcore-properties-in-zookeeper-tp4079639.html
Sent from the Solr - User mailing list archive at Nabble.com.
issues
when run against SOLR 3.5.0... I assume this is searching for a default
collection 'collection1'...
Can someone help me with this issue?
org.apache.solr.client.solrj.impl.HttpSolrServer$RemoteSolrException: Server
at http://127.0.0.1:54093 returned non ok status:500, message:{msg
> > > solrhome is my home of solr.
> > >
> > > my solr.xml has that:
> > >
> > > > > host="${host:}" hostPort="${jetty.port:8080}"
> > > hostContext="${hostContext:search}"
> > > zkClientTimeout=&qu
.apache.catalina.startup.Bootstrap start
> >
> > solrhome is my home of solr.
> >
> > my solr.xml has that:
> >
> > > host="${host:}" hostPort="${jetty.port:8080}"
> > hostContext="${hostContext:search}"
> > zkClientTim
; my solr.xml has that:
>
> host="${host:}" hostPort="${jetty.port:8080}"
> hostContext="${hostContext:search}"
> zkClientTimeout="${zkClientTimeout:15000}">
>
>
>
> When I open webpage I get that error:
> *
>
solr.
my solr.xml has that:
When I open webpage I get that error:
*
There are no SolrCores running.
Using the Solr Admin UI currently requires at least one SolrCore.*
When I look catalina.out I see that:
Mar 26, 2013 8:54:35 PM org.apache.solr.cloud.ZkController
publish
INFO
..
Anyway, I'll follow up in JIRA.
--Gregg
[1] https://issues.apache.org/jira/browse/SOLR-4413
On Wed, Feb 6, 2013 at 8:42 PM, Mark Miller wrote:
> Thanks Gregg - can you file a JIRA issue?
>
> - Mark
>
> On Feb 6, 2013, at 5:57 PM, Gregg Donovan wrote:
>
> > M
Thanks Gregg - can you file a JIRA issue?
- Mark
On Feb 6, 2013, at 5:57 PM, Gregg Donovan wrote:
> Mark-
>
> You're right that SolrCore#getIndexDir() did not directly read
> index.properties in 3.6. In 3.6, it gets it indirectly from what is passed
> to the constructor
Mark-
You're right that SolrCore#getIndexDir() did not directly read
index.properties in 3.6. In 3.6, it gets it indirectly from what is passed
to the constructor of SolrIndexSearcher. Here's SolrCore#getIndexDir() in
3.6:
public String getIndexDir() {
synchronized (se
On Feb 6, 2013, at 4:23 PM, Gregg Donovan wrote:
> code we had that relied on the 3.6 behavior of SolrCore#getIndexDir() is
> not working the same way.
Can you be very specific about the different behavior that you are seeing? What
exactly where you seeing and counting on and what a
ng a force option that
guarantees a replication.
- Mark
On Feb 6, 2013, at 4:23 PM, Gregg Donovan wrote:
> In the process of upgrading from 3.6 to 4.1, we've noticed that much of the
> code we had that relied on the 3.6 behavior of SolrCore#getIndexDir() is
> not working t
In the process of upgrading from 3.6 to 4.1, we've noticed that much of the
code we had that relied on the 3.6 behavior of SolrCore#getIndexDir() is
not working the same way.
In 3.6, SolrCore#getIndexDir() would get us the index directory read from
index.properties, if it existed, otherwi
This is perfect, thanks! I'm surprised it eluded me for so long.
From: Mark Miller [markrmil...@gmail.com]
Sent: Tuesday, February 05, 2013 4:09 PM
To: solr-user@lucene.apache.org
Subject: Re: Correct way for getting SolrCore?
The SolrCoreAware inte
then I guess SolrCore.getIndexReaderFactory() is the way to
> go.
>
> Thanks,
> Ryan
>
> From: Ryan Josal [rjo...@rim.com]
> Sent: Tuesday, February 05, 2013 1:27 PM
> To: solr-user@lucene.apache.org
> Subject: RE: Correct way fo
m.com]
Sent: Tuesday, February 05, 2013 1:27 PM
To: solr-user@lucene.apache.org
Subject: RE: Correct way for getting SolrCore?
Is there any way I can get the cores and do my initialization in the @Override
public void init(final NamedList args) method? I could wait for the first
request, but I im
Ryan
From: Mark Miller [markrmil...@gmail.com]
Sent: Tuesday, February 05, 2013 1:15 PM
To: solr-user@lucene.apache.org
Subject: Re: Correct way for getting SolrCore?
The request should give you access to the core - the core to the core
descriptor, the descriptor t
needs to have
> some initialization code in the init method. I need to build some
> information about each SolrCore in memory so that when an update comes in for
> a particular SolrCore, I can use the data for the appropriate core.
> Ultimately, I need a lucene IndexReader for eac
Hey guys,
I am writing an UpdateRequestProcessorFactory plugin which needs to have some
initialization code in the init method. I need to build some information about
each SolrCore in memory so that when an update comes in for a particular
SolrCore, I can use the data for the appropriate
This may be related to SOLR-3939.
I'll try and get to testing it out without that fix.
- Mark
> On Thu, Oct 18, 2012 at 12:52 AM, Minoru Osuka wrote:
>> Hi,
>>
>> I am facing replication problem.
>> I had added a shard replica after the leader's core had been reloaded. I
>> had expected to star
First, why are you reloading the leader? Just as an experiment? I
know there's been some JIRA issues with reloading cores and
SolrCloud...
Second, what's your evidence that replication didn't happen?
For just a few documents the slave index might be updated from
the transaction log and you wouldn'
Hi,
I am facing replication problem.
I had added a shard replica after the leader's core had been reloaded. I
had expected to start index replication, but it hadn't worked.
Please give me some workaround advice.
My operation commands are following.
ZooKeeper localhost:2181
Solr Shard1 Leader loc
You attachment didn't come through, the mail server often
strips this stuff. Please either inline it or put it up on some
publicly accessible place
Best
Erick
On Sun, Mar 11, 2012 at 10:51 PM, Nikhila Pala wrote:
> Hi,
>
> ** **
>
> I’m getting some exceptions while shutting the hybris s
Hi,
I'm getting some exceptions while shutting the hybris server and the exception
details are specifies in the file attached to this mail. Please try to resolve
it as soon as possible.
Thanks & Regards,
Nikhila Pala
Systems engineer
Infosys Technologies Limited
CAUTION - D
docs)?
this is the chicken and the egg problem that i think i mentioned before,
and the reason why most people deal with this type of situation externally
from solr -- plugins like UpdateProcessor's can get a searcher fro mthe
SolrCore, but searchers always represent a snapshot moment in ti
gestion?
>
>
> 2011/12/29 Alessandro Benedetti
>
>> Hi guys,
>> I'm developing a custom SolrEventListener, and inside the PostCommit()
>> method I need to execute some queries and collect results.
>> In my SolrEventListener class, I have a SolrCore
>
ping a custom SolrEventListener, and inside the PostCommit()
> method I need to execute some queries and collect results.
> In my SolrEventListener class, I have a SolrCore
> Object( org.apache.solr.core.SolrCore) and a list of queries (Strings ).
>
> How can I use the SolrCore to optima
Hi guys,
I'm developing a custom SolrEventListener, and inside the PostCommit()
method I need to execute some queries and collect results.
In my SolrEventListener class, I have a SolrCore
Object( org.apache.solr.core.SolrCore) and a list of queries (Strings ).
How can I use the SolrCo
ery("id:"+idDoc);
server.query(query);
When I verify the result : it's OK. (I have 1 document in the docListResult)
In the second class I am using SolrCore for indexing and searching (because
I need 2 indexes) as follows:
servercore2 = new EmbeddedSolrServer(coreContainer, "core2"
Hello every body,
referring to the link : http://wiki.apache.org/solr/CoreAdmin.
I've created a solr.xml file as follows:
So before using SolrCore I instanciated a SolrServer to index and search
documents as follows:
System.setProperty("solr
gt; >I want to know the detail of IndexReader in SolrCore. I read a
> > little codes of SolrCore. Here is my understanding, are they correct?
> >Each SolrCore has many SolrIndexSearcher and keeps them in
> > _searchers. and _searcher keep trace of the latest versio
is there anyone could help me?
2010/10/11 Li Li :
> hi all,
> I want to know the detail of IndexReader in SolrCore. I read a
> little codes of SolrCore. Here is my understanding, are they correct?
> Each SolrCore has many SolrIndexSearcher and keeps them in
> _searchers. and
hi all,
I want to know the detail of IndexReader in SolrCore. I read a
little codes of SolrCore. Here is my understanding, are they correct?
Each SolrCore has many SolrIndexSearcher and keeps them in
_searchers. and _searcher keep trace of the latest version of index.
Each
emory
requirements > 2x indexSize, which for us is a lot since indexSize=8GB.
I'm wondering why it either a) loads the index twice, or b) seems to not
release the 2nd load of the RAMDirectory in memory
--
View this message in context:
http://lucene.472066.n3.nabble.com/SolrCore-Index-Searc
On 10/1/10 9:16 PM, Chris Hostetter wrote:
>
> : > it's the same instance, it's just listed twice.
> : >
> :
> : This comes up again and again - and it is confusing - I wonder if we
> : can't improve what's displayed to make this more clear.
>
> On stats.jsp (or using /admin/mbeans?stats=true)
1 - 100 of 144 matches
Mail list logo
