I just posted a simple change on SOLR-126... it cancels any pending
activity when you close the UpdateHandler
public void close() throws IOException {
log.info("closing " + this);
iwCommit.lock();
try{
// cancel any pending operations
if( tracker.pending != null ) {
tra
On 2/5/07, Yonik Seeley <[EMAIL PROTECTED]> wrote:
On 2/5/07, Mike Klaas <[EMAIL PROTECTED]> wrote:
> On 2/5/07, Yonik Seeley <[EMAIL PROTECTED]> wrote:
>
> > That's probably a good idea.
> >
> > I was able to get the current version to fail on my PC at work
> > intermittently by running somethin
On 2/5/07, Mike Klaas <[EMAIL PROTECTED]> wrote:
On 2/5/07, Yonik Seeley <[EMAIL PROTECTED]> wrote:
> That's probably a good idea.
>
> I was able to get the current version to fail on my PC at work
> intermittently by running something else that was eating CPU.
Could you try the latest trunk?
On 2/5/07, Yonik Seeley <[EMAIL PROTECTED]> wrote:
That's probably a good idea.
I was able to get the current version to fail on my PC at work
intermittently by running something else that was eating CPU.
Could you try the latest trunk? It should block on pending commits if
they happen to ta
On 2/5/07 11:18 AM, "Yonik Seeley" <[EMAIL PROTECTED]> wrote:
>
> Yes, I think that's it.
> SolrCore.close() shuts down the Executor.
> From the trace, you can see SolrCore closing, then an attempt to open
> up another searcher after that.
>
> The close of the update handler should probably shut
On 2/5/07, Ryan McKinley <[EMAIL PROTECTED]> wrote:
>
> Getting the test to pass is one thing... but this exception is
> another. Is it possible that this could be triggered by normal use of
> Solr? Perhaps by too-frequent commits?
>
I don't *think* so... I haven't seen any trouble while load
On 2/5/07, Ryan McKinley <[EMAIL PROTECTED]> wrote:
>
> Getting the test to pass is one thing... but this exception is
> another. Is it possible that this could be triggered by normal use of
> Solr? Perhaps by too-frequent commits?
>
I don't *think* so... I haven't seen any trouble while load
Getting the test to pass is one thing... but this exception is
another. Is it possible that this could be triggered by normal use of
Solr? Perhaps by too-frequent commits?
I don't *think* so... I haven't seen any trouble while load testing
this on a real system.
I *think* the RejectedExecut
>
> Perhaps we should increase the alloted time _and_ check explicitly if
> an egregious amount of time has passed in the unittest. If so, we can
> skip the test instead of failing it.
That's probably a good idea.
I was able to get the current version to fail on my PC at work
intermittently by
On 2/4/07, Yonik Seeley <[EMAIL PROTECTED]> wrote:
Stack trace:
INFO: Opening [EMAIL PROTECTED] main
Feb 4, 2007 5:19:41 PM org.apache.solr.core.SolrException log
SEVERE: java.util.concurrent.RejectedExecutionException
at
java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExec
On 2/5/07, Mike Klaas <[EMAIL PROTECTED]> wrote:
On 2/4/07, Ryan McKinley <[EMAIL PROTECTED]> wrote:
> hymmm. what do you think the best option is?
>
> Should we increase the time it waits to check if stuff autocommited?
> It currently waits 1 second for something that *should* start an
> autoco
On 2/4/07, Ryan McKinley <[EMAIL PROTECTED]> wrote:
hymmm. what do you think the best option is?
Should we increase the time it waits to check if stuff autocommited?
It currently waits 1 second for something that *should* start an
autocommit within 1/2 sec.
Perhaps we should increase the allo
hymmm. what do you think the best option is?
Should we increase the time it waits to check if stuff autocommited?
It currently waits 1 second for something that *should* start an
autocommit within 1/2 sec.
Is the RejectedExecutionException only thrown because JUnit failed?
or is this an excepti
On 2/4/07, Yonik Seeley <[EMAIL PROTECTED]> wrote:
OK, the wildcard seems to be norton antivirus.
Antivirus on:
BUILD FAILED
Total time: 2 minutes 22 seconds
Antivirus off:
BUILD SUCCESSFUL
Total time: 1 minute 24 seconds
Not yet sure why that would make the difference... and only on this test
OK, the wildcard seems to be norton antivirus.
Antivirus on:
BUILD FAILED
Total time: 2 minutes 22 seconds
Antivirus off:
BUILD SUCCESSFUL
Total time: 1 minute 24 seconds
Not yet sure why that would make the difference... and only on this test.
-Yonik
Removing the directory did not help.
I just tried a fresh checkout on my C: drive, still no dice.
I'll try a reboot, and a remote login to my machine at work next.
-Yonik
On Feb 4, 2007, at 8:34 PM, Yonik Seeley wrote:
On 2/4/07, Ryan McKinley <[EMAIL PROTECTED]> wrote:
is this on your machine or on the apache machine? I have never had a
problem running on my machine.
My local machine happens every time now.
I think Erik said it was failing for him also.
still trying (in vain) to make this fail on my setup...
The one line that looks suspicious from your stack trace is:
WARNING: best effort to remove
C:\DOCUME~1\Yonik\LOCALS~1\Temp\org.apache.solr.update.AutoCommitTest-testMaxDocs-1170627577515
FAILED !
can you delete the directory wher
On 2/4/07, Ryan McKinley <[EMAIL PROTECTED]> wrote:
Can you tell specifically what part triggers the bad behavior? or is
it whenever autocommit gets triggered?
I wish I could be more useful, but from my system (win XP,
jdk1.5.0_07) things look ok...
I'm on WinXP, and it fails on both Java5 (_0
Can you tell specifically what part triggers the bad behavior? or is
it whenever autocommit gets triggered?
I wish I could be more useful, but from my system (win XP,
jdk1.5.0_07) things look ok...
On 2/4/07, Yonik Seeley <[EMAIL PROTECTED]> wrote:
On 2/4/07, Ryan McKinley <[EMAIL PROTECTED]>
On 2/4/07, Ryan McKinley <[EMAIL PROTECTED]> wrote:
is this on your machine or on the apache machine? I have never had a
problem running on my machine.
My local machine happens every time now.
I think Erik said it was failing for him also.
-Yonik
is this on your machine or on the apache machine? I have never had a
problem running on my machine.
The previous error made more sense to me.. it looked like commit did
not actually complete within the given time period. This one seems
more like a Problem.
Do we need to explicitly handle the T
On 2/4/07, Yonik Seeley <[EMAIL PROTECTED]> wrote:
With the latest changes to AutoCommitTest, now I'm getting failures:
[junit] Tests run: 2, Failures: 1, Errors: 0, Time elapsed: 5.593 sec
[junit] Test org.apache.solr.update.AutoCommitTest FAILED
Stack trace:
INFO: Opening [EMAIL PRO
With the latest changes to AutoCommitTest, now I'm getting failures:
[junit] Tests run: 2, Failures: 1, Errors: 0, Time elapsed: 5.593 sec
[junit] Test org.apache.solr.update.AutoCommitTest FAILED
-Yonik
24 matches
Mail list logo
