Well, if the documents do get indexed, then all you have to do is lengthen the timeout for your connection, what is it set at now?
But this isn't expected. The first place I'd look is whether your indexing machine is allowing the op system enough memory to manage its disk caches well. The second question I'd ask is whether you're optimizing your index each time you add documents, this isn't necessary. What are your JVM settings? What physical machine are you running on? Have you looked at any other processes that might be running on that machine (if it's a *nix machine, top can be a staring point). At a guess I'd wonder about being I/O bound, so that's the first place I'd start looking Best Erick On Tue, Sep 6, 2011 at 8:04 AM, Luis Cappa Banda <luisca...@gmail.com> wrote: > Hello, Erik. > > Thank you for answering. The performance decreases during indexing: while > replication is in process the batch machine could not recieve and process > quickly the indexing petitions and some "read timed out" exceptions appear. > Luckily I just load some hundreds of documents every day because it isn't a > batch operation itself (I just index daily the new documents recieved), but > in those minutes the batch machine seems unable to operate correctly. The > machines are in the same LAN, so I think that it's not a connection > performance problem. Is it posible that the batch machine has I/O HDD > problems while reading and writing into disk at the same time? > > Thank you very much. >
