lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "scott.chu" <>
Subject Re: Updating error while add doc to Solrcloud
Date Tue, 17 May 2016 06:36:34 GMT

I clear the cugna collection data (by renaming 'data' folder to 'xdata')and restart Solrcloud.
I add previous possible-error xml doc, it succeeds. So I'm sure doc data has no problem. Is
it because the index file size is too large? If the zk nodes fails during adding doc, could
it cause this updating error since I do see some "can't find leader error' in solr log?

2016/5/17 (週二)
----- Original Message ----- 
From: scott(自己) 
To: solr-user 
Date: 2016/5/17 (週二) 14:29
Subject: Updating error while add doc to Solrcloud

I build Solrcloud with 2 nodes, 1 shard, 2 replica. I add doc in xml format using post.jar
up to 2.85M+ no. of docs and 10gb index size. When I add more docs. the solr.log shows: 

    2016-05-17 14:01:09,024 WARN (main) [ ] o.e.j.s.h.RequestLogHandler !RequestLog 
    2016-05-17 14:01:09,275 WARN (main) [ ] o.e.j.s.SecurityHandler ServletContext@o.e.j.w.WebAppContext@57fffcd7{/solr,file:/D:/portable_sw/solr-5.4.1/server/solr-webapp/webapp/,STARTING}{D:\portable_sw\solr-5.4.1\server/solr-webapp/webapp}
has uncovered http methods for path: / 
    2016-05-17 14:01:09,346 WARN (main) [ ] o.a.s.c.CoreContainer Couldn't add files from
D:\portable_sw\solr-5.4.1\mynodes\cloud\node1\lib to classpath: D:\portable_sw\solr-5.4.1\mynodes\cloud\node1\lib

    2016-05-17 14:01:11,419 WARN (coreLoadExecutor-7-thread-1-processing-n:
[c:cugna s:shard1 r:core_node2 x:cugna_shard1_replica2] o.a.s.u.UpdateLog Exception reverse
reading log 

Later I stop all and kill write.lock (I ususally do this in Solr 3 when add doc fails) and
add doc again but Solrcloud show can't find write.lock. So I recover write.lock and call post.jar
again. The output shows: 

    "SimplePostTool version 5.0.0 
    Posting files to [base] url http://localhost:8983/solr/cugna/update using content-type
    POSTing file NMLBOym_a_UN2000_10_20160511_1014.xml to [base] 
    SimplePostTool: WARNING: Solr returned an error #400 (Bad Request) for url: http://localhost:8983/solr/cugna/update

    SimplePostTool: WARNING: Response: <?xml version="1.0" encoding="UTF-8"?> 
    <lst name="responseHeader"><int name="status">400</int><int name="QTime">3</int></lst><lst
name="error"><str name="msg"> 
    Exception writing document id un_555917 to the index; possible analysis error.</str><int
    SimplePostTool: WARNING: IOException while reading response: Server
returned HTTP response code: 40 
    0 for URL: http://localhost:8983/solr/cugna/update 
    1 files indexed. 
    COMMITting Solr index changes to http://localhost:8983/solr/cugna/update... 
    Time spent: 0:00:00.259" 

I thought it's that doc un_555917 problem, then I comment out it in xml and do again, it keeps
showing same error to every single doc. I assume there's something wrong with Solrcloud. Does
anyone experience this before? What could be the problem? Can I recover it? Or I have to add
all docs again? 

2016/5/17 (週二) 
----- Original Message ----- 
From: scott(自己) 
To: solr-user 
Date: 2016/5/17 (週二) 09:39 
Subject: Re(2): [scottchu] Cab I migrate solrcloud by just copying wholepackagefolder? 

OK! Thanks for reminding. I'll stick to the convention. 

2016/5/17 (週二) 
----- Original Message ----- 
From: Chris Hostetter 
To: solr-user ; scott(自己) 
Date: 2016/5/17 (週二) 02:43 
Subject: Re: [scottchu] Cab I migrate solrcloud by just copying whole packagefolder? 

: Message-Id: <> 
: Subject: [scottchu] Cab I migrate solrcloud by just copying whole package 
: folder? 
: References: 
: <><C162E1B1F0311FC46A64E2E2AA 
: <> 
: In-Reply-To: <> 
Thread Hijacking on Mailing Lists 

When starting a new discussion on a mailing list, please do not reply to 
an existing message, instead start a fresh email. Even if you change the 
subject line of your email, other mail headers still track which thread 
you replied to and your question is "hidden" in that thread and gets less 
attention. It makes following discussions in the mailing list archives 
particularly difficult. 


??? AVG ?? - 
??: 2015.0.6201 / ???: 4568/12238 - ????: 05/15/16 

已透過 AVG 檢查 - 
版本: 2015.0.6201 / 病毒庫: 4568/12245 - 發佈日期: 05/16/16 

已透過 AVG 檢查 - 
版本: 2015.0.6201 / 病毒庫: 4568/12245 - 發佈日期: 05/16/16
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message