You are viewing a plain text version of this content. The canonical link for it is here.
Posted to solr-user@lucene.apache.org by "rajat.rastogi@hindustantimes.com" <ra...@hindustantimes.com> on 2017/06/07 11:10:34 UTC
Solr Issue While indexing Data
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
[cid:622f6e86-772f-47fb-9ef2-39cb0b9490ae@apcprd06.prod.outlook.com]
[cid:99669178-012a-48bb-82fb-6741c9e546f6@apcprd06.prod.outlook.com]
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 While indexing Data
Posted by Susheel Kumar <su...@gmail.com>.
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.rastogi@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&version=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&version=2&df=text}
> 2017-07-19 08:25:06.333 DEBUG (qtp434091818-7165) [ x:cda]
> o.a.s.u.p.LogUpdateProcessorFactory PRE_UPDATE FINISH
> {df=text&qt=edismax&wt=javabin&version=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&version=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&version=2&df=text}
> 2017-07-19 09:14:57.321 DEBUG (qtp434091818-10682) [ x:cda]
> o.a.s.u.p.LogUpdateProcessorFactory PRE_UPDATE FINISH
> {df=text&qt=edismax&wt=javabin&version=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&version=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&version=2&df=text}
> 2017-07-19 09:23:26.477 DEBUG (qtp434091818-10770) [ x:cda6m]
> o.a.s.u.p.LogUpdateProcessorFactory PRE_UPDATE FINISH
> {wt=javabin&version=2&df=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&version=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&qt=edismax&wt=javabin&version=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&version=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&version=2&df=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&df=text&qt=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&qt=edismax&waitSearcher=true&commit=true&
> softCommit=false&wt=javabin&version=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&commit=true&softCommit=false&
> wt=javabin&version=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&softCommit=false&df=text&waitSearcher=true&wt=
> javabin&version=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&version=2&df=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&df=text&qt=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&qt=edismax&waitSearcher=true&commit=true&
> softCommit=false&wt=javabin&version=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&commit=true&softCommit=false&
> wt=javabin&version=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&softCommit=false&df=text&waitSearcher=true&wt=
> javabin&version=2}
>
> For Better in sight
> regards
> Rajat
>
>
>
> --
> View this message in context: http://lucene.472066.n3.
> nabble.com/Solr-Issue-While-indexing-Data-tp4339417p4346762.html
> Sent from the Solr - User mailing list archive at Nabble.com.
>
Re: Solr Issue While indexing Data
Posted by rajat rastogi <ra...@hindustantimes.com>.
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&version=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&version=2&df=text}
2017-07-19 08:25:06.333 DEBUG (qtp434091818-7165) [ x:cda]
o.a.s.u.p.LogUpdateProcessorFactory PRE_UPDATE FINISH
{df=text&qt=edismax&wt=javabin&version=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&version=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&version=2&df=text}
2017-07-19 09:14:57.321 DEBUG (qtp434091818-10682) [ x:cda]
o.a.s.u.p.LogUpdateProcessorFactory PRE_UPDATE FINISH
{df=text&qt=edismax&wt=javabin&version=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&version=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&version=2&df=text}
2017-07-19 09:23:26.477 DEBUG (qtp434091818-10770) [ x:cda6m]
o.a.s.u.p.LogUpdateProcessorFactory PRE_UPDATE FINISH
{wt=javabin&version=2&df=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&version=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&qt=edismax&wt=javabin&version=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&version=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&version=2&df=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&df=text&qt=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&qt=edismax&waitSearcher=true&commit=true&softCommit=false&wt=javabin&version=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&commit=true&softCommit=false&wt=javabin&version=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&softCommit=false&df=text&waitSearcher=true&wt=javabin&version=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&version=2&df=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&df=text&qt=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&qt=edismax&waitSearcher=true&commit=true&softCommit=false&wt=javabin&version=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&commit=true&softCommit=false&wt=javabin&version=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&softCommit=false&df=text&waitSearcher=true&wt=javabin&version=2}
For Better in sight
regards
Rajat
--
View this message in context: http://lucene.472066.n3.nabble.com/Solr-Issue-While-indexing-Data-tp4339417p4346762.html
Sent from the Solr - User mailing list archive at Nabble.com.
Re: Solr Issue While indexing Data
Posted by rajat rastogi <ra...@hindustantimes.com>.
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
Posted by Erick Erickson <er...@gmail.com>.
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.rastogi@hindustantimes.com <
rajat.rastogi@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 While indexing Data
Posted by rajat rastogi <ra...@hindustantimes.com>.
hi Shawn ,
Top out put is as follows
<http://lucene.472066.n3.nabble.com/file/n4346917/Screen_Shot_2017-07-20_at_10.png>
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
Posted by Susheel Kumar <su...@gmail.com>.
By the way you shouldn't be running solr as root.
On Fri, Jul 21, 2017 at 12:06 AM, rajat rastogi <
rajat.rastogi@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+s472066n4346953h12@n3.nabble.com<mailto:ml+
> s472066n4346953h12@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&node=4339417&code=cmFqYXQucmFzdG9naUBoaW5kdXN0YW
> 50aW1lcy5jb218NDMzOTQxN3wtMTQwMjc3NDE5Mg==>.
> NAML<http://lucene.472066.n3.nabble.com/template/
> NamlServlet.jtp?macro=macro_viewer&id=instant_html%
> 21nabble%3Aemail.naml&base=nabble.naml.namespaces.
> BasicNamespace-nabble.view.web.template.NabbleNamespace-
> nabble.view.web.template.NodeNamespace&breadcrumbs=
> 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
Posted by rajat rastogi <ra...@hindustantimes.com>.
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...@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&node=4339417&code=cmFqYXQucmFzdG9naUBoaW5kdXN0YW50aW1lcy5jb218NDMzOTQxN3wtMTQwMjc3NDE5Mg==>.
NAML<http://lucene.472066.n3.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=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
Posted by rajat rastogi <ra...@hindustantimes.com>.
Hi Shawn ,
I mailed you the info @ apache@elyograg.org<ma...@elyograg.org>
I can resend it the mail.
regards
Rajat
On 20-Jul-2017, at 16:40, Shawn Heisey-2 [via Lucene] <ml...@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&node=4339417&code=cmFqYXQucmFzdG9naUBoaW5kdXN0YW50aW1lcy5jb218NDMzOTQxN3wtMTQwMjc3NDE5Mg==>.
NAML<http://lucene.472066.n3.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=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-tp4339417p4346956.html
Sent from the Solr - User mailing list archive at Nabble.com.
Re: Solr Issue While indexing Data
Posted by Shawn Heisey <ap...@elyograg.org>.
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
Posted by rajat rastogi <ra...@hindustantimes.com>.
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] <ml...@n3.nabble.com>> wrote:
On 6/7/2017 5:10 AM, [hidden email]<x-msg://6/user/SendEmail.jtp?type=node&node=4346826&i=0> 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<http://lucene.472066.n3.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=4339417&code=cmFqYXQucmFzdG9naUBoaW5kdXN0YW50aW1lcy5jb218NDMzOTQxN3wtMTQwMjc3NDE5Mg==>.
NAML<http://lucene.472066.n3.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=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-tp4339417p4346931.html
Sent from the Solr - User mailing list archive at Nabble.com.
Re: Solr Issue While indexing Data
Posted by Shawn Heisey <ap...@elyograg.org>.
On 6/7/2017 5:10 AM, rajat.rastogi@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