Filter filter, int n,
Sort sort), and it's normal.
At 2010-10-20 19:21:27，kafka0102 wrote:
>For solr's SolrIndexSearcher.search(QueryResult qr, QueryCommand cmd), I find
>it's too slowly.my index's size is about 500M, and record's num is 3984274.my
thanks a lot.
I got it.
On 2010年10月21日 22:36, Yonik Seeley wrote:
2010/10/21 kafka0102:
I found the problem's cause.It's the DocSetCollector. my fitler query result's
size is about 300,so the DocSetCollector.getDocSet() is OpenBitSet. And
300 OpenBitSet.fastSet(doc)
It takes about one hour to replacate 6G index for solr in my env. But my
network can transfer file about 10-20M/s using scp. So solr's http replcation
is too slow, it's normal or I do something wrong?
I hacked SnapPuller to log the cost, and the log is like thus:
[2010-11-01
17:21:19][INFO][pool-6-thread-1][SnapPuller.java(1037)]readFully1048576 cost 979
[2010-11-01
17:21:19][INFO][pool-6-thread-1][SnapPuller.java(1037)]readFully1048576 cost 4
[2010-11-01
17:21:19][INFO][pool-6-thread-1][Snap
ith my env
At 2010-11-01 17:30:32，kafka0102 wrote:
I hacked SnapPuller to log the cost, and the log is like thus:
[2010-11-01
17:21:19][INFO][pool-6-thread-1][SnapPuller.java(1037)]readFully1048576 cost 979
[2010-11-01
17:21:19][INFO][pool-6-thread-1][SnapPuller.java(1037)]readFully1048576 cost
8:54，"Lance Norskog" wrote:
>This is the time to replicate and open the new index, right? Opening a
>new index can take a lot of time. How many autowarmers and queries are
>there in the caches? Opening a new index re-runs all of the queries in
>all of the caches.
>
>2010
Does anyone care about this?
I use task queue for now.
I think DIH delta cannot handle changed data very well. For aim db,it needs not
only a last_index_time collum. If a row is deleted, DIH delta cannot know it.
So it need another boolean collum marking whether the row is
deleted.However,thus h
In my app,I want to search numdocs for some queries. I see SolrIndexSearcher
has two methods:
public int numDocs(Query a, DocSet b)
public int numDocs(Query a, Query b)
But these're not fit for me.For search's params,I get q and fq, and q' results
are not in filterCache.But above methods are bot
numDocs methods seem just for filterCache. So I just need use QueryResult
search(QueryResult qr, QueryCommand cmd) by setting QueryCommand.len=0?I would
try it.
At 2010-11-19 15:49:31，kafka0102 wrote:
In my app,I want to search numdocs for some queries. I see SolrIndexSearcher
has two methods
my replication got errors like :
Unable to move index file from:
/home/data/tuba/search-index/eshequn.post.db_post/index.20101122034500/_21.frq
to:
/home/data/tuba/search-index/eshequn.post.db_post/index.20101122031000/_21.frq
I looked at log and found the last slave replication commit before t
er.DATE_FMT = "MMddHHmmss" should be fine.
At 2010-11-22 21:13:41，"Erick Erickson" wrote:
>what op system are you on? what version of Solr? what filesystem?
>
>It's really hard to help without more information, you might want to review:
>http://wiki.apach
Does anyone care about the bug?
At 2010-11-22 22:28:39，kafka0102 wrote:
>sorry for my unclear question.
>My solr's version is 1.4.1,and I maybe hit a solr's bug.
>In my case,my slave's using index's directory is index.20101122031000.It was
>generated at 201
12 matches
Mail list logo
