Hi,
 
I am migrating from solr 1.4 to solr 3.6. I have used the latest 3.6 jars.
 
After indexing for few data, I noticed that the indexing is taking a lot of
time and the statistics are shown below
 
 
 
 
<lst name="statusMessages">
  <str name="Total Requests made to DataSource">1737</str> 
  <str name="Total Rows Fetched">1133174</str> 
  <str name="Total Documents Skipped">0</str> 
  <str name="Full Dump Started">2012-05-11 00:16:03</str> 
  <str name="">Indexing completed. Added/Updated: 434 documents. Deleted 0
documents.</str> 
  <str name="Committed">2012-05-11 00:36:20</str> 
  <str name="Total Documents Processed">434</str> 
  <str name="Time taken">0:20:16.941</str> 
  </lst>
  <str name="WARNING">This response format is experimental. It is likely to
change in the future.</str>
  
  whereas to index the same data in 1.4, it is taking a less time and also
the total request made to datasource is also less in 1.4 compared to 3.6.
  
  Total Requests made to DataSource=5, 
  Total Rows Fetched=3042, 
  Total Documents Skipped=0, 
  Full Dump Started=2012-05-10 01:47:59, 
  Indexing completed. Added/Updated: 434 documents. Deleted 0 documents., 
  Committed=2012-05-10 01:48:34, Optimized=2012-05-10 01:48:34, 
  Total Documents Processed=434, Time taken =0:0:35.760
  
Also, during indexing,  Im getting the following message in the output log
file

SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further
details.

But, i ve placed the latest jar file in both server and client. Is this
issue related to slow indexing?

Is indexing slow in 3.6 compared to 1.4. or am i missing anything here? 
 
Please guide me.
 
Note : I am using the same solr config and schema file as in 1.4 for 3.6.
 
Thanks in advance.

--
View this message in context: 
http://lucene.472066.n3.nabble.com/Slow-indexing-in-solr-3-6-tp3979903.html
Sent from the Solr - User mailing list archive at Nabble.com.

Reply via email to