On Thu, Dec 17, 2015 at 8:00 AM, Midas A wrote:
>
> org.apache.solr.update.CommitTracker._scheduleCommitWithinIfNeeded(CommitTracker.java:118)
>
I seems like you specifies commitWithin that's legal but seems unusual and
doubtful with DIH.
> > rejected from java.util.concurrent.ScheduledThreadPo
Ah. Then it might be that DIH cannot be run in parallel. Though the
exception is much lower in the stack.
Not sure. Maybe somebody else with more knowledge in the commit path can
comment on it.
On 17 Dec 2015 12:21 pm, "Midas A" wrote:
> Alexandre,
>
> *Only two DIH, indexing different data. *
Alexandre,
*Only two DIH, indexing different data. *
On Thu, Dec 17, 2015 at 10:46 AM, Alexandre Rafalovitch
wrote:
> How many? On the same node?
>
> I am not sure if running multiple DIH is a popular case.
>
> My theory, still, that you are running out of a pool size there. Though if
> it hap
How many? On the same node?
I am not sure if running multiple DIH is a popular case.
My theory, still, that you are running out of a pool size there. Though if
it happens with even just two DIH, it could be a different issue.
On 17 Dec 2015 12:01 pm, "Midas A" wrote:
> Alexandre ,
>
> we are ru
Alexandre ,
we are running multiple DIH to index data.
On Thu, Dec 17, 2015 at 12:40 AM, Alexandre Rafalovitch
wrote:
> Are you sending documents from one client or many?
>
> Looks like an exhaustion of some sort of pool related to Commit within,
> which I assume you are using.
>
> Regards,
>
Are you sending documents from one client or many?
Looks like an exhaustion of some sort of pool related to Commit within,
which I assume you are using.
Regards,
Alex
On 16 Dec 2015 4:11 pm, "Midas A" wrote:
> Getting following warning while indexing ..Anybody please tell me the
> reason .
