slow commits and overlapping commits
I managed to get a thread dump during a slow commit:
"resin-tcp-connection-*:5062-129" Id=12721 in RUNNABLE total cpu
time=391530.ms user time=390620.ms at java.lang.String.intern(Native
Method) at
org.apache.lucene.util.SimpleStringInter
I managed to get a thread dump during a slow commit:
"resin-tcp-connection-*:5062-129" Id=12721 in RUNNABLE total cpu
time=391530.ms user time=390620.ms
at java.lang.String.intern(Native Method)
at
org.apache.lucene.util.SimpleStringInterner.intern(SimpleStringInterner.java:74)
at org.apac
I am taking a snapshot after every commit. From looking at the snapshots,
it does not look like the delay in caused by segments merging because I am
not seeing any large new segments after a commit.
I still can't figure out why there is a 2 minutes gap between "start commit"
and "SolrDelectionPol
You can use the postCommit event listener as an callback mechanism to let
you know that a commit has happened.
Bill
On Sun, May 22, 2011 at 9:31 PM, Jeff Crump wrote:
> I don't have an answer to this but only another question: I don't think I
> can use auto-commit in my application, as I have
I don't have an answer to this but only another question: I don't think I
can use auto-commit in my application, as I have to "checkpoint" my index
submissions and I don't know of any callback mechanism that would let me
know a commit has happened. Is there one?
2011/5/21 Erick Erickson
> Well
Well, committing less offside a possibilty . Here's what's probably
happening. When you pass certain thresholds, segments are merged which can
take quite some time. His are you triggering commits? If it's external,
think about using auto commit instead.
Best
Erick
On May 20, 2011 6:04 PM, "Bill
