Re: Solr Issue - Logger : UpdateLog Error Message : java.io.EOFException

2020-10-03 Thread Erick Erickson
Very strange things start to happen when GC becomes unstable. The first and 
simplest thing to do would be to bump up your heap, say to 20g (note, try to 
stay under 32G or be prepared to jump significantly higher. At 32G long 
pointers have to be used and you actually have less memory available than you 
think).

The first three warnings indicate that you have both managed-schema and 
schema.xml in your configset _and_ are using the managed schema (enabled in 
solrconfig.xml). Which also suggests you’re upgrading from a previous version. 
This is printed out in as a courtesy notification that schema.xml is no longer 
being used so you should delete it to avoid confusion. NOTE: if you want to use 
schema.xml like you have before, see the reference guide.

The fourth warning suggests that you have killed Solr without committing and 
it’s replaying the transaction log. For instance, “kill -9” or other will do 
it. If you do something like that before a commit completes, updates are 
replayed from the tlog in order to preserve data.

Which leads to your second issue. I’d guess either you’re not committing after 
your updates (and, BTW, please just let your autocommit settings handle that), 
and forcefully killing Solr (e.g. kill -9). That can happen even if you use the 
“bin/solr stop” command if it takes too long (3 minutes by default last I 
knew). A “normal” shutdown that succeeds (i.e. bin/solr stop that doesn’t print 
a message about forcefully killing Solr” will commit on shutdown BTW. Taking 
over 3 minutes may be a symptom of GC going crazy.

You should to try to figure out why you have this kind of memory spike, 
returning a zillion documents is one possible cause (i.e. rows=100 or 
something). All the docs have to be assembled in memory, so if you need to 
return lots of rows, use streaming or cursorMark.

So what I’d do:
1> bump up your heap
2> insure that you shut Solr down gracefully
3> see if any particular query triggers this memory spike and if you’re using 
an anti-pattern.

Best,
Erick

> On Oct 2, 2020, at 7:10 PM, Training By Coding  
> wrote:
> 
> Events:
>   • GC logs showing continuous Full GC events. Log report attached.
>   • Core filling failed , showing less data( Num Docs)  than expected.
>   • following warnings showing on dashboard before error.
> 
> Level Logger  Message
> WARN falseManagedIndexSchemaFactory   The schema has been upgraded to 
> managed, but the non-managed schema schema.xml is still loadable. PLEASE 
> REMOVE THIS FILE.
> WARN falseManagedIndexSchemaFactory   The schema has been upgraded to 
> managed, but the non-managed schema schema.xml is still loadable. PLEASE 
> REMOVE THIS FILE.
> WARN falseSolrResourceLoader  Solr loaded a deprecated 
> plugin/analysis class [solr.TrieDateField]. Please consult documentation how 
> to replace it accordingly.
> WARN falseManagedIndexSchemaFactory   The schema has been upgraded to 
> managed, but the non-managed schema schema.xml is still loadable. PLEASE 
> REMOVE THIS FILE.
> WARN falseUpdateLog   Starting log replay 
> tlog{file=\data\tlog\tlog.0445482 refcount=2} 
> active=false starting pos=0 inSortedOrder=false
>   • Total data in all cores around 8 GB
>   • Other Configurations:
>   • -XX:+UseG1GC
>   • -XX:+UseStringDeduplication
>   • -XX:MaxGCPauseMillis=500
>   • -Xms15g
>   • -Xmx15g
>   • -Xss256k
>   • OS Environment :
>   • Windows 10,
>   • Filling cores by calling SQL query using jtds-1.3.1 library.
>   • Solr Version 7.5
>   • Runtime: Oracle Corporation OpenJDK 64-Bit Server VM 11.0.2 
> 11.0.2+9
>   • Processors : 48
>   • System Physical Memory : 128 GB
>   • Swap Space : 256GB
>   • solr-spec7.5.0
>   • solr-impl7.5.0 b5bf70b7e32d7ddd9742cc821d471c5fabd4e3df - 
> jimczi - 2018-09-18 13:07:55
>   • lucene-spec7.5.0
>   • lucene-impl7.5.0 b5bf70b7e32d7ddd9742cc821d471c5fabd4e3df - 
> jimczi - 2018-09-18 13:01:1
> Error Message : 
> java.io.EOFException
> at 
> org.apache.solr.common.util.FastInputStream.readFully(FastInputStream.java:168)
> at org.apache.solr.common.util.JavaBinCodec.readStr(JavaBinCodec.java:863)
> at org.apache.solr.common.util.JavaBinCodec.readStr(JavaBinCodec.java:857)
> at org.apache.solr.common.util.JavaBinCodec.readObject(JavaBinCodec.java:266)
> at org.apache.solr.common.util.JavaBinCodec.readVal(JavaBinCodec.java:256)
> at 
> org.apache.solr.common.util.JavaBinCodec.readSolrInputDocument(JavaBinCodec.java:603)
> at org.apache.solr.common.util.JavaBinCodec.readObject(JavaBinCodec.java:315)
> at org.apache.solr.common.util.JavaBinCodec.readVal(JavaBinCodec.java:256)
> at org.apache.solr.common.util.JavaBinCodec.readArray(JavaBinCodec.java:747)
> at 

Re: Solr issue with Sitecore 9.0.1

2020-01-16 Thread Jan Høydahl
You have to provide a lot more information in order to get help.

Java version, solr version, solr config (env vars), much more logs than what 
you posted (something is crashing)

Jan Høydahl

> 16. jan. 2020 kl. 12:22 skrev Lakshmana Gudivada (AU) 
> :
> 
> Hi Team,
> 
> Recently I have installed Solr 6.6.2 in my local desktop along with Sitecore 
> 9.0.1. I have installed https version of Solr using nssm 2.24 and trying to 
> browse https://localhost:8983/Solr
> 
> But unfortunately the web page throws the below error and solr.log file also 
> has the same error.
> 
> Can someone please help on this below error? This needs to be fixed asap so 
> we will have our local setup up and running.
> 
> 2020-01-16 10:10:08.508 ERROR (qtp1330278544-27) [   ] 
> o.a.s.s.SolrDispatchFilter Error processing the request. CoreContainer is 
> either not initialized or shutting down.
> 2020-01-16 10:10:08.508 WARN  (qtp1330278544-27) [   ] o.e.j.s.ServletHandler
> javax.servlet.UnavailableException: Error processing the request. 
> CoreContainer is either not initialized or shutting down.
>at 
> org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:321)
>at 
> org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:305)
>at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1691)
>at 
> org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:582)
>at 
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)
>at 
> org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:548)
>at 
> org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:226)
>at 
> org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1180)
>at 
> org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:512)
>at 
> org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185)
>at 
> org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1112)
>at 
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)
>at 
> org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:213)
>at 
> org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:119)
>at 
> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134)
>at 
> org.eclipse.jetty.rewrite.handler.RewriteHandler.handle(RewriteHandler.java:335)
>at 
> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134)
>at org.eclipse.jetty.server.Server.handle(Server.java:534)
>at 
> org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:320)
>at 
> org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:251)
>at 
> org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:273)
>at 
> org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:95)
>at 
> org.eclipse.jetty.io.ssl.SslConnection.onFillable(SslConnection.java:202)
>at 
> org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:273)
>at 
> org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:95)
>at 
> org.eclipse.jetty.io.SelectChannelEndPoint$2.run(SelectChannelEndPoint.java:93)
>at 
> org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.executeProduceConsume(ExecuteProduceConsume.java:303)
>at 
> org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.produceConsume(ExecuteProduceConsume.java:148)
>at 
> org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.run(ExecuteProduceConsume.java:136)
>at 
> org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:671)
>at 
> org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:589)
>at java.lang.Thread.run(Unknown Source)
> 
> 
> Much appreciate your help in resolving this.
> 
> Thanks
> 
> Lakshmana Prasanna Kumar Gudivada
> Senior Consultant
> Digital Business
> NTT
> 
> T: +61 (3) 70253006
> M: +91 9032443591
> E: lakshmana.gudiv...@global.ntt
> hello.global.ntt
> 
> This email and all contents are subject to the following disclaimer:
> https://hello.global.ntt/en-us/email-disclaimer
> 
> 
> 
> 
> 


Re: SOLR Issue

2018-08-21 Thread Shawn Heisey

On 8/21/2018 8:05 AM, Sandesh Ingawale wrote:

We have ecommerce base web application and we used SOLR for search.

Now we want to implement SOLR authentication and SOLR ranking feature 
with our application.


We need to do this programmatically(C#), can you please suggest what 
should be approach we have?


OR If you have any code snippets please send us. SOLR authentication 
needs to done with our application.


As well as please let us know if we need to do any configuration.



There is a C# client and a .NET client for Solr that are referenced in 
the documentation.  These are third party software, so you would need to 
discuss usage with those projects, not this one.


https://lucene.apache.org/solr/guide/7_4/client-api-lineup.html

I tried as per below link but after change in jetty.xml and restart 
the SOLR, it gives error.


https://support.ptc.com/help/windchill/wc111_hc/whc_en/index.html#page/Windchill_Help_Center/WCInstall_WCIndexSearchConfigStandalone_BasicAuthStandalone.html 





Those instructions are for a version of Solr that was not produced by 
the Solr project.  If you're using a version packaged by someone else, 
you'll need to talk to whoever did that packaging.  We have no idea how 
they might have changed things.


Here are the official instructions for enabling basic authentication in 
Solr:


https://lucene.apache.org/solr/guide/7_4/authentication-and-authorization-plugins.html

Thanks,
Shawn



Re: Solr Issue after the DSE upgrade

2018-06-18 Thread Charlie Hull

On 17/06/2018 03:10, Umadevi Nalluri wrote:

I am getting Connection refused (Connection refused) when I am runnind 
reload_core with dsetool after we setup jmx , this issue is happening since the 
dse upgrade to 5.0.12 , can some one please help with this issue is this a bug?
Is there a work around for this?


dsetool appears to be a utility from Datastax - have you tried asking 
them for support?


Charlie


Thanks
Kantheti




--
Charlie Hull
Flax - Open Source Enterprise Search

tel/fax: +44 (0)8700 118334
mobile:  +44 (0)7767 825828
web: www.flax.co.uk


Re: SOLR ISSUE

2018-05-16 Thread Shawn Heisey
On 5/16/2018 9:27 AM, Shah, Rimple (LNG-RDU) wrote:
> https://lucene.apache.org/solr/guide/7_2/aws-solrcloud-tutorial.html
> I am trying to follow these instructions for running SOLR on EC2. Somehow I 
> am getting this error each and every time when I try to access the dashboard. 
> Is anyone able to help in this?
>
> HTTP ERROR 404
> Problem accessing /solr/. Reason:
>
> Not Found
> Caused by:
> javax.servlet.UnavailableException: Error processing the request. 
> CoreContainer is either not initialized or shutting down.

That message is the clue.  To figure out why there's a problem with
CoreContainer, you're going to need to find and examine the solr.log file.

If looking at the logfile doesn't give you any information you can
understand, you'll probably need to share any ERROR or WARN logs in the
file with us so we can pursue it further.  Note that these messages are
frequently quite long, and we will need all of it, not just the first
line or two.  Some of the information can't be properly interpreted
without the Solr version, so include that too.

Having access to the entire logfile would give us the best chance at
determining what's wrong.  Because the mailing list tends to eat all
email attachments, you'll need to use a file sharing website or a paste
website and provide a URL for us to access the file.

If I had to guess what might be wrong, reading the instructions you're
following, I am betting that there is no file named solr.xml in the
defined solr home, and there is no solr.xml in zookeeper either.  You
might be able to get this working by copying solr.xml from the
server/solr directory in the installation location to the defined solr
home.  Alternately, you could copy the file to zookeeper:

https://lucene.apache.org/solr/guide/7_2/using-zookeeper-to-manage-configuration-files.html#preparing-zookeeper-before-first-cluster-start

Thanks,
Shawn



Re: Solr Issue

2018-01-05 Thread Erick Erickson
Ok, I missed that you had multiple records.

Pagination does not mesh well with streaming, they address quite different
use cases. You might have to re-think your indexing scheme to somehow make
the selection more amenable to standard Solr queries. Perhaps something
with the join query parser or indexing parent/child docs.

Best,
Erick

On Fri, Jan 5, 2018 at 11:57 AM, Lewin Joy (TMNA) <lewin@toyota.com>
wrote:

> Hi Erick,
>
> I just didn't know how to handle the logic without using streaming query.
> What I want is to apply the logic without streaming expressions.
>
> I want to eliminate "item_name"s in the result set which has any of it's
> record's status='N'
>
> Example:
> Id:1, Item Name: A , status: Y
> Id:2, Item Name: A,  status: Y
> Id:3, Item Name: B,  status: Y
> Id:4, Item Name: B,  status: N
> Id:5, Item Name: B,  status: Y
>
> For this data, If I apply fq=status:Y -status:N, I would still get Ids:
> 1,2,3, and 5.
> I would like to eliminate B completely as it has one record with status:N
>
> Is this possible to do in Solr without using streaming expressions?
>
> -Lewin
>
> -Original Message-
> From: Erick Erickson [mailto:erickerick...@gmail.com]
> Sent: Tuesday, January 02, 2018 6:34 PM
> To: solr-user <solr-user@lucene.apache.org>
> Subject: Re: Solr Issue
>
> wait, what is it you want to do? Streaming is built expressly to handle
> very large result sets. It is _not_ really designed to deliver pages at a
> time. Why do you want to use it at all?
>
> Why not just use straight Solr, perhaps with cursorMark if you want to
> page deeply. The query is something like:
> q=status:‘N’ -status: ‘Y’
> or
> q=status:‘N’:-status: ‘Y’
>
> Best,
> Erick
>
> On Tue, Jan 2, 2018 at 1:35 PM, Lewin Joy (TMNA) <lewin@toyota.com>
> wrote:
> > ** PROTECTED 関係者外秘
> > Hi,
> >
> > I am using Solr 6.1 and am facing an issue with a complex scenario.
> > Could you help figure out how this can be achieved in Solr?
> >
> > We have items:  A, B, C . There will be multiple record entries for each
> items.
> > For our understanding, let’s say the fields for these records are:
> primary_key,item_name,status.
> >
> > I need to retrieve all records with status= ‘N’ and filter out items
> which has any of it’s record matching status: ‘Y’
> >
> > For record set below, the query should only return me records 1 and 2.
> > Primary_key
> >
> > Item_Name
> >
> > status
> >
> > 1
> >
> > A
> >
> > N
> >
> > 2
> >
> > A
> >
> > N
> >
> > 3
> >
> > B
> >
> > N
> >
> > 4
> >
> > B
> >
> > Y
> >
> > 5
> >
> > B
> >
> > N
> >
> > 6
> >
> > C
> >
> > Y
> >
> > 7
> >
> > C
> >
> > N
> >
> >
> >
> > Currently, I am using Streaming Query expressions to do complement()
> operation.
> > But the number of records with status= ‘Y’ is too huge and causes
> performance Problems.
> > And secondly, streaming query exports with Joins and complements can’t
> be used properly for bringing out paginated outputs.
> >
> > Is there anyway, we can group the results and do a query on the group to
> filter out such records?
> > Or any other approach which could give my results paginated?
> >
> > Thanks,
> > Lewin
>


RE: Solr Issue

2018-01-05 Thread Lewin Joy (TMNA)
Hi Erick,

I just didn't know how to handle the logic without using streaming query.
What I want is to apply the logic without streaming expressions.

I want to eliminate "item_name"s in the result set which has any of it's 
record's status='N'

Example:
Id:1, Item Name: A , status: Y
Id:2, Item Name: A,  status: Y
Id:3, Item Name: B,  status: Y
Id:4, Item Name: B,  status: N
Id:5, Item Name: B,  status: Y

For this data, If I apply fq=status:Y -status:N, I would still get Ids: 1,2,3, 
and 5.
I would like to eliminate B completely as it has one record with status:N

Is this possible to do in Solr without using streaming expressions?

-Lewin

-Original Message-
From: Erick Erickson [mailto:erickerick...@gmail.com] 
Sent: Tuesday, January 02, 2018 6:34 PM
To: solr-user <solr-user@lucene.apache.org>
Subject: Re: Solr Issue

wait, what is it you want to do? Streaming is built expressly to handle very 
large result sets. It is _not_ really designed to deliver pages at a time. Why 
do you want to use it at all?

Why not just use straight Solr, perhaps with cursorMark if you want to page 
deeply. The query is something like:
q=status:‘N’ -status: ‘Y’
or
q=status:‘N’:-status: ‘Y’

Best,
Erick

On Tue, Jan 2, 2018 at 1:35 PM, Lewin Joy (TMNA) <lewin@toyota.com> wrote:
> ** PROTECTED 関係者外秘
> Hi,
>
> I am using Solr 6.1 and am facing an issue with a complex scenario.
> Could you help figure out how this can be achieved in Solr?
>
> We have items:  A, B, C . There will be multiple record entries for each 
> items.
> For our understanding, let’s say the fields for these records are: 
> primary_key,item_name,status.
>
> I need to retrieve all records with status= ‘N’ and filter out items which 
> has any of it’s record matching status: ‘Y’
>
> For record set below, the query should only return me records 1 and 2.
> Primary_key
>
> Item_Name
>
> status
>
> 1
>
> A
>
> N
>
> 2
>
> A
>
> N
>
> 3
>
> B
>
> N
>
> 4
>
> B
>
> Y
>
> 5
>
> B
>
> N
>
> 6
>
> C
>
> Y
>
> 7
>
> C
>
> N
>
>
>
> Currently, I am using Streaming Query expressions to do complement() 
> operation.
> But the number of records with status= ‘Y’ is too huge and causes performance 
> Problems.
> And secondly, streaming query exports with Joins and complements can’t be 
> used properly for bringing out paginated outputs.
>
> Is there anyway, we can group the results and do a query on the group to 
> filter out such records?
> Or any other approach which could give my results paginated?
>
> Thanks,
> Lewin


Re: Solr Issue

2018-01-02 Thread Rick Leir
Lewin
Is this not a job for a database like MySQL? Solr is a search engine, which can 
be used as a DB with some effort. Choose the right tool for the job . Cheers -- 
Rick

On January 2, 2018 4:35:47 PM EST, "Lewin Joy (TMNA)"  
wrote:
>** PROTECTED 関係者外秘
>Hi,
>
>I am using Solr 6.1 and am facing an issue with a complex scenario.
>Could you help figure out how this can be achieved in Solr?
>
>We have items:  A, B, C . There will be multiple record entries for
>each items.
>For our understanding, let’s say the fields for these records are:
>primary_key,item_name,status.
>
>I need to retrieve all records with status= ‘N’ and filter out items
>which has any of it’s record matching status: ‘Y’
>
>For record set below, the query should only return me records 1 and 2.
>Primary_key
>
>Item_Name
>
>status
>
>1
>
>A
>
>N
>
>2
>
>A
>
>N
>
>3
>
>B
>
>N
>
>4
>
>B
>
>Y
>
>5
>
>B
>
>N
>
>6
>
>C
>
>Y
>
>7
>
>C
>
>N
>
>
>
>Currently, I am using Streaming Query expressions to do complement()
>operation.
>But the number of records with status= ‘Y’ is too huge and causes
>performance Problems.
>And secondly, streaming query exports with Joins and complements can’t
>be used properly for bringing out paginated outputs.
>
>Is there anyway, we can group the results and do a query on the group
>to filter out such records?
>Or any other approach which could give my results paginated?
>
>Thanks,
>Lewin

-- 
Sorry for being brief. Alternate email is rickleir at yahoo dot com 

Re: Solr Issue

2018-01-02 Thread Erick Erickson
wait, what is it you want to do? Streaming is built expressly to
handle very large result sets. It is _not_ really designed to deliver
pages at a time. Why do you want to use it at all?

Why not just use straight Solr, perhaps with cursorMark if you want to
page deeply. The query is something like:
q=status:‘N’ -status: ‘Y’
or
q=status:‘N’:-status: ‘Y’

Best,
Erick

On Tue, Jan 2, 2018 at 1:35 PM, Lewin Joy (TMNA)  wrote:
> ** PROTECTED 関係者外秘
> Hi,
>
> I am using Solr 6.1 and am facing an issue with a complex scenario.
> Could you help figure out how this can be achieved in Solr?
>
> We have items:  A, B, C . There will be multiple record entries for each 
> items.
> For our understanding, let’s say the fields for these records are: 
> primary_key,item_name,status.
>
> I need to retrieve all records with status= ‘N’ and filter out items which 
> has any of it’s record matching status: ‘Y’
>
> For record set below, the query should only return me records 1 and 2.
> Primary_key
>
> Item_Name
>
> status
>
> 1
>
> A
>
> N
>
> 2
>
> A
>
> N
>
> 3
>
> B
>
> N
>
> 4
>
> B
>
> Y
>
> 5
>
> B
>
> N
>
> 6
>
> C
>
> Y
>
> 7
>
> C
>
> N
>
>
>
> Currently, I am using Streaming Query expressions to do complement() 
> operation.
> But the number of records with status= ‘Y’ is too huge and causes performance 
> Problems.
> And secondly, streaming query exports with Joins and complements can’t be 
> used properly for bringing out paginated outputs.
>
> Is there anyway, we can group the results and do a query on the group to 
> filter out such records?
> Or any other approach which could give my results paginated?
>
> Thanks,
> Lewin


Re: Solr Issue

2017-09-07 Thread Michael Kuhlmann
Hi Patrick,

can you attach the query you're sending to Solr and one example result?
Or more specific, what are your hl.* parameters?

-Michael

Am 07.09.2017 um 09:36 schrieb Patrick Fallert:
>
> Hey Guys, 
> i´ve got a problem with my Solr Highlighter..
> When I search for a word, i get some results. For every result i want
> to display the highlighted text and here is my problem. Some of the
> returned documents have a highlighted text the other ones doesnt. I
> don´t know why it is but i need to fix this problem. Below is the
> configuration of my managed-schema. The configuration of the
> highlighter in solrconfig.xml is default.
> I hope someone can help me. If you need more details you can ask me
> for sure.
>
> managed-schema:
>
> 
> 
> 
> id
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
>  sortMissingLast="true" multiValued="true"/>
>  currencyConfig="currency.xml" defaultCurrency="USD" precisionStep="8"/>
>  positionIncrementGap="0" docValues="true" precisionStep="0"/>
>  positionIncrementGap="0" docValues="true" multiValued="true"
> precisionStep="0"/>
>  indexed="true" stored="false">
> 
> 
> 
> 
> 
>  indexed="true" stored="false">
> 
> 
>  encoder="integer"/>
> 
> 
>  indexed="true" stored="false">
> 
> 
>  encoder="identity"/>
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
>  positionIncrementGap="0" docValues="true" precisionStep="0"/>
>  positionIncrementGap="0" docValues="true" multiValued="true"
> precisionStep="0"/>
>  positionIncrementGap="0" docValues="true" precisionStep="0"/>
>  positionIncrementGap="0" docValues="true" multiValued="true"
> precisionStep="0"/>
>  stored="false" docValues="false" multiValued="true"/>
>  positionIncrementGap="0" docValues="true" precisionStep="0"/>
>  positionIncrementGap="0" docValues="true" multiValued="true"
> precisionStep="0"/>
>  docValues="true"/>
>  class="solr.SpatialRecursivePrefixTreeFieldType" geo="true"
> maxDistErr="0.001" distErrPct="0.025" distanceUnits="kilometers"/>
>  positionIncrementGap="0" docValues="true" precisionStep="0"/>
>  positionIncrementGap="0" docValues="true" multiValued="true"
> precisionStep="0"/>
>  positionIncrementGap="100">
> 
> 
> 
> 
> 
> 
>  multiValued="true"/>
> 
>  docValues="true" multiValued="true"/>
> 
>  docValues="true" multiValued="true"/>
>  stored="false">
> 
> 
> 
> 
> 
> 
>  multiValued="true"/>
> 
>  multiValued="true"/>
>  dimension="2"/>
> 
>  docValues="true"/>
>  docValues="true" multiValued="true"/>
>  positionIncrementGap="0" docValues="true" precisionStep="6"/>
>  positionIncrementGap="0" docValues="true" multiValued="true"
> precisionStep="6"/>
>  positionIncrementGap="0" docValues="true" precisionStep="8"/>
>  positionIncrementGap="0" docValues="true" multiValued="true"
> precisionStep="8"/>
>  positionIncrementGap="100">
> 
> 
> 
>  ignoreCase="true"/>
> 
> 
> 
> 
>  positionIncrementGap="100">
> 
> 
> 
>  ignoreCase="true"/>
> 
> 
> 
>  positionIncrementGap="100">
> 
> 
>  articles="lang/contractions_ca.txt" ignoreCase="true"/>
> 
>  ignoreCase="true"/>
> 
> 
> 
>  positionIncrementGap="100">
> 
> 
> 
> 
> 
> 
> 
>  positionIncrementGap="100">
> 
> 
> 
>  ignoreCase="true"/>
> 
> 
> 
>  positionIncrementGap="100">
> 
> 
> 
>  words="lang/stopwords_da.txt" ignoreCase="true"/>
> 
> 
> 
>  positionIncrementGap="100">
> 
> 
> 
>  words="lang/stopwords_de.txt" ignoreCase="true"/>
> 
> 
> 
> 
>  positionIncrementGap="100">
> 
> 
> 
>  ignoreCase="false"/>
> 
> 
> 
>  positionIncrementGap="100">
> 
> 
>  ignoreCase="true"/>
> 
> 
>  protected="protwords.txt"/>
> 
> 
> 
> 
>  ignoreCase="true" synonyms="synonyms.txt"/>
>  ignoreCase="true"/>
> 
> 
>  protected="protwords.txt"/>
> 
> 
> 
>  autoGeneratePhraseQueries="true" positionIncrementGap="100">
> 
> 
>  ignoreCase="true"/>
>  catenateNumbers="1" generateNumberParts="1" splitOnCaseChange="1"
> generateWordParts="1" catenateAll="0" catenateWords="1"/>
> 
>  protected="protwords.txt"/>
> 
> 
> 
> 
> 
>  ignoreCase="true" synonyms="synonyms.txt"/>
>  ignoreCase="true"/>
>  catenateNumbers="0" generateNumberParts="1" splitOnCaseChange="1"
> generateWordParts="1" catenateAll="0" catenateWords="0"/>
> 
>  protected="protwords.txt"/>
> 
> 
> 
>  autoGeneratePhraseQueries="true" positionIncrementGap="100">
> 
> 
>  ignoreCase="true" synonyms="synonyms.txt"/>
>  ignoreCase="true"/>
>  catenateNumbers="1" generateNumberParts="0" generateWordParts="0"
> catenateAll="0" catenateWords="1"/>
> 
>  protected="protwords.txt"/>
> 
> 
> 
> 
> 
> 
>  ignoreCase="true" synonyms="synonyms.txt"/>
>  ignoreCase="true"/>
>  catenateNumbers="1" generateNumberParts="0" generateWordParts="0"
> catenateAll="0" catenateWords="1"/>
> 
>  protected="protwords.txt"/>
> 
> 
> 
> 
>  positionIncrementGap="100">
> 
> 
> 
>  words="lang/stopwords_es.txt" ignoreCase="true"/>
> 
> 
> 
>  positionIncrementGap="100">
> 
> 
> 
>  ignoreCase="true"/>
> 
> 
> 
>  positionIncrementGap="100">
> 
> 
> 
> 
> 
> 
>  ignoreCase="true"/>
> 
> 
>  positionIncrementGap="100">
> 
> 
> 
>  words="lang/stopwords_fi.txt" 

Re: Solr Issue While indexing Data

2017-07-21 Thread Susheel Kumar
By the way you shouldn't be running solr as root.

On Fri, Jul 21, 2017 at 12:06 AM, rajat rastogi <
rajat.rast...@hindustantimes.com> wrote:

> Hi Shawn ,
> I have Two instances of solr running and my indexing process is in java as
> well .
> PID 15958 is my indexing process.
> PID 4499 is my Solr instance which has Stuck Commits
> PID 9299 is another solr instance which is forking fine
>
> regards
>
> Rajat
>
> On 20-Jul-2017, at 16:40, Shawn Heisey-2 [via Lucene] <
> ml+s472066n4346953...@n3.nabble.com s472066n4346953...@n3.nabble.com>> wrote:
>
> On 7/20/2017 12:29 AM, rajat rastogi wrote:
> > I shared The code base, config , schema with you . Were they of any help
> , or can You point what I am doing wrong in them .
>
> I did not see any schema or config.
>
> The top output shows that you have three large Java processes, all
> running as root.  Which of these is Solr?  Are they all instances of Solr?
>
> Thanks,
> Shawn
>
>
>
> 
> If you reply to this email, your message will be added to the discussion
> below:
> http://lucene.472066.n3.nabble.com/Solr-Issue-While-indexing-Data-
> tp4339417p4346953.html
> To unsubscribe from Solr Issue While indexing Data, click here<
> http://lucene.472066.n3.nabble.com/template/NamlServlet.jtp?macro=
> unsubscribe_by_code=4339417=cmFqYXQucmFzdG9naUBoaW5kdXN0YW
> 50aW1lcy5jb218NDMzOTQxN3wtMTQwMjc3NDE5Mg==>.
> NAML NamlServlet.jtp?macro=macro_viewer=instant_html%
> 21nabble%3Aemail.naml=nabble.naml.namespaces.
> BasicNamespace-nabble.view.web.template.NabbleNamespace-
> nabble.view.web.template.NodeNamespace=
> notify_subscribers%21nabble%3Aemail.naml-instant_emails%
> 21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>
> IMPORTANT NOTICE: "This email is confidential containing HT Media
> confidential information, may be legally privileged, and is for the
> intended recipient only. Access, disclosure, copying, distribution, or
> reliance on any of it by anyone else is prohibited and may be a criminal
> offense. Please delete if obtained in error and email confirmation to the
> sender." Experience news. Like never before. Only on
> www.hindustantimes.com
>
>
>
>
> --
> View this message in context: http://lucene.472066.n3.
> nabble.com/Solr-Issue-While-indexing-Data-tp4339417p4347094.html
> Sent from the Solr - User mailing list archive at Nabble.com.
>


Re: Solr Issue While indexing Data

2017-07-20 Thread rajat rastogi
Hi Shawn ,
I have Two instances of solr running and my indexing process is in java as well 
.
PID 15958 is my indexing process.
PID 4499 is my Solr instance which has Stuck Commits
PID 9299 is another solr instance which is forking fine

regards

Rajat

On 20-Jul-2017, at 16:40, Shawn Heisey-2 [via Lucene] 
>
 wrote:

On 7/20/2017 12:29 AM, rajat rastogi wrote:
> I shared The code base, config , schema with you . Were they of any help , or 
> can You point what I am doing wrong in them .

I did not see any schema or config.

The top output shows that you have three large Java processes, all
running as root.  Which of these is Solr?  Are they all instances of Solr?

Thanks,
Shawn




If you reply to this email, your message will be added to the discussion below:
http://lucene.472066.n3.nabble.com/Solr-Issue-While-indexing-Data-tp4339417p4346953.html
To unsubscribe from Solr Issue While indexing Data, click 
here.
NAML

IMPORTANT NOTICE: "This email is confidential containing HT Media confidential 
information, may be legally privileged, and is for the intended recipient only. 
Access, disclosure, copying, distribution, or reliance on any of it by anyone 
else is prohibited and may be a criminal offense. Please delete if obtained in 
error and email confirmation to the sender." Experience news. Like never 
before. Only on www.hindustantimes.com




--
View this message in context: 
http://lucene.472066.n3.nabble.com/Solr-Issue-While-indexing-Data-tp4339417p4347094.html
Sent from the Solr - User mailing list archive at Nabble.com.

Re: Solr Issue While indexing Data

2017-07-20 Thread rajat rastogi
Hi Shawn ,

I mailed you the info @ apa...@elyograg.org
I can resend it the mail.

regards

Rajat



On 20-Jul-2017, at 16:40, Shawn Heisey-2 [via Lucene] 
>
 wrote:

On 7/20/2017 12:29 AM, rajat rastogi wrote:
> I shared The code base, config , schema with you . Were they of any help , or 
> can You point what I am doing wrong in them .

I did not see any schema or config.

The top output shows that you have three large Java processes, all
running as root.  Which of these is Solr?  Are they all instances of Solr?

Thanks,
Shawn




If you reply to this email, your message will be added to the discussion below:
http://lucene.472066.n3.nabble.com/Solr-Issue-While-indexing-Data-tp4339417p4346953.html
To unsubscribe from Solr Issue While indexing Data, click 
here.
NAML

IMPORTANT NOTICE: "This email is confidential containing HT Media confidential 
information, may be legally privileged, and is for the intended recipient only. 
Access, disclosure, copying, distribution, or reliance on any of it by anyone 
else is prohibited and may be a criminal offense. Please delete if obtained in 
error and email confirmation to the sender." Experience news. Like never 
before. Only on www.hindustantimes.com




--
View this message in context: 
http://lucene.472066.n3.nabble.com/Solr-Issue-While-indexing-Data-tp4339417p4346956.html
Sent from the Solr - User mailing list archive at Nabble.com.

Re: Solr Issue While indexing Data

2017-07-20 Thread Shawn Heisey
On 7/20/2017 12:29 AM, rajat rastogi wrote:
> I shared The code base, config , schema with you . Were they of any help , or 
> can You point what I am doing wrong in them .

I did not see any schema or config.

The top output shows that you have three large Java processes, all
running as root.  Which of these is Solr?  Are they all instances of Solr?

Thanks,
Shawn



Re: Solr Issue While indexing Data

2017-07-20 Thread rajat rastogi
Hi Shawn ,

I shared The code base, config , schema with you . Were they of any help , or 
can You point what I am doing wrong in them .

regards

Rajat

On 19-Jul-2017, at 21:41, Shawn Heisey-2 [via Lucene] 
>
 wrote:

On 6/7/2017 5:10 AM, [hidden 
email] wrote:
> My enviorment
>
> os :Ubuntu 14.04.1 LTS
> java : Orcale hotspot 1.8.0_121
> solr version :6.4.2
> cpu :16 cores
> ram :124 gb

Everybody seems to want different information from you.  Here's my
contribution:

On the linux commandline, run the "top" utility (not htop, or anything
else, actually type "top").  Press shift-M to sort the list by memory
usage, then grab a screenshot or a photo of that display.  Share the
image with us in some way.  Typically a file-sharing website is the best
option.

That will provide a wealth of information that can be useful for
narrowing down performance issues.

Thanks,
Shawn




If you reply to this email, your message will be added to the discussion below:
http://lucene.472066.n3.nabble.com/Solr-Issue-While-indexing-Data-tp4339417p4346826.html
To unsubscribe from Solr Issue While indexing Data, click 
here.
NAML

IMPORTANT NOTICE: "This email is confidential containing HT Media confidential 
information, may be legally privileged, and is for the intended recipient only. 
Access, disclosure, copying, distribution, or reliance on any of it by anyone 
else is prohibited and may be a criminal offense. Please delete if obtained in 
error and email confirmation to the sender." Experience news. Like never 
before. Only on www.hindustantimes.com




--
View this message in context: 
http://lucene.472066.n3.nabble.com/Solr-Issue-While-indexing-Data-tp4339417p4346931.html
Sent from the Solr - User mailing list archive at Nabble.com.

Re: Solr Issue While indexing Data

2017-07-19 Thread rajat rastogi
hi Shawn ,

Top out put is as follows


 

regards

Rajat



--
View this message in context: 
http://lucene.472066.n3.nabble.com/Solr-Issue-While-indexing-Data-tp4339417p4346917.html
Sent from the Solr - User mailing list archive at Nabble.com.


Re: Solr Issue While indexing Data

2017-07-19 Thread Shawn Heisey
On 6/7/2017 5:10 AM, rajat.rast...@hindustantimes.com wrote:
> My enviorment 
>
> os :Ubuntu 14.04.1 LTS
> java : Orcale hotspot 1.8.0_121
> solr version :6.4.2
> cpu :16 cores
> ram :124 gb

Everybody seems to want different information from you.  Here's my
contribution:

On the linux commandline, run the "top" utility (not htop, or anything
else, actually type "top").  Press shift-M to sort the list by memory
usage, then grab a screenshot or a photo of that display.  Share the
image with us in some way.  Typically a file-sharing website is the best
option.

That will provide a wealth of information that can be useful for
narrowing down performance issues.

Thanks,
Shawn



Re: Solr Issue While indexing Data

2017-07-19 Thread Susheel Kumar
What is you current
a) softcommit and hardcommit settings. you can share as it is from config
and how are you committing then?
b) how much is heap out of 124gb
c) how many documents are you adding that is taking long and approx how
many fields including copy fields?

Thnx

On Wed, Jul 19, 2017 at 7:32 AM, rajat rastogi <
rajat.rast...@hindustantimes.com> wrote:

> Hi Erik,
>
> Some Logs of solr
>
>
> 2017-07-19 08:14:09.104 INFO  (qtp434091818-6937) [   x:cda]
> o.a.s.u.p.LogUpdateProcessorFactory [cda]  webapp=/solr path=/update
> params={wt=javabin=2}{add=[54945918f81f4e218b994b75]} 0 24362730
> 2017-07-19 08:14:09.181 DEBUG (qtp434091818-10997) [   x:cda6m]
> o.a.s.u.p.LogUpdateProcessorFactory PRE_UPDATE
> add{,id=54945918f81f4e218b994b75} {wt=javabin=2=text}
> 2017-07-19 08:25:06.333 DEBUG (qtp434091818-7165) [   x:cda]
> o.a.s.u.p.LogUpdateProcessorFactory PRE_UPDATE FINISH
> {df=text=edismax=javabin=2}
> 2017-07-19 08:25:06.334 INFO  (qtp434091818-7165) [   x:cda]
> o.a.s.u.p.LogUpdateProcessorFactory [cda]  webapp=/solr path=/update
> params={wt=javabin=2}{add=[541011730e39384b04ba64ed]} 0 24005213
> 2017-07-19 08:25:06.454 DEBUG (qtp434091818-10958) [   x:cda6m]
> o.a.s.u.p.LogUpdateProcessorFactory PRE_UPDATE
> add{,id=541011730e39384b04ba64ed} {wt=javabin=2=text}
> 2017-07-19 09:14:57.321 DEBUG (qtp434091818-10682) [   x:cda]
> o.a.s.u.p.LogUpdateProcessorFactory PRE_UPDATE FINISH
> {df=text=edismax=javabin=2}
> 2017-07-19 09:14:57.321 INFO  (qtp434091818-10682) [   x:cda]
> o.a.s.u.p.LogUpdateProcessorFactory [cda]  webapp=/solr path=/update
> params={wt=javabin=2}{add=[54c92064a9b16e2fafeff7a0]} 0 8594125
> 2017-07-19 09:14:57.373 DEBUG (qtp434091818-12118) [   x:cda6m]
> o.a.s.u.p.LogUpdateProcessorFactory PRE_UPDATE
> add{,id=54c92064a9b16e2fafeff7a0} {wt=javabin=2=text}
> 2017-07-19 09:23:26.477 DEBUG (qtp434091818-10770) [   x:cda6m]
> o.a.s.u.p.LogUpdateProcessorFactory PRE_UPDATE FINISH
> {wt=javabin=2=text}
> 2017-07-19 09:23:26.477 INFO  (qtp434091818-10770) [   x:cda6m]
> o.a.s.u.p.LogUpdateProcessorFactory [cda6m]  webapp=/solr path=/update
> params={wt=javabin=2}{add=[520f8aaf53941a4044cdbe86]} 0 8555637
> 2017-07-19 10:17:29.822 DEBUG (qtp434091818-9274) [   x:cda]
> o.a.s.u.p.LogUpdateProcessorFactory PRE_UPDATE FINISH
> {df=text=edismax=javabin=2}
> 2017-07-19 10:17:29.822 INFO  (qtp434091818-9274) [   x:cda]
> o.a.s.u.p.LogUpdateProcessorFactory [cda]  webapp=/solr path=/update
> params={wt=javabin=2}{add=[559623155ffdf728657573ef]} 0 19477949
> 2017-07-19 10:17:29.896 DEBUG (qtp434091818-13046) [   x:cda6m]
> o.a.s.u.p.LogUpdateProcessorFactory PRE_UPDATE
> add{,id=559623155ffdf728657573ef} {wt=javabin=2=text}
> 2017-07-19 10:18:47.465 INFO  (qtp434091818-7737) [   x:cda]
> o.a.s.u.DirectUpdateHandler2 end_commit_flush
> 2017-07-19 10:18:47.465 INFO  (qtp434091818-10998) [   x:cda]
> o.a.s.u.DirectUpdateHandler2 start
> commit{,optimize=false,openSearcher=true,waitSearcher=true,
> expungeDeletes=false,softCommit=false,prepareCommit=false}
> 2017-07-19 10:18:47.465 INFO  (qtp434091818-10998) [   x:cda]
> o.a.s.u.SolrIndexWriter Calling setCommitData with
> IW:org.apache.solr.update.SolrIndexWriter@4843d921
> 2017-07-19 10:18:47.469 DEBUG (qtp434091818-7737) [   x:cda]
> o.a.s.u.p.LogUpdateProcessorFactory PRE_UPDATE FINISH
> {commit=true=text=edismax}
> 2017-07-19 10:18:47.469 INFO  (qtp434091818-7737) [   x:cda]
> o.a.s.u.p.LogUpdateProcessorFactory [cda]  webapp=/solr path=/update
> params={commit=true}{commit=} 0 28038519
> 2017-07-19 10:18:48.620 INFO  (qtp434091818-10998) [   x:cda]
> o.a.s.u.DirectUpdateHandler2 end_commit_flush
> 2017-07-19 10:18:48.728 DEBUG (qtp434091818-10998) [   x:cda]
> o.a.s.u.p.LogUpdateProcessorFactory PRE_UPDATE FINISH
> {df=text=edismax=true=true&
> softCommit=false=javabin=2}
> 2017-07-19 10:18:48.728 INFO  (qtp434091818-10998) [   x:cda]
> o.a.s.u.p.LogUpdateProcessorFactory [cda]  webapp=/solr path=/update
> params={waitSearcher=true=true=false&
> wt=javabin=2}{commit=}
> 0 10735236
> 2017-07-19 10:18:48.731 DEBUG (qtp434091818-13082) [   x:cda6m]
> o.a.s.u.p.LogUpdateProcessorFactory PRE_UPDATE
> commit{,optimize=false,openSearcher=true,waitSearcher=true,
> expungeDeletes=false,softCommit=false,prepareCommit=false}
> {commit=true=false=text=true=
> javabin=2}
> root@shineRecSolrMast:~/solr-6.4.2/server/logs# tail -f solr.log
> 2017-07-19 10:17:29.896 DEBUG (qtp434091818-13046) [   x:cda6m]
> o.a.s.u.p.LogUpdateProcessorFactory PRE_UPDATE
> add{,id=559623155ffdf728657573ef} {wt=javabin=2=text}
> 2017-07-19 10:18:47.465 INFO  (qtp434091818-7737) [   x:cda]
> o.a.s.u.DirectUpdateHandler2 end_commit_flush
> 2017-07-19 10:18:47.465 INFO  (qtp434091818-10998) [   x:cda]
> o.a.s.u.DirectUpdateHandler2 start
> commit{,optimize=false,openSearcher=true,waitSearcher=true,
> expungeDeletes=false,softCommit=false,prepareCommit=false}
> 2017-07-19 10:18:47.465 INFO  (qtp434091818-10998) [   x:cda]
> o.a.s.u.SolrIndexWriter Calling setCommitData with
> 

Re: Solr Issue While indexing Data

2017-07-19 Thread rajat rastogi
Hi Erik,

Some Logs of solr 


2017-07-19 08:14:09.104 INFO  (qtp434091818-6937) [   x:cda]
o.a.s.u.p.LogUpdateProcessorFactory [cda]  webapp=/solr path=/update
params={wt=javabin=2}{add=[54945918f81f4e218b994b75]} 0 24362730
2017-07-19 08:14:09.181 DEBUG (qtp434091818-10997) [   x:cda6m]
o.a.s.u.p.LogUpdateProcessorFactory PRE_UPDATE
add{,id=54945918f81f4e218b994b75} {wt=javabin=2=text}
2017-07-19 08:25:06.333 DEBUG (qtp434091818-7165) [   x:cda]
o.a.s.u.p.LogUpdateProcessorFactory PRE_UPDATE FINISH
{df=text=edismax=javabin=2}
2017-07-19 08:25:06.334 INFO  (qtp434091818-7165) [   x:cda]
o.a.s.u.p.LogUpdateProcessorFactory [cda]  webapp=/solr path=/update
params={wt=javabin=2}{add=[541011730e39384b04ba64ed]} 0 24005213
2017-07-19 08:25:06.454 DEBUG (qtp434091818-10958) [   x:cda6m]
o.a.s.u.p.LogUpdateProcessorFactory PRE_UPDATE
add{,id=541011730e39384b04ba64ed} {wt=javabin=2=text}
2017-07-19 09:14:57.321 DEBUG (qtp434091818-10682) [   x:cda]
o.a.s.u.p.LogUpdateProcessorFactory PRE_UPDATE FINISH
{df=text=edismax=javabin=2}
2017-07-19 09:14:57.321 INFO  (qtp434091818-10682) [   x:cda]
o.a.s.u.p.LogUpdateProcessorFactory [cda]  webapp=/solr path=/update
params={wt=javabin=2}{add=[54c92064a9b16e2fafeff7a0]} 0 8594125
2017-07-19 09:14:57.373 DEBUG (qtp434091818-12118) [   x:cda6m]
o.a.s.u.p.LogUpdateProcessorFactory PRE_UPDATE
add{,id=54c92064a9b16e2fafeff7a0} {wt=javabin=2=text}
2017-07-19 09:23:26.477 DEBUG (qtp434091818-10770) [   x:cda6m]
o.a.s.u.p.LogUpdateProcessorFactory PRE_UPDATE FINISH
{wt=javabin=2=text}
2017-07-19 09:23:26.477 INFO  (qtp434091818-10770) [   x:cda6m]
o.a.s.u.p.LogUpdateProcessorFactory [cda6m]  webapp=/solr path=/update
params={wt=javabin=2}{add=[520f8aaf53941a4044cdbe86]} 0 8555637
2017-07-19 10:17:29.822 DEBUG (qtp434091818-9274) [   x:cda]
o.a.s.u.p.LogUpdateProcessorFactory PRE_UPDATE FINISH
{df=text=edismax=javabin=2}
2017-07-19 10:17:29.822 INFO  (qtp434091818-9274) [   x:cda]
o.a.s.u.p.LogUpdateProcessorFactory [cda]  webapp=/solr path=/update
params={wt=javabin=2}{add=[559623155ffdf728657573ef]} 0 19477949
2017-07-19 10:17:29.896 DEBUG (qtp434091818-13046) [   x:cda6m]
o.a.s.u.p.LogUpdateProcessorFactory PRE_UPDATE
add{,id=559623155ffdf728657573ef} {wt=javabin=2=text}
2017-07-19 10:18:47.465 INFO  (qtp434091818-7737) [   x:cda]
o.a.s.u.DirectUpdateHandler2 end_commit_flush
2017-07-19 10:18:47.465 INFO  (qtp434091818-10998) [   x:cda]
o.a.s.u.DirectUpdateHandler2 start
commit{,optimize=false,openSearcher=true,waitSearcher=true,expungeDeletes=false,softCommit=false,prepareCommit=false}
2017-07-19 10:18:47.465 INFO  (qtp434091818-10998) [   x:cda]
o.a.s.u.SolrIndexWriter Calling setCommitData with
IW:org.apache.solr.update.SolrIndexWriter@4843d921
2017-07-19 10:18:47.469 DEBUG (qtp434091818-7737) [   x:cda]
o.a.s.u.p.LogUpdateProcessorFactory PRE_UPDATE FINISH
{commit=true=text=edismax}
2017-07-19 10:18:47.469 INFO  (qtp434091818-7737) [   x:cda]
o.a.s.u.p.LogUpdateProcessorFactory [cda]  webapp=/solr path=/update
params={commit=true}{commit=} 0 28038519
2017-07-19 10:18:48.620 INFO  (qtp434091818-10998) [   x:cda]
o.a.s.u.DirectUpdateHandler2 end_commit_flush
2017-07-19 10:18:48.728 DEBUG (qtp434091818-10998) [   x:cda]
o.a.s.u.p.LogUpdateProcessorFactory PRE_UPDATE FINISH
{df=text=edismax=true=true=false=javabin=2}
2017-07-19 10:18:48.728 INFO  (qtp434091818-10998) [   x:cda]
o.a.s.u.p.LogUpdateProcessorFactory [cda]  webapp=/solr path=/update
params={waitSearcher=true=true=false=javabin=2}{commit=}
0 10735236
2017-07-19 10:18:48.731 DEBUG (qtp434091818-13082) [   x:cda6m]
o.a.s.u.p.LogUpdateProcessorFactory PRE_UPDATE
commit{,optimize=false,openSearcher=true,waitSearcher=true,expungeDeletes=false,softCommit=false,prepareCommit=false}
{commit=true=false=text=true=javabin=2}
root@shineRecSolrMast:~/solr-6.4.2/server/logs# tail -f solr.log
2017-07-19 10:17:29.896 DEBUG (qtp434091818-13046) [   x:cda6m]
o.a.s.u.p.LogUpdateProcessorFactory PRE_UPDATE
add{,id=559623155ffdf728657573ef} {wt=javabin=2=text}
2017-07-19 10:18:47.465 INFO  (qtp434091818-7737) [   x:cda]
o.a.s.u.DirectUpdateHandler2 end_commit_flush
2017-07-19 10:18:47.465 INFO  (qtp434091818-10998) [   x:cda]
o.a.s.u.DirectUpdateHandler2 start
commit{,optimize=false,openSearcher=true,waitSearcher=true,expungeDeletes=false,softCommit=false,prepareCommit=false}
2017-07-19 10:18:47.465 INFO  (qtp434091818-10998) [   x:cda]
o.a.s.u.SolrIndexWriter Calling setCommitData with
IW:org.apache.solr.update.SolrIndexWriter@4843d921
2017-07-19 10:18:47.469 DEBUG (qtp434091818-7737) [   x:cda]
o.a.s.u.p.LogUpdateProcessorFactory PRE_UPDATE FINISH
{commit=true=text=edismax}
2017-07-19 10:18:47.469 INFO  (qtp434091818-7737) [   x:cda]
o.a.s.u.p.LogUpdateProcessorFactory [cda]  webapp=/solr path=/update
params={commit=true}{commit=} 0 28038519
2017-07-19 10:18:48.620 INFO  (qtp434091818-10998) [   x:cda]
o.a.s.u.DirectUpdateHandler2 end_commit_flush
2017-07-19 10:18:48.728 DEBUG (qtp434091818-10998) [   x:cda]

Re: Solr Issue While indexing Data

2017-07-19 Thread rajat rastogi
Hi Eric ,

Thanks for your Reply.

I tried the solution given , but it did not work.

Please help me to narrow down the problem.

Please let me know if any more inputs are required from my end viz schema,
configs etc.

Can this problem be related to GC ?

regards

Rajat



--
View this message in context: 
http://lucene.472066.n3.nabble.com/Solr-Issue-While-indexing-Data-tp4339417p4346745.html
Sent from the Solr - User mailing list archive at Nabble.com.


Re: Solr Issue While indexing Data

2017-06-07 Thread Erick Erickson
bq: All setting are set to default in solrconfig  with a change of auto
commit off .

Did you take your 4x solrconfig and just use it? I'd strongly recommend you
take the 6x configs and use those as a base, moving any customizations
over. Secondly, be sure you specify classic schema rather than data_driven
as the later tries to create fields on the fly and copy them all.

Best,
Erick

On Wed, Jun 7, 2017 at 4:10 AM, rajat.rast...@hindustantimes.com <
rajat.rast...@hindustantimes.com> wrote:

> Hi All,
>
>
> My enviorment
>
> os :Ubuntu 14.04.1 LTS
> java : Orcale hotspot 1.8.0_121
> solr version :6.4.2
> cpu :16 cores
> ram :124 gb
>
> Solr Running in a Master slave Architecture  . Indexing is being done on
> Master using a cron job in every 30 Minutes .
> Solr instance has 3 cores on which indexing happens simultaneously(cores
> with different views of same data).
>
> We Migrated from solr 4.2 to solr 6.4.2 .
> Indexing code is in java  which reads from multiple sources than pushes a
> javabin object.
> All setting are set to default in solrconfig  with a change of auto commit
> off .
>
> Problem :we  have been *Facing indexing issues* while indexing data
>
> Observation: Addition of documents taking too long in index . some times
> addition of a document takes hours . Commits are taking very long due to
> this.
> Two Cpu cores have a close to 100 % utilisation
>
> PFA hprof analysis and object distribution .
>
>
> regards
> Rajat
>
>
>
>
>
>
>
>
>
> IMPORTANT NOTICE: "This email is confidential containing HT Media
> confidential information, may be legally privileged, and is for the
> intended recipient only. Access, disclosure, copying, distribution, or
> reliance on any of it by anyone else is prohibited and may be a criminal
> offense. Please delete if obtained in error and email confirmation to the
> sender." Experience news. Like never before. Only on
> www.hindustantimes.com
>


Re: Solr Issue

2016-12-07 Thread Greg Harris
Hi Monti,

As pointed out there is a huge gap of no information. There are two primary
possibilities. One is that something about your resources is depleted. As
Shawn has pointed out... watch them as you start up. Two, Solr is somehow
locked or waiting on something. Since there is no information at the INFO
level you can either throw your logs into DEBUG level and pray to god you
see something relevant in the noise. Or, you can run a thread dump after
you've hit your gap in time and see what the server is doing at that
moment. My recommendation is to do the latter. I'd also wonder about that 0
cores found entry as well.

Greg



On Dec 7, 2016 3:02 AM, "Monti Chandra"  wrote:

> Hello team,
> I am working on solr version to 6.2.1. It was working so nice for the first
> 20 days and now the server is restarting very slow(15-20 min).
> Please get the hardware specs of my system below:
> Linux version 3.10.0-327.el7.x86_64 (buil...@kbuilder.dev.centos.org) (gcc
> version 4.8.3 20140911 (Red Hat 4.8.3-9) (GCC) )
> kernel-3.10.0-327.el7.x86_64
> It is working fine when i am taking solr directory to another server of
> same configuartion.
>
> As I am using 6.2.1 basically,  So i have downloaded the fresh
> solr-6.2.1(without any collection) and try to start the same but the server
> is not  able to start effectively. please get the log below:
>
> 0INFO  (main) [   ] o.e.j.u.log Logging initialized @257ms
> 131  INFO  (main) [   ] o.e.j.s.Server jetty-9.3.8.v20160314
> 146  INFO  (main) [   ] o.e.j.d.p.ScanningAppProvider Deployment monitor
> [file:///root/temp/solr-6.2.1/server/contexts/] at interval 0
> 311  INFO  (main) [   ] o.e.j.w.StandardDescriptorProcessor NO JSP Support
> for /solr, did not find org.apache.jasper.servlet.JspServlet
> 320  WARN  (main) [   ] o.e.j.s.SecurityHandler
> ServletContext@o.e.j.w.WebAppContext@5383967b{/solr,
> file:///root/temp/solr-6.2.1/server/solr-webapp/webapp/,
> STARTING}{/root/temp/solr-6.2.1/server/solr-webapp/webapp}
> has uncovered http methods for path: /
> 327  INFO  (main) [   ] o.a.s.s.SolrDispatchFilter
> SolrDispatchFilter.init(): WebAppClassLoader=1465085305@57536d79
> 340  INFO  (main) [   ] o.a.s.c.SolrResourceLoader JNDI not configured for
> solr (NoInitialContextEx)
> 340  INFO  (main) [   ] o.a.s.c.SolrResourceLoader using system property
> solr.solr.home: /root/temp/solr-6.2.1/server/solr
> 340  INFO  (main) [   ] o.a.s.c.SolrResourceLoader new SolrResourceLoader
> for directory: '/root/temp/solr-6.2.1/server/solr'
> 340  INFO  (main) [   ] o.a.s.c.SolrResourceLoader JNDI not configured for
> solr (NoInitialContextEx)
> 340  INFO  (main) [   ] o.a.s.c.SolrResourceLoader using system property
> solr.solr.home: /root/temp/solr-6.2.1/server/solr
> 345  INFO  (main) [   ] o.a.s.c.SolrXmlConfig Loading container
> configuration from /root/temp/solr-6.2.1/server/solr/solr.xml
> 402  INFO  (main) [   ] o.a.s.c.CorePropertiesLocator Config-defined core
> root directory: /root/temp/solr-6.2.1/server/solr
> 424  INFO  (main) [   ] o.a.s.c.CoreContainer New CoreContainer 1663619914
> 425  INFO  (main) [   ] o.a.s.c.CoreContainer Loading cores into
> CoreContainer [instanceDir=/root/temp/solr-6.2.1/server/solr]
> 425  WARN  (main) [   ] o.a.s.c.CoreContainer Couldn't add files from
> /root/temp/solr-6.2.1/server/solr/lib to classpath:
> /root/temp/solr-6.2.1/server/solr/lib
> 434  INFO  (main) [   ] o.a.s.h.c.HttpShardHandlerFactory created with
> socketTimeout : 60,connTimeout : 6,maxConnectionsPerHost :
> 20,maxConnections : 1,corePoolSize : 0,maximumPoolSize :
> 2147483647,maxThreadIdleTime : 5,sizeOfQueue : -1,fairnessPolicy :
> false,useRetries : false,connectionsEvictorSleepDelay :
> 5000,maxConnectionIdleTime : 4,
> 592  INFO  (main) [   ] o.a.s.u.UpdateShardHandler Creating
> UpdateShardHandler HTTP client with params:
> socketTimeout=60=6=true
> 594  INFO  (main) [   ] o.a.s.l.LogWatcher SLF4J impl is
> org.slf4j.impl.Log4jLoggerFactory
> 594  INFO  (main) [   ] o.a.s.l.LogWatcher Registering Log Listener [Log4j
> (org.slf4j.impl.Log4jLoggerFactory)]
> 596  INFO  (main) [   ] o.a.s.c.CoreContainer Security conf doesn't exist.
> Skipping setup for authorization module.
> 596  INFO  (main) [   ] o.a.s.c.CoreContainer No authentication plugin
> used.
> 127902 INFO  (main) [   ] o.a.s.c.CorePropertiesLocator Looking for core
> definitions underneath /root/temp/solr-6.2.1/server/solr
> 127906 INFO  (main) [   ] o.a.s.c.CorePropertiesLocator Found 0 core
> definitions
> 127909 INFO  (main) [   ] o.a.s.s.SolrDispatchFilter
> user.dir=/root/temp/solr-6.2.1/server
> 127909 INFO  (main) [   ] o.a.s.s.SolrDispatchFilter
> SolrDispatchFilter.init() done
> 127918 INFO  (main) [   ] o.e.j.s.h.ContextHandler Started
> o.e.j.w.WebAppContext@5383967b
> {/solr,file:///root/temp/solr-6.2.1/server/solr-webapp/
> webapp/,AVAILABLE}{/root/temp/solr-6.2.1/server/solr-webapp/webapp}
> 127926 INFO  (main) [   ] 

Re: Solr Issue

2016-12-07 Thread Erick Erickson
It's possibly you have autosuggest configured and it's rebuilding on startup.
See "buildOnStartup" here:
https://cwiki.apache.org/confluence/display/solr/Suggester

Depending on the suggester, this will re-read _all_ documents
from the index to build the internal autosuggest structures which
can take many minutes. That would also explain Shawn's observation
that there is quite a gap in the timestamps.

Although I am puzzled by a couple of things:
1> There should be a message in your log
explicitly referencing building autosuggest. I don't see it.
2> this message:
o.a.s.c.CorePropertiesLocator Found 0 core
definitions

seems to indicate that there are no replicas on the server.

Best,
Erick



On Wed, Dec 7, 2016 at 9:01 AM, Shawn Heisey  wrote:
> On 12/7/2016 3:24 AM, Monti Chandra wrote:
>> I am working on solr version to 6.2.1. It was working so nice for the first
>> 20 days and now the server is restarting very slow(15-20 min).
>> Please get the hardware specs of my system below:
>> Linux version 3.10.0-327.el7.x86_64 (buil...@kbuilder.dev.centos.org) (gcc
>> version 4.8.3 20140911 (Red Hat 4.8.3-9) (GCC) )
>> kernel-3.10.0-327.el7.x86_64
>
> These are not hardware specs.  They are software specs, and really don't
> contain anything useful.  From this, we can tell that you are running
> CentOS 7 64-bit with a 3.10 kernel, and that's pretty much it.
>
>> It is working fine when i am taking solr directory to another server of
>> same configuartion.
>>
>> As I am using 6.2.1 basically,  So i have downloaded the fresh
>> solr-6.2.1(without any collection) and try to start the same but the server
>> is not  able to start effectively. please get the log below:
> 
>> 596  INFO  (main) [   ] o.a.s.c.CoreContainer No authentication plugin used.
>> 127902 INFO  (main) [   ] o.a.s.c.CorePropertiesLocator Looking for core
>> definitions underneath /root/temp/solr-6.2.1/server/solr
>> 127906 INFO  (main) [   ] o.a.s.c.CorePropertiesLocator Found 0 core
>> definitions
>> 127909 INFO  (main) [   ] o.a.s.s.SolrDispatchFilter
>> user.dir=/root/temp/solr-6.2.1/server
>> 127909 INFO  (main) [   ] o.a.s.s.SolrDispatchFilter
>> SolrDispatchFilter.init() done
>> 127918 INFO  (main) [   ] o.e.j.s.h.ContextHandler Started
>> o.e.j.w.WebAppContext@5383967b
>> {/solr,file:///root/temp/solr-6.2.1/server/solr-webapp/webapp/,AVAILABLE}{/root/temp/solr-6.2.1/server/solr-webapp/webapp}
>> 127926 INFO  (main) [   ] o.e.j.s.ServerConnector Started
>> ServerConnector@1573f9fc{HTTP/1.1,[http/1.1]}{0.0.0.0:}
>> 127926 INFO  (main) [   ] o.e.j.s.Server Started @128185ms
>>
>>
>> Is there any H/w, OS or kernel level threat caused by running solr? Please
>> help me I am wondering for a very long time.
>
> This log shows no errors.  It says that Jetty is listening on port
> .  It does look like it took a couple of minutes for Solr to finish
> starting, but other than that, I cannot see any problems here.
>
> Troubleshooting performance issues like this requires careful
> observation, and may be very difficult to do via a mailing list.  We
> have pretty much zero information to go on, and the logs you have sent
> do not even contain any relevant warnings.
>
> There is only one odd thing.  The log jumps from 596 milliseconds to
> 127902 milliseconds -- over two minutes with absolutely no information
> logged, after which it completes startup.  When I start a
> freshly-downloaded Solr 6.2.1 in foreground mode, the time difference
> between these two log entries on my system is only 32 milliseconds, and
> then Solr is fully started less than a second later.
>
> 4271 INFO  (main) [   ] o.a.s.c.CoreContainer No authentication plugin used.
> 4303 INFO  (main) [   ] o.a.s.c.CorePropertiesLocator Looking for core
> definitions underneath C:\Users\sheisey\Downloads\solr-6.2.1\server\solr
> 4552 INFO  (main) [   ] o.a.s.c.CorePropertiesLocator Found 0 core
> definitions
> 4552 INFO  (main) [   ] o.a.s.s.SolrDispatchFilter
> user.dir=C:\Users\sheisey\Downloads\solr-6.2.1\server
> 4552 INFO  (main) [   ] o.a.s.s.SolrDispatchFilter
> SolrDispatchFilter.init() done
> 4553 INFO  (main) [   ] o.e.j.s.h.ContextHandler Started
> o.e.j.w.WebAppContext@a67c67e{/solr,file:///C:/Users/sheisey/Downloads/solr-6.2.1/server/solr-webapp/webapp/,AVAILABLE}{C:\Users\sheisey\Downloads\solr-6.2.1\server/solr-webapp/webapp}
> 4559 INFO  (main) [   ] o.e.j.s.ServerConnector Started
> ServerConnector@4c12331b{HTTP/1.1,[http/1.1]}{0.0.0.0:8983}
> 4560 INFO  (main) [   ] o.e.j.s.Server Started @5548ms
>
> Do you have any more information you can share?  Something I'd like to
> see is a screenshot of "top" running in your terminal, after starting
> the fresh Solr with no collections.  Before getting the screenshot,
> press shift-M to sort the list by memory usage.
>
> Thanks,
> Shawn
>


Re: Solr Issue

2016-12-07 Thread Shawn Heisey
On 12/7/2016 3:24 AM, Monti Chandra wrote:
> I am working on solr version to 6.2.1. It was working so nice for the first
> 20 days and now the server is restarting very slow(15-20 min).
> Please get the hardware specs of my system below:
> Linux version 3.10.0-327.el7.x86_64 (buil...@kbuilder.dev.centos.org) (gcc
> version 4.8.3 20140911 (Red Hat 4.8.3-9) (GCC) )
> kernel-3.10.0-327.el7.x86_64

These are not hardware specs.  They are software specs, and really don't
contain anything useful.  From this, we can tell that you are running
CentOS 7 64-bit with a 3.10 kernel, and that's pretty much it.

> It is working fine when i am taking solr directory to another server of
> same configuartion.
>
> As I am using 6.2.1 basically,  So i have downloaded the fresh
> solr-6.2.1(without any collection) and try to start the same but the server
> is not  able to start effectively. please get the log below:

> 596  INFO  (main) [   ] o.a.s.c.CoreContainer No authentication plugin used.
> 127902 INFO  (main) [   ] o.a.s.c.CorePropertiesLocator Looking for core
> definitions underneath /root/temp/solr-6.2.1/server/solr
> 127906 INFO  (main) [   ] o.a.s.c.CorePropertiesLocator Found 0 core
> definitions
> 127909 INFO  (main) [   ] o.a.s.s.SolrDispatchFilter
> user.dir=/root/temp/solr-6.2.1/server
> 127909 INFO  (main) [   ] o.a.s.s.SolrDispatchFilter
> SolrDispatchFilter.init() done
> 127918 INFO  (main) [   ] o.e.j.s.h.ContextHandler Started
> o.e.j.w.WebAppContext@5383967b
> {/solr,file:///root/temp/solr-6.2.1/server/solr-webapp/webapp/,AVAILABLE}{/root/temp/solr-6.2.1/server/solr-webapp/webapp}
> 127926 INFO  (main) [   ] o.e.j.s.ServerConnector Started
> ServerConnector@1573f9fc{HTTP/1.1,[http/1.1]}{0.0.0.0:}
> 127926 INFO  (main) [   ] o.e.j.s.Server Started @128185ms
>
>
> Is there any H/w, OS or kernel level threat caused by running solr? Please
> help me I am wondering for a very long time.

This log shows no errors.  It says that Jetty is listening on port
.  It does look like it took a couple of minutes for Solr to finish
starting, but other than that, I cannot see any problems here.

Troubleshooting performance issues like this requires careful
observation, and may be very difficult to do via a mailing list.  We
have pretty much zero information to go on, and the logs you have sent
do not even contain any relevant warnings.

There is only one odd thing.  The log jumps from 596 milliseconds to
127902 milliseconds -- over two minutes with absolutely no information
logged, after which it completes startup.  When I start a
freshly-downloaded Solr 6.2.1 in foreground mode, the time difference
between these two log entries on my system is only 32 milliseconds, and
then Solr is fully started less than a second later.

4271 INFO  (main) [   ] o.a.s.c.CoreContainer No authentication plugin used.
4303 INFO  (main) [   ] o.a.s.c.CorePropertiesLocator Looking for core
definitions underneath C:\Users\sheisey\Downloads\solr-6.2.1\server\solr
4552 INFO  (main) [   ] o.a.s.c.CorePropertiesLocator Found 0 core
definitions
4552 INFO  (main) [   ] o.a.s.s.SolrDispatchFilter
user.dir=C:\Users\sheisey\Downloads\solr-6.2.1\server
4552 INFO  (main) [   ] o.a.s.s.SolrDispatchFilter
SolrDispatchFilter.init() done
4553 INFO  (main) [   ] o.e.j.s.h.ContextHandler Started
o.e.j.w.WebAppContext@a67c67e{/solr,file:///C:/Users/sheisey/Downloads/solr-6.2.1/server/solr-webapp/webapp/,AVAILABLE}{C:\Users\sheisey\Downloads\solr-6.2.1\server/solr-webapp/webapp}
4559 INFO  (main) [   ] o.e.j.s.ServerConnector Started
ServerConnector@4c12331b{HTTP/1.1,[http/1.1]}{0.0.0.0:8983}
4560 INFO  (main) [   ] o.e.j.s.Server Started @5548ms

Do you have any more information you can share?  Something I'd like to
see is a screenshot of "top" running in your terminal, after starting
the fresh Solr with no collections.  Before getting the screenshot,
press shift-M to sort the list by memory usage.

Thanks,
Shawn



Re: solr issue with pdf forms

2015-04-22 Thread Dan Davis
Steve,

Are you using ExtractingRequestHandler / DataImportHandler or extracting
the text content from the PDF outside of Solr?

On Wed, Apr 22, 2015 at 6:40 AM, steve.sch...@t-systems.com wrote:

 Hi guys,

 hopefully you can help me with my issue. We are using a solr setup and
 have the following issue:
 - usual pdf files are indexed just fine
 - pdf files with writable form-fields look like this:

 Ich�bestätige�mit�meiner�Unterschrift,�dass�alle�Angaben�korrekt�und�vollständig�sind

 Somehow the blank space character is not indexed correctly.

 Is this a know issue? Does anybody have an idea?

 Thanks a lot
 Best
 Steve



RE: Solr issue

2014-09-01 Thread Shay Sofer
Hi,

None of the above fix my problem.

The problem is with QueryComponent.java:

  private void groupedFinishStage(final ResponseBuilder rb) {
// To have same response as non-distributed request.
GroupingSpecification groupSpec = rb.getGroupingSpec();
if (rb.mergedTopGroups.isEmpty()) {
  for (String field : groupSpec.getFields()) {
rb.mergedTopGroups.put(field, new TopGroups(null, null, 0, 0, new 
GroupDocs[]{}, Float.NaN));
  }
  rb.resultIds = new HashMap();
}

We are cleaning rb.resultIds, and in HighlightComponent we are trying to read 
from it and NPE is established.



-Original Message-
From: Patanachai Tangchaisin [mailto:patanachai.tangchai...@wizecommerce.com] 
Sent: Thursday, August 28, 2014 10:42 PM
To: solr-user@lucene.apache.org
Subject: Re: Solr issue

Hi Shay,

I'm not quite sure about this.
But, I think it is get fixed with this.

https://issues.apache.org/jira/browse/SOLR-6223
https://issues.apache.org/jira/browse/SOLR-4186
https://issues.apache.org/jira/browse/SOLR-4049

Could you try 4.10 from a svn branch and see if your problem is fixed?

Thanks,
Patanachai



On 08/28/2014 03:23 AM, Shay Sofer wrote:
 Hi,

 Version - 4.8.1

 While executing this solr query (from solr web UI):

 http://localhost:8983/solr/Global_A/select?q=%2Btext%3A%28shay*%29+rows=100fl=id%2CobjId%2Cnullshards=http%3A%2F%2F127.0.0.1%3A8983%2Fsolr%2F0_A%2Chttp%3A%2F%2F127.0.0.1%3A8983%2Fsolr%2FGlobal_Agroup=truegroup.query=name__s%3Ashaysort=name__s_sort+aschl=truehttp://localhost:8983/solr/cpm_Global_A/select?q=%2Btext%3A%28shay*%29+rows=100fl=id%2CobjId%2Cnullshards=http%3A%2F%2F127.0.0.1%3A8983%2Fsolr%2Fcpm_0_A%2Chttp%3A%2F%2F127.0.0.1%3A8983%2Fsolr%2Fcpm_Global_Agroup=truegroup.query=name__s%3Ashaysort=name__s_sort+aschl=true

 We got NullPointerException:

 java.lang.NullPointerException at 
 org.apache.solr.handler.component.HighlightComponent.finishStage(HighlightComponent.java:189)
  at 
 org.apache.solr.handler.component.SearchHandler.handleRequestBody(SearchHandler.java:330)
  at 
 org.apache.solr.handler.RequestHandlerBase.handleRequest(RequestHandlerBase.java:135)
  at org.apache.solr.core.SolrCore.execute(SolrCore.java:1952) at 
 org.apache.solr.servlet.SolrDispatchFilter.execute(SolrDispatchFilter.java:774)
  at 
 org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:418)
  at 
 org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:207)
  at 
 org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1419)
  at 
 org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:455) at 
 org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137) 
 at 
 org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:557) 
 at 
 org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231)
  at 
 org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1075)
  at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:384) 
 at 
 org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:193)
  at 
 org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1009)
  at 
 org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:135) 
 at 
 org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:255)
  at 
 org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:154)
  at 
 org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:116)
  at org.eclipse.jetty.server.Server.handle(Server.java:368) at 
 org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:489)
  at 
 org.eclipse.jetty.server.BlockingHttpConnection.handleRequest(BlockingHttpConnection.java:53)
  at 
 org.eclipse.jetty.server.AbstractHttpConnection.headerComplete(AbstractHttpConnection.java:942)
  at 
 org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.headerComplete(AbstractHttpConnection.java:1004)
  at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:640) at 
 org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:235) at 
 org.eclipse.jetty.server.BlockingHttpConnection.handle(BlockingHttpConnection.java:72)
  at 
 org.eclipse.jetty.server.bio.SocketConnector$ConnectorEndPoint.run(SocketConnector.java:264)
  at 
 org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:608)
  at 
 org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:543)
  at java.lang.Thread.run(Thread.java:722)

 Seems like integration of Grouping + shards + highlighting cause this 
 NullPointerException.

 Anyone familiar with this issue?

 Thanks,
 Shay.




CONFIDENTIALITY NOTICE
==
This email message and any attachments are for the exclusive use of the 
intended recipient(s) and may contain confidential and privileged

Re: Solr issue

2014-08-28 Thread Patanachai Tangchaisin

Hi Shay,

I'm not quite sure about this.
But, I think it is get fixed with this.

https://issues.apache.org/jira/browse/SOLR-6223
https://issues.apache.org/jira/browse/SOLR-4186
https://issues.apache.org/jira/browse/SOLR-4049

Could you try 4.10 from a svn branch and see if your problem is fixed?

Thanks,
Patanachai



On 08/28/2014 03:23 AM, Shay Sofer wrote:

Hi,

Version - 4.8.1

While executing this solr query (from solr web UI):

http://localhost:8983/solr/Global_A/select?q=%2Btext%3A%28shay*%29+rows=100fl=id%2CobjId%2Cnullshards=http%3A%2F%2F127.0.0.1%3A8983%2Fsolr%2F0_A%2Chttp%3A%2F%2F127.0.0.1%3A8983%2Fsolr%2FGlobal_Agroup=truegroup.query=name__s%3Ashaysort=name__s_sort+aschl=truehttp://localhost:8983/solr/cpm_Global_A/select?q=%2Btext%3A%28shay*%29+rows=100fl=id%2CobjId%2Cnullshards=http%3A%2F%2F127.0.0.1%3A8983%2Fsolr%2Fcpm_0_A%2Chttp%3A%2F%2F127.0.0.1%3A8983%2Fsolr%2Fcpm_Global_Agroup=truegroup.query=name__s%3Ashaysort=name__s_sort+aschl=true

We got NullPointerException:

java.lang.NullPointerException at 
org.apache.solr.handler.component.HighlightComponent.finishStage(HighlightComponent.java:189)
 at 
org.apache.solr.handler.component.SearchHandler.handleRequestBody(SearchHandler.java:330)
 at 
org.apache.solr.handler.RequestHandlerBase.handleRequest(RequestHandlerBase.java:135)
 at org.apache.solr.core.SolrCore.execute(SolrCore.java:1952) at 
org.apache.solr.servlet.SolrDispatchFilter.execute(SolrDispatchFilter.java:774) 
at 
org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:418)
 at 
org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:207)
 at 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1419)
 at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:455) 
at 
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137) 
at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:557) 
at 
org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231)
 at 
org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1075)
 at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:384) 
at 
org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:193)
 at 
org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1009)
 at 
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:135) 
at 
org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:255)
 at 
org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:154)
 at 
org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:116) 
at org.eclipse.jetty.server.Server.handle(Server.java:368) at 
org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:489)
 at 
org.eclipse.jetty.server.BlockingHttpConnection.handleRequest(BlockingHttpConnection.java:53)
 at 
org.eclipse.jetty.server.AbstractHttpConnection.headerComplete(AbstractHttpConnection.java:942)
 at 
org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.headerComplete(AbstractHttpConnection.java:1004)
 at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:640) at 
org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:235) at 
org.eclipse.jetty.server.BlockingHttpConnection.handle(BlockingHttpConnection.java:72)
 at 
org.eclipse.jetty.server.bio.SocketConnector$ConnectorEndPoint.run(SocketConnector.java:264)
 at 
org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:608)
 at 
org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:543) 
at java.lang.Thread.run(Thread.java:722)

Seems like integration of Grouping + shards + highlighting cause this 
NullPointerException.

Anyone familiar with this issue?

Thanks,
Shay.





CONFIDENTIALITY NOTICE
==
This email message and any attachments are for the exclusive use of the 
intended recipient(s) and may contain confidential and privileged information. 
Any unauthorized review, use, disclosure or distribution is prohibited. If you 
are not the intended recipient, please contact the sender by reply email and 
destroy all copies of the original message along with any attachments, from 
your computer system. If you are the intended recipient, please be advised that 
the content of this message is subject to access, review and disclosure by the 
sender's Email System Administrator.


Re: solr issue

2013-02-22 Thread Gora Mohanty
On 22 February 2013 12:40, Pawankumar Rote
pawankumar.r...@aressindia.net wrote:

 Hi

 One of our client has purchased SOLR extension. We have integrated it with 
 mageno community edition. We are facing below issues.

 1] On click of search box pop up appears - it is ok. But the price displayed 
 against the product name is product’s special price. We want to display the 
 price of product with inclusive of VAT.

 2] The product images are also not displayed instead placeholder image is 
 seen.
[...]

I think that you are in the wrong place. You are probably
talking about some commercial product that acts as a
bridge between Magento, and Solr, and as such you
should seek support from the organisation that the product
was purchased from.

Your questions above have nothing to do with Solr, but
probably with how that product integrates with Magento,
and indexes to Solr.

Regards,
Gora


Re: solr issue with seaching words

2012-09-14 Thread Erick Erickson
And you have SnowballPorterFilterFactory in your analysis chain which
is transforming jacke into jack.

Best
Erick

On Mon, Sep 10, 2012 at 7:15 AM, zainu zainu...@gmail.com wrote:
 http://lucene.472066.n3.nabble.com/file/n4006583/Unbenannt.png



 --
 View this message in context: 
 http://lucene.472066.n3.nabble.com/solr-issue-with-seaching-words-tp4005200p4006583.html
 Sent from the Solr - User mailing list archive at Nabble.com.


Re: solr issue with seaching words

2012-09-10 Thread zainu
Thank you very much guys for your reply and sorry for getting back to you so
late. Here is output from anylsis. Please see the attached image. I can see
, it returns me Jack as well when i type jacke.



--
View this message in context: 
http://lucene.472066.n3.nabble.com/solr-issue-with-seaching-words-tp4005200p4006580.html
Sent from the Solr - User mailing list archive at Nabble.com.


Re: solr issue with seaching words

2012-09-10 Thread zainu
http://lucene.472066.n3.nabble.com/file/n4006583/Unbenannt.png 



--
View this message in context: 
http://lucene.472066.n3.nabble.com/solr-issue-with-seaching-words-tp4005200p4006583.html
Sent from the Solr - User mailing list archive at Nabble.com.


Re: solr issue with seaching words

2012-09-06 Thread Chris Hostetter

: I am facing a strange problem. I am searching for word jacke but solr also
: returns result where my description contains 'RCA-Jack/'. Íf i search
: jacka or jackc or jackd, it works fine and does not return me any
: result which is what i am expecting in this case.

you need to tell us what the analyzers in your fieldType - if i had to 
guess, i would suspect that you are using a rules basd stemmer that 
converts jacke to jack in combination with something that splits on 
- ... which could be WordDelimiterFilter, or it could be something else.

devil is in the details


-Hoss

Re: solr issue with seaching words

2012-09-04 Thread Rafał Kuć
Hello!

I suppose, you may have word delimiter along with stemming in your
configuration. You may see how your analysis chain works in Solr
analysis pages (admin panel). You can paste the type configuration for
the field you experiencing issues on and we will be able to see what
is happening.

-- 
Regards,
 Rafał Kuć
 Sematext :: http://sematext.com/ :: Solr - Lucene - Nutch - ElasticSearch

 I am facing a strange problem. I am searching for word jacke but solr also
 returns result where my description contains 'RCA-Jack/'. Íf i search
 jacka or jackc or jackd, it works fine and does not return me any
 result which is what i am expecting in this case.

 Only when there is jacke, it return me result with RCA-Jack/. So there
 seems some kind of relationshio between e and / and it considers e as
 /. 

 Any help?



 --
 View this message in context:
 http://lucene.472066.n3.nabble.com/solr-issue-with-seaching-words-tp4005200.html
 Sent from the Solr - User mailing list archive at Nabble.com.



Re: solr issue with seaching words

2012-09-04 Thread Dikchant Sahi
Try debugging it using analysis page or running the query in debug mode
(debugQuery=true).

In analysis page, add 'RCA-Jack/' to index and 'jacke' to query. This might
help you understanding the behavior.

If still unable to debug, some additional information would be required to
help.

On Tue, Sep 4, 2012 at 3:38 PM, zainu zainu...@gmail.com wrote:

 I am facing a strange problem. I am searching for word jacke but solr
 also
 returns result where my description contains 'RCA-Jack/'. Íf i search
 jacka or jackc or jackd, it works fine and does not return me any
 result which is what i am expecting in this case.

 Only when there is jacke, it return me result with RCA-Jack/. So there
 seems some kind of relationshio between e and / and it considers e as
 /.

 Any help?



 --
 View this message in context:
 http://lucene.472066.n3.nabble.com/solr-issue-with-seaching-words-tp4005200.html
 Sent from the Solr - User mailing list archive at Nabble.com.



Re: Solr Issue : SOLR-3771

2012-08-31 Thread Lance Norskog
Java has system properties for setting proxies.

http://docs.oracle.com/javase/6/docs/technotes/guides/net/proxies.html

On Fri, Aug 31, 2012 at 3:43 AM, Nagaraj Molala nmol...@gmail.com wrote:
 Hi,

 Is there any option in the configuration to add proxy setting in the
 rss-data-config.xml file or any configuration in solr?. Basically mentioned
 rss url is able to parse with standalone java program using proxy setting.
 while trying to index with the Solr using dataImport, its giving the
 UnknownHostException exception. I am attaching the config files.

 ?xml version=1.0 encoding=UTF-8 ?
 dataConfig
 dataSource type=URLDataSource /
 document
 entity name=IndustryMonitor
 pk=link
 url=company URL comes here ..
 processor=XPathEntityProcessor
 forEach=/channel | /channel/item
 transformer=DateFormatTransformer

 field column=title xpath=/rss/channel/item/title /
 field column=author xpath=/rss/channel/item/author /
 field column=link xpath=/rss/channel/item/link /

 /entity
 /document
 /dataConfig



 Warm Regards,
 Nagaraj Molala
 Cell: +91 8447016501
 
 From: Jack Krupansky (JIRA) [j...@apache.org]
 Sent: Friday, August 31, 2012 4:28 AM
 To: Nagaraj M
 Subject: [jira] [Commented] (SOLR-3771) While using RSS indexing from Solr,
 we are getting error Caused by: java.net.UnknownHostException  indexing
 fail.

 [
 https://issues.apache.org/jira/browse/SOLR-3771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13445389#comment-13445389
 ]

 Jack Krupansky commented on SOLR-3771:
 --

 Any support questions should be directed to the Solr user mailing list:
 solr-user@lucene.apache.org

 It still doesn't sound as if there is any evidence being presented here of a
 bug in Solr.


 While using RSS indexing from Solr, we are getting error Caused by:
 java.net.UnknownHostException  indexing fail.

 

 Key: SOLR-3771
 URL: https://issues.apache.org/jira/browse/SOLR-3771
 Project: Solr
  Issue Type: Bug
  Components: search
Affects Versions: 3.6
 Environment: Solr Search engine using RSS data feeding
Reporter: Nagaraj Molala
 Attachments: rss-data-config.xml, schema.xml, solrconfig.xml


 we are getting below error. Please give us the solution as this is a show
 stopper for our application. Attached the config files for your reference.

 https://issues.apache.org/jira/browse/SOLR 2:51 PM
 Caused by: java.net.UnknownHostException: xx.abcd.abcd.com
at java.net.PlainSocketImpl.connect(Unknown Source)
at java.net.SocksSocketImpl.connect(Unknown Source)
at java.net.Socket.connect(Unknown Source)
at sun.net.NetworkClient.doConnect(Unknown Source)
at sun.net.www.http.HttpClient.openServer(Unknown Source)
at sun.net.www.http.HttpClient.openServer(Unknown Source)
at sun.net.www.http.HttpClient.init(Unknown Source)
at sun.net.www.http.HttpClient.New(Unknown Source)
at sun.net.www.http.HttpClient.New(Unknown Source)
at
 sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(Unknown
 Source)
at sun.net.www.protocol.http.HttpURLConnection.plainConnect(Unknown
 Sour
 ce)
at sun.net.www.protocol.http.HttpURLConnection.connect(Unknown
 Source)
at
 sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown So
 urce)
at
 org.apache.solr.handler.dataimport.URLDataSource.getData(URLDataSourc
 e.java:97)
... 13 more


 --
 This message is automatically generated by JIRA.
 If you think it was sent incorrectly, please contact your JIRA
 administrators
 For more information on JIRA, see: http://www.atlassian.com/software/jira



 Warm Regards,

 Nagaraj Molala

 Contractor

 GE Capital – Americas



 T :  +91 120 4675233
 M : +91 8447016501.

 E : nagaraj.mol...@ge.com



 D-195 Sector 63
 Noida, UP 201306, INDIA



 --
 With Regards,
 Nagaraj Molala.
 Mobile: 9618246257.



-- 
Lance Norskog
goks...@gmail.com


RE: SOLR issue - too many search queries

2012-04-10 Thread Darren Govoni

My first reaction to your question is why are you running thousands of queries 
in a loop? Immediately, I think this will not scale well and the design 
probably needs to be re-visited.

Second, if you need that many requests, then you need to seriously consider an 
architecture that supports it. This will require a complex design involving 
load balancers, multiple servers, replication, etc. People have achieved this 
with Solr, but it's beyond the scope of Solr itself to provide this, as its a 
matter of system architecture.

Also, there are limits to the number of app server threads allowed, OS threads 
allowed, OS sockets, OS file descriptors, etc. etc. All of which need to be 
understood, designed for and configured properly.


brbrbr--- Original Message ---
On 4/10/2012  07:51 AM arunssasidhar wrote:brWe have a PHP web application 
which is using SOLR for searching. The APP is
brusing CURL to connect to the SOLR server and which run in a loop with
brthousands of predefined keywords. That will create thousands of different
brsearch quires to SOLR at a given time.
br
brMy issue is that, when a single user logged into the app everything is
brworking as expected. When there is more than one user is trying to run the
brapp we are getting this response from the server.
br
brFailed to connect to xxx.xxx.xxx.xxx: Cannot assign requested
braddressFailed to connect to xxx.xxx.xxx.xxx: Cannot assign requested
braddressFailed
br
brOur assumption is that, SOLR server is unable to handle this much search
brqueries at a given time. If so what is the solution to overcome this?. Is
brthere any settings like keep-alive in SOLR?
br
brAny help would be highly appreciate.
br
brThanks,
br
brArun S
br
br
br--
brView this message in context: 
http://lucene.472066.n3.nabble.com/SOLR-issue-too-many-search-queries-tp3899518p3899518.html
brSent from the Solr - User mailing list archive at Nabble.com.
br
br


Re: SOLR issue - too many search queries

2012-04-10 Thread Yonik Seeley
On Tue, Apr 10, 2012 at 8:51 AM, arunssasidhar arunssasid...@gmail.com wrote:
 We have a PHP web application which is using SOLR for searching. The APP is
 using CURL to connect to the SOLR server and which run in a loop with
 thousands of predefined keywords. That will create thousands of different
 search quires to SOLR at a given time.

Thousands of concurrent queries?  That's normally not a useful metric
unless you have a very strange application.

You normally want to look at the following:
 - throughput (queries per second)
 - latency (how long the queries take - average, 90%, 95%, etc)

-Yonik
lucenerevolution.com - Lucene/Solr Open Source Search Conference.
Boston May 7-10


Re: solr issue..

2011-12-23 Thread Erick Erickson
What version of Solr?

It might help to review:
http://wiki.apache.org/solr/UsingMailingLists

Best
Erick

On Fri, Dec 23, 2011 at 4:55 AM, karan_jindal
karan_jin...@students.iiit.ac.in wrote:
 hi all,

 I am getting this error while clicking on the replication link on the
 admin page of solr..

 java.lang.ClassFormatError: Unknown constant tag 69 in class file
 org/apache/jsp/admin/replication/index_jsp javax.servlet.ServletException:
 java.lang.ClassFormatError: Unknown constant tag 69 in class file
 org/apache/jsp/admin/replication/index_jsp at
 org.apache.jasper.servlet.JspServlet.service(JspServlet.java:275) at
 javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at
 org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
 at
 org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
 at
 org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:646)
 at
 org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:436)
 at
 org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:374)
 at
 org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:302)
 at
 org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:275)
 at
 org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
 at
 org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
 at
 org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
 at
 org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
 at
 org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
 at
 org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
 at
 org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:567)
 at
 org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
 at
 org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:293)
 at
 org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:849)
 at
 org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
 at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:454)
 at java.lang.Thread.run(Thread.java:662) Caused by:
 java.lang.ClassFormatError: Unknown constant tag 69 in class file
 org/apache/jsp/admin/replication/index_jsp at
 java.lang.ClassLoader.defineClass1(Native Method) at
 java.lang.ClassLoader.defineClassCond(ClassLoader.java:631) at
 java.lang.ClassLoader.defineClass(ClassLoader.java:615) at
 java.security.SecureClassLoader.defineClass(SecureClassLoader.java:141) at
 java.net.URLClassLoader.defineClass(URLClassLoader.java:283) at
 java.net.URLClassLoader.access$000(URLClassLoader.java:58) at
 java.net.URLClassLoader$1.run(URLClassLoader.java:197) at
 java.security.AccessController.doPrivileged(Native Method) at
 java.net.URLClassLoader.findClass(URLClassLoader.java:190) at
 org.apache.jasper.servlet.JasperLoader.loadClass(JasperLoader.java:134) at
 org.apache.jasper.servlet.JasperLoader.loadClass(JasperLoader.java:66) at
 org.apache.jasper.JspCompilationContext.load(JspCompilationContext.java:618)
 at
 org.apache.jasper.servlet.JspServletWrapper.getServlet(JspServletWrapper.java:144)
 at
 org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:329)
 at
 org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:342)
 at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:267) ...
 21 more



 what might be the reason of this??
 everything else is working fine.. replication , searching..
 can anybody help??

 thanks  regards
 Karan jindal