-->
These old forums are deprecated now and set to read-only. We are waiting for you on our new forums!
More modern, Discourse-based and with GitHub/Google/Twitter authentication built-in.

All times are UTC - 5 hours [ DST ]



Forum locked This topic is locked, you cannot edit posts or make further replies.  [ 2 posts ] 
Author Message
 Post subject: Unexpected output from mass indexer
PostPosted: Mon Mar 25, 2013 3:42 pm 
Newbie

Joined: Mon Nov 26, 2012 2:34 pm
Posts: 6
Hi,

I have been using the mass indexer to create my initial index (I'm using a monitor to track its progress). After a recent update from SVN it started a different output than I have seen before.
Quote:
[2013-03-25 12:28:15.361] INFO org.hibernate.stat.ConcurrentStatisticsImpl HQL: null, time: 358ms, rows: 40
[13-03-25 12:28:15.361] {Hibernate Search: entityloader-1} HQL: null, time: 358ms, rows: 40
[2013-03-25 12:28:15.383] INFO org.hibernate.stat.ConcurrentStatisticsImpl HQL: null, time: 17ms, rows: 20
[13-03-25 12:28:15.383] {Hibernate Search: entityloader-2} HQL: null, time: 17ms, rows: 20


This seems to happen hundreds (or thousands) of times in rapid succession. I no longer see the output telling me that "X entities have been indexed, X% Complete". I'm assuming someone else modified something and it's causing the issues but I have been unsuccessful in finding the root cause of the above INFO message.

Since I'm not seeing status updates does this mean the indexer is not working? Any ideas what caused this change in output?

We are running Hibernate Search 3.4.0.Final and Hibernate Core 3.6.3.Final (We are working to upgrade to 4.x of each but this is the current setup). My mass indexer is called as:

Code:
        monitor = new IndexMonitor();

        builderService.setActive(false);
        FullTextSession ftSession = dao.getTextSession();
        ftSession.createIndexer().batchSizeToLoadObjects(10).cacheMode(CacheMode.IGNORE)
            .progressMonitor(monitor).threadsToLoadObjects(5).batchSizeToLoadObjects(20)
            .threadsForSubsequentFetching(20).threadsForIndexWriter(3).startAndWait();
        builderService.setActive(true);


Thanks for any help in figuring this out.


Top
 Profile  
 
 Post subject: Re: Unexpected output from mass indexer
PostPosted: Wed Mar 27, 2013 8:15 am 
Hibernate Team
Hibernate Team

Joined: Fri Oct 05, 2007 4:47 pm
Posts: 2536
Location: Third rock from the Sun
Was the Hibernate configuration changed?
Looks like someone enabled query logging, and that might be slowing you down very significantly, to the point of not seeing any progress in reasonable time.

_________________
Sanne
http://in.relation.to/


Top
 Profile  
 
Display posts from previous:  Sort by  
Forum locked This topic is locked, you cannot edit posts or make further replies.  [ 2 posts ] 

All times are UTC - 5 hours [ DST ]


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum

Search for:
© Copyright 2014, Red Hat Inc. All rights reserved. JBoss and Hibernate are registered trademarks and servicemarks of Red Hat, Inc.