This seems a little abstract. What I'd do is double check that the SQL is working correctly by running the stored procedure outside of Solr and see what you get. You should also be able to look at the corresponding .properties file and see the inputs used for the delta import. If the data import XML is called "dih-example.xml", then the properties file should be called "dih-example.properties" and be in the same conf directory (for the collection). Example contents are:
#Fri Oct 10 14:53:44 EDT 2014 last_index_time=2014-10-10 14\:53\:44 healthtopic.last_index_time=2014-10-10 14\:53\:44 Again, I'm suggesting you double check that the SQL is working correctly. If that isn't the problem, provide more details on your data import handler, e.g. the XML with some modifications (no passwords). On Thu, Oct 16, 2014 at 2:11 AM, Jay Potharaju <[email protected]> wrote: > Hi > I 'm using DIH for updating my core. I 'm using store procedure for doing a > full/ delta imports. In order to avoid running delta imports for a long > time, i limit the rows returned to a max of 100,000 rows at a given time. > On an average the delta import runs for less than 1 minute. > > For the last couple of days I have been noticing that my delta imports has > been running for couple of hours and tries to update all the records in the > core. I 'm not sure why that has been happening. I cant reproduce this > event all the time, it happens randomly. > > Has anyone noticed this kind of behavior. And secondly are there any solr > logs that will tell me what is getting updated or what exactly is happening > at the DIH ? > Any suggestion appreciated. > > Document size: 20 million > Solr 4.9 > 3 Nodes in the solr cloud. > > > Thanks > J >
