You are viewing a plain text version of this content. The canonical link for it is here.
Posted to solr-user@lucene.apache.org by Ja...@ustranscom.mil on 2013/04/29 16:15:51 UTC
Bizarre Solr issue
Hello, everyone.
I have a really bizarre Solr issue that I hope someone can help me resolve.
Production environment is *nix running CF 9.0.0, with both Verity and Solr
collections.
Trying to list collections is breaking - one collection in particular is
breaking the CFCOLLECTION action="list": Error message states that the
solrconfig.xml file cannot be found.
I unregistered this collection via CFAdmin, then went into the file system
and deleted the folders for this collection and restarted both Application
and Solr services. Ran the script, again, and still getting the same error
message for the collection that we just completely removed. It's NOT being
cached in the browser.
This is working fine in development (Windows environment, CF9.0.1).
Thoughts/suggestions greatly appreciated.
RE: Bizarre Solr issue
Posted by Ja...@ustranscom.mil.
I don’t know if this will make any difference, or not, but production is two load-balanced servers (as far as I know, both identical).
If I run the script specifically on the first server, it errors as I have described.
If I run the script specifically on the second server, it lists the collections with no issue, but when I try to index the collection from a query, nothing is put into the collection - it will have a size of 0 and a doccount of 0 when the script completes.
Jack
RE: Bizarre Solr issue
Posted by Ja...@ustranscom.mil.
Hello, Alex, and thank you for your reply.
I just looked it up: ColdFusion Server 9 ships with Solr version 1.4.1. Both
dev and production environments use the same version.
The script that I wrote takes environment into consideration - with three
Windows dev environments and one Linux production environment, all paths are
appropriately hardcoded for folder delimiter using a conditional statement -
all Windows environments are similar to "C:\path\to\collection" and the Linux
environment is hardcoded for "/usr/path/to/collection". Although, I _could_
use a "/" for everything because CF Server automatically converts "\" to "/"
in paths, I'm so OCD about coding that I use whichever is correct for which
environment.
How do I access the Solr logs to check? I'm fairly new to collections.
Thank you,
Jack
-----Original Message-----
From: Alexandre Rafalovitch [mailto:arafalov@gmail.com]
Sent: Monday, April 29, 2013 9:24 AM
To: solr-user@lucene.apache.org
Subject: Re: Bizarre Solr issue
Version of Solr would help here. Solr 4+ will log where it find the
collections if enabled (not sure about earlier version). The most likely
problem is related to path. Perhaps you are hardcoding '\'
separator somewhere on Windows and that messes up the path on Unix.
Or you have different Solr version on dev/prod.
I would probably look for path being mentioned in the logs and, if that fails,
using truss/strace
(http://docstore.mik.ua/orelly/unix2.1/unixnut/c02_236.htm) and just check
where solrconfig.xml is being looked for in reality. It is a hammer ('when you
have a hammer....') for sure, but it is often a faster way to get ground-truth
this way and then figure out what's causing it.
Regards,
Alex.
Personal blog: http://blog.outerthoughts.com/
LinkedIn: http://www.linkedin.com/in/alexandrerafalovitch
- Time is the quality of nature that keeps events from happening all at once.
Lately, it doesn't seem to be working. (Anonymous - via GTD
book)
On Mon, Apr 29, 2013 at 10:15 AM, <Ja...@ustranscom.mil> wrote:
> Hello, everyone.
>
> I have a really bizarre Solr issue that I hope someone can help me resolve.
>
> Production environment is *nix running CF 9.0.0, with both Verity and
> Solr collections.
>
> Trying to list collections is breaking - one collection in particular
> is breaking the CFCOLLECTION action="list": Error message states that
> the solrconfig.xml file cannot be found.
>
> I unregistered this collection via CFAdmin, then went into the file
> system and deleted the folders for this collection and restarted both
> Application and Solr services. Ran the script, again, and still
> getting the same error message for the collection that we just
> completely removed. It's NOT being cached in the browser.
>
> This is working fine in development (Windows environment, CF9.0.1).
>
> Thoughts/suggestions greatly appreciated.
Re: Bizarre Solr issue
Posted by Alexandre Rafalovitch <ar...@gmail.com>.
Version of Solr would help here. Solr 4+ will log where it find the
collections if enabled (not sure about earlier version). The most
likely problem is related to path. Perhaps you are hardcoding '\'
separator somewhere on Windows and that messes up the path on Unix.
Or you have different Solr version on dev/prod.
I would probably look for path being mentioned in the logs and, if
that fails, using truss/strace
(http://docstore.mik.ua/orelly/unix2.1/unixnut/c02_236.htm) and just
check where solrconfig.xml is being looked for in reality. It is a
hammer ('when you have a hammer....') for sure, but it is often a
faster way to get ground-truth this way and then figure out what's
causing it.
Regards,
Alex.
Personal blog: http://blog.outerthoughts.com/
LinkedIn: http://www.linkedin.com/in/alexandrerafalovitch
- Time is the quality of nature that keeps events from happening all
at once. Lately, it doesn't seem to be working. (Anonymous - via GTD
book)
On Mon, Apr 29, 2013 at 10:15 AM, <Ja...@ustranscom.mil> wrote:
> Hello, everyone.
>
> I have a really bizarre Solr issue that I hope someone can help me resolve.
>
> Production environment is *nix running CF 9.0.0, with both Verity and Solr
> collections.
>
> Trying to list collections is breaking - one collection in particular is
> breaking the CFCOLLECTION action="list": Error message states that the
> solrconfig.xml file cannot be found.
>
> I unregistered this collection via CFAdmin, then went into the file system
> and deleted the folders for this collection and restarted both Application
> and Solr services. Ran the script, again, and still getting the same error
> message for the collection that we just completely removed. It's NOT being
> cached in the browser.
>
> This is working fine in development (Windows environment, CF9.0.1).
>
> Thoughts/suggestions greatly appreciated.
RE: Bizarre Solr issue
Posted by Ja...@ustranscom.mil.
The logs stdout and stderr are blank. The log request had info, but nothing
that is related.
Persistent flag is set to true in all environments.
After backing up the solr.xml file, the collections were manually erased
from the file allowing me to list collections without breaking! Yay.
This allowed my script to create at least one of the collections. I'm sure
we'll get the other, soon.
Thank you to everyone for your help!
Jack
_______________________________________________
-----Original Message-----
From: Jack.Drysdale.ctr@ustranscom.mil
[mailto:Jack.Drysdale.ctr@ustranscom.mil]
Sent: Monday, April 29, 2013 12:27 PM
To: solr-user@lucene.apache.org
Subject: RE: Bizarre Solr issue
Hello, Shawn, and thanks for your reply.
I will look into this, ASAP. I know that on one of the dev environments the
persistent flag is set to "true"; I'll check the others and the production.
I will also see if someone can get me a copy of the logs from the production
environment to see if any more detail is contained within.
Thanks,
Jack
-----Original Message-----
From: Shawn Heisey [mailto:solr@elyograg.org]
Sent: Monday, April 29, 2013 12:19 PM
To: solr-user@lucene.apache.org
Subject: Re: Bizarre Solr issue
On 4/29/2013 8:15 AM, Jack.Drysdale.ctr@ustranscom.mil wrote:
> Production environment is *nix running CF 9.0.0, with both Verity and
> Solr collections.
>
> Trying to list collections is breaking - one collection in particular
> is breaking the CFCOLLECTION action="list": Error message states that
> the solrconfig.xml file cannot be found.
>
> I unregistered this collection via CFAdmin, then went into the file
> system and deleted the folders for this collection and restarted both
> Application and Solr services. Ran the script, again, and still
> getting the same error message for the collection that we just
> completely removed. It's NOT being cached in the browser.
>
> This is working fine in development (Windows environment, CF9.0.1).
CFCOLLECTION and CFAdmin are not part of Solr. We have no way of knowing
what happens when you do things in CFAdmin. I do have one possible idea of
what might be going wrong here, though.
Here's how multi-core Solr works in all versions prior to 4.3: The directory
named with the solr.solr.home property (defaulting to ./solr) contains a
file called solr.xml. This file describes the index cores that Solr knows
about and defines a few global settings. Solr includes something called the
CoreAdmin API for manipulating cores and solr.xml, which is probably
utilized by CFAdmin.
If the solr.xml file is missing an attribute called persistent on the <solr>
tag, or that attribute is set to false, then changes made using the
CoreAdmin API are not persisted in the solr.xml file on disk, so when Solr
restarts, it will use what it had before.
Note: SolrCloud (4.0 and later) does add the concept of collections - a
cluster-wide view of multiple cores. SolrCloud is not required, and with
version 1.4.1, you won't have to worry about it.
Thanks,
Shawn
RE: Bizarre Solr issue
Posted by Ja...@ustranscom.mil.
Hello, Shawn, and thanks for your reply.
I will look into this, ASAP. I know that on one of the dev environments the
persistent flag is set to "true"; I'll check the others and the production.
I will also see if someone can get me a copy of the logs from the production
environment to see if any more detail is contained within.
Thanks,
Jack
-----Original Message-----
From: Shawn Heisey [mailto:solr@elyograg.org]
Sent: Monday, April 29, 2013 12:19 PM
To: solr-user@lucene.apache.org
Subject: Re: Bizarre Solr issue
On 4/29/2013 8:15 AM, Jack.Drysdale.ctr@ustranscom.mil wrote:
> Production environment is *nix running CF 9.0.0, with both Verity and
> Solr collections.
>
> Trying to list collections is breaking - one collection in particular
> is breaking the CFCOLLECTION action="list": Error message states that
> the solrconfig.xml file cannot be found.
>
> I unregistered this collection via CFAdmin, then went into the file
> system and deleted the folders for this collection and restarted both
> Application and Solr services. Ran the script, again, and still
> getting the same error message for the collection that we just
> completely removed. It's NOT being cached in the browser.
>
> This is working fine in development (Windows environment, CF9.0.1).
CFCOLLECTION and CFAdmin are not part of Solr. We have no way of knowing
what happens when you do things in CFAdmin. I do have one possible idea of
what might be going wrong here, though.
Here's how multi-core Solr works in all versions prior to 4.3: The directory
named with the solr.solr.home property (defaulting to ./solr) contains a
file called solr.xml. This file describes the index cores that Solr knows
about and defines a few global settings. Solr includes something called the
CoreAdmin API for manipulating cores and solr.xml, which is probably
utilized by CFAdmin.
If the solr.xml file is missing an attribute called persistent on the <solr>
tag, or that attribute is set to false, then changes made using the
CoreAdmin API are not persisted in the solr.xml file on disk, so when Solr
restarts, it will use what it had before.
Note: SolrCloud (4.0 and later) does add the concept of collections - a
cluster-wide view of multiple cores. SolrCloud is not required, and with
version 1.4.1, you won't have to worry about it.
Thanks,
Shawn
Re: Bizarre Solr issue
Posted by Shawn Heisey <so...@elyograg.org>.
On 4/29/2013 8:15 AM, Jack.Drysdale.ctr@ustranscom.mil wrote:
> Production environment is *nix running CF 9.0.0, with both Verity and Solr
> collections.
>
> Trying to list collections is breaking - one collection in particular is
> breaking the CFCOLLECTION action="list": Error message states that the
> solrconfig.xml file cannot be found.
>
> I unregistered this collection via CFAdmin, then went into the file system
> and deleted the folders for this collection and restarted both Application
> and Solr services. Ran the script, again, and still getting the same error
> message for the collection that we just completely removed. It's NOT being
> cached in the browser.
>
> This is working fine in development (Windows environment, CF9.0.1).
CFCOLLECTION and CFAdmin are not part of Solr. We have no way of
knowing what happens when you do things in CFAdmin. I do have one
possible idea of what might be going wrong here, though.
Here's how multi-core Solr works in all versions prior to 4.3: The
directory named with the solr.solr.home property (defaulting to ./solr)
contains a file called solr.xml. This file describes the index cores
that Solr knows about and defines a few global settings. Solr includes
something called the CoreAdmin API for manipulating cores and solr.xml,
which is probably utilized by CFAdmin.
If the solr.xml file is missing an attribute called persistent on the
<solr> tag, or that attribute is set to false, then changes made using
the CoreAdmin API are not persisted in the solr.xml file on disk, so
when Solr restarts, it will use what it had before.
Note: SolrCloud (4.0 and later) does add the concept of collections - a
cluster-wide view of multiple cores. SolrCloud is not required, and
with version 1.4.1, you won't have to worry about it.
Thanks,
Shawn