Just checking in Mary. Were you able to get past this? Have you
considering contacting Adobe for official support?
No, we had to drop the use of Solr at this time,
Just FYI, I did submit a bug report on this, if anyone wants to comment or vote
on it.
Just checking in Mary. Were you able to get past this? Have you
considering contacting Adobe for official support?
No, we had to drop the use of Solr at this time, it wasn't critical enough for
this application to pay for a support ticket (and that involves a heck of red
tape here and takes
Just checking in Mary. Were you able to get past this? Have you
considering contacting Adobe for official support?
On Mon, Apr 11, 2011 at 2:41 PM, Mary Jo Sminkey mary...@cfwebstore.com wrote:
What are you loading into your index (queries or documents)? Can you
provide a code snippet of
To be clear - is this only for your unit tests? Could you possibly
use
sleep() to slow things down a bit? That's a hack - but would allow
you
to keep testing.
Currently it's only showing up on my unit tests, but that's only because I'm
the only one using the application. If multiple
According to this you should be able to comment out caching altogether in
the solrconfig.xml file.
Cool, thanks I'll try that. The info I had from the Solr folks was to set
autowarmCount=0 for all the caching, but that didn't seem to have any effect.
Maybe removing caching completely will do
As an aside, it may be worth looking at the native Solr data import
modules. Can have massive performance benefits over using cfindex.
Dominic
On 11 April 2011 15:33, Mary Jo Sminkey mary...@cfwebstore.com wrote:
According to this you should be able to comment out caching altogether in
the
Cool, thanks I'll try that. The info I had from the Solr folks was to
set autowarmCount=0 for all the caching, but that didn't seem to have
any effect. Maybe removing caching completely will do it.
Sigh, nope I commented out the three types of caches in the config file and
still get the
-
From: Mary Jo Sminkey [mailto:mary...@cfwebstore.com]
Sent: Monday, April 11, 2011 10:27 AM
To: cf-talk
Subject: Re: Solr Errors
Cool, thanks I'll try that. The info I had from the Solr folks was to
set autowarmCount=0 for all the caching, but that didn't seem to have
any effect. Maybe
Message-
From: Mary Jo Sminkey [mailto:mary...@cfwebstore.com]
Sent: Monday, April 11, 2011 10:27 AM
To: cf-talk
Subject: Re: Solr Errors
Cool, thanks I'll try that. The info I had from the Solr folks was to
set autowarmCount=0 for all the caching, but that didn't seem to have
any
Same here and that is basically what we are doing today with Verity. This
whole thread though is making me want to get started on Solr testing since
the plan was eventually to migrate from our Verity solution to Solr.
Hhm, I wonder if I just need to switch over the Verity then? Didn't really
We are planning to test switching off it since the rumor mill is that the
next version of CF will no longer have Verity.
On Mon, Apr 11, 2011 at 11:34 AM, Mary Jo Sminkey mary...@cfwebstore.comwrote:
Hhm, I wonder if I just need to switch over the Verity then? Didn't really
want to redo all
Mary,
What are you loading into your index (queries or documents)? Can you
provide a code snippet of your process?
Carl
On 4/8/2011 9:36 AM, Mary Jo Sminkey wrote:
Well, by doing some research on the Solr boards and lists, I was able to
figure out the problem. It appears to be due to CF
What are you loading into your index (queries or documents)? Can you
provide a code snippet of your process?
Just results of a query, so nothing real earth-shattering. Just wanted to use
Solr to search all my long text fields that hold a considerable amount of data
(users have a search
Well, by doing some research on the Solr boards and lists, I was able to figure
out the problem. It appears to be due to CF committing after every cfindex tag
and this causes Solr to open a new searcher and auto warm it (load from
cache). If you are committing more frequently than the warming
To be clear - is this only for your unit tests? Could you possibly use
sleep() to slow things down a bit? That's a hack - but would allow you
to keep testing.
On Fri, Apr 8, 2011 at 11:36 AM, Mary Jo Sminkey mary...@cfwebstore.com wrote:
Well, by doing some research on the Solr boards and
: Friday, April 08, 2011 2:25 PM
To: cf-talk
Subject: Re: Solr Errors
To be clear - is this only for your unit tests? Could you possibly use
sleep() to slow things down a bit? That's a hack - but would allow you
to keep testing.
On Fri, Apr 8, 2011 at 11:36 AM, Mary Jo Sminkey mary...@cfwebstore.com
-
From: Mark A. Kruger [mailto:mkru...@cfwebtools.com]
Sent: Friday, April 08, 2011 3:37 PM
To: cf-talk
Subject: RE: Solr Errors
Mary Jo,
There has to be a way to disable that warmcache process altogether... don't
you think?
-Mark
Mark A. Kruger, MCSE, CFG
(402) 408-3733 ext 105
Well, technically yes - there was a CHF after 901.
Sorry, I meant for Solr in particular. I can try the hot fix (don't recall if I
installed it or not) but I'm not seeing anything listed that would effect Solr:
http://kb2.adobe.com/cps/862/cpsid_86263.html
MJS
There was definitely fixes for Solr indexing, which I don't
necessarily think will help you, but as a general rule I tend to
recommend getting up to the latest/greatest.
On Wed, Apr 6, 2011 at 8:36 AM, Mary Jo Sminkey mary...@cfwebstore.com wrote:
Well, technically yes - there was a CHF after
Interesting. It almost sounds like a load issue. Was the site under heavy load?
No, not at all. This was just running some unit tests locally. Basically the
tests add a new data point, index it to add it to the collection, then run a
search for it to make sure they are being picked up
Mary Jo,
These are options you can set in the INI files of Solr - along with standard
JVM options. If you have a high traffic solr install you will need to fine
tune it to run according to the amount of traffic you have.
As I mentioned in my other reply, this is *not* happening under load,
I shouldn't imagine adding cflocks will do much good. The error is to
do with the nature of your collections and the way in which the Solr
server is configured (potentially it's JVM settings and or the server
settings themselves). I think your best bet would be to ask the Solr
folks, they'll be
I shouldn't imagine adding cflocks will do much good. The error is to
do with the nature of your collections and the way in which the Solr
server is configured (potentially it's JVM settings and or the server
settings themselves). I think your best bet would be to ask the Solr
folks, they'll be
Are you running the latest CF9? There were Solr fixes past 9.0.0.
On Tue, Apr 5, 2011 at 11:34 AM, Mary Jo Sminkey mary...@cfwebstore.com wrote:
I shouldn't imagine adding cflocks will do much good. The error is to
do with the nature of your collections and the way in which the Solr
server is
Are you running the latest CF9? There were Solr fixes past 9.0.0.
CF9.01 on all boxes, so yes, unless there are other hot fixes past that.
MJS
~|
Order the Adobe Coldfusion Anthology now!
]
Sent: Tuesday, April 05, 2011 2:00 PM
To: cf-talk
Subject: Re: Solr Errors
Are you running the latest CF9? There were Solr fixes past 9.0.0.
CF9.01 on all boxes, so yes, unless there are other hot fixes past that.
MJS
Well, technically yes - there was a CHF after 901.
On Tue, Apr 5, 2011 at 12:59 PM, Mary Jo Sminkey mary...@cfwebstore.com wrote:
Are you running the latest CF9? There were Solr fixes past 9.0.0.
CF9.01 on all boxes, so yes, unless there are other hot fixes past that.
MJS
Interesting. It almost sounds like a load issue. Was the site under heavy load?
On Mon, Apr 4, 2011 at 4:09 PM, Mary Jo Sminkey mary...@cfwebstore.com wrote:
Has anyone else seen these kinds of errors? I keep getting them on CF9.01
when I run cfindex tags to add new data to a Solr
Mary Jo,
These are options you can set in the INI files of Solr - along with standard
JVM options. If you have a high traffic solr install you will need to fine
tune it to run according to the amount of traffic you have.
-Mark
Mark A. Kruger, MCSE, CFG
(402) 408-3733 ext 105
29 matches
Mail list logo
