Hi GW,

 It would be great if you can elaborate or provide pointers to scenarios which 
can cause this issue w.r.t commit problem.

Regards,
Prateek Jain

-----Original Message-----
From: GW [mailto:thegeofo...@gmail.com] 
Sent: 21 November 2016 01:56 PM
To: solr-user@lucene.apache.org
Subject: Re: unable to write docs

Check out Prateeks answer first and use commit wisely.

99% chance it's a commit issue.

On 21 November 2016 at 08:42, Alexandre Rafalovitch <arafa...@gmail.com>
wrote:

> What's the specific error message for 2). And did it only happen once 
> or once in a while?
> ----
> http://www.solr-start.com/ - Resources for Solr users, new and 
> experienced
>
>
> On 22 November 2016 at 00:39, Prateek Jain J 
> <prateek.j.j...@ericsson.com> wrote:
> >
> > 1. Commits are issued every 30 seconds, not on every write operation.
> > 2. logs only has error entries saying it failed to write documents.
> >
> >
> > Regards,
> > Prateek Jain
> >
> > -----Original Message-----
> > From: Alexandre Rafalovitch [mailto:arafa...@gmail.com]
> > Sent: 21 November 2016 12:34 PM
> > To: solr-user <solr-user@lucene.apache.org>
> > Subject: Re: unable to write docs
> >
> > 1) Are you definitely issuing commits?
> > 2) Do you have anything in the logs? You should if that's an 
> > exceptional
> situation.
> >
> > Regards,
> >    Alex.
> > ----
> > http://www.solr-start.com/ - Resources for Solr users, new and
> experienced
> >
> >
> > On 21 November 2016 at 23:18, Prateek Jain J <
> prateek.j.j...@ericsson.com> wrote:
> >>
> >> Hi All,
> >>
> >> We are observing that SOLR is able to query documents but is 
> >> failing to
> write documents (create indexes). This is happening only for one core, 
> other cores are working fine. Can you think of possible reasons which 
> can lead to this? Disk has enough space to write/index and has correct 
> permissions. We are using solr 4.8.1 and not using solr-cloud.
> >>
> >> Although, the error is gone after restarting solr but just curious 
> >> to
> know what can lead to such situation.
> >>
> >>
> >> Regards,
> >> Prateek Jain
> >>
>

Reply via email to