Please Visit: http://lifelongprogrammer.blogspot.com
Shard Splitting and Document Routing in SolrCloud
http://www.slideshare.net/shalinmangar/solr-cloud-shardsplitting
http://www.slideshare.net/thelabdude/tjp-solr-webinar#
Document Routing: Custom Hashing
http://searchhub.org/2013/06/13/solr-cloud-document-routing/ numShards=4 router=compositeId
id = BigCo!doc5
q=my_query&shard.keys=BigCo!
Co-locate documents
SolrCloud Collections API
/admin/collections?action=CREATE|DELETE|RELOAD|CREATE&name=mycollection
Each shard is assigned a hash range
Each shard also has a state which defaults to 'ACTIVE'
Seamless on-the-fly splitting – no downtime required
● Retried on failures
● /admin/collections?
action=SPLITSHARD&collection=mycollection
– &shard=shardId
● A lower-level CoreAdmin API comes free!
– /admin/cores?action=SPLIT&core=core0&targetCore=core1&targetCore=core2
– /admin/cores?action=SPLIT&core=core0&path=/path/to/index/1&path=/path/to/index/2
https://issues.apache.org/jira/browse/SOLR-4816
1) Document routing: Updates are routed directly to the correct shard leader eliminating document routing at the server.
2) Optional parallel update execution: Updates for each shard are executed in a separate thread so parallel indexing can occur across the cluster.
https://issues.apache.org/jira/browse/SOLR-3076
Solr(Cloud) should support block joins
https://issues.apache.org/jira/browse/SOLR-5025
Implement true re-sharding for SolrCloud ==Unresolved
from Google Plus RSS Feed for 101157854606139706613 http://www.slideshare.net/shalinmangar/solr-cloud-shardsplitting
via LifeLong Community
Shard Splitting and Document Routing in SolrCloud
http://www.slideshare.net/shalinmangar/solr-cloud-shardsplitting
http://www.slideshare.net/thelabdude/tjp-solr-webinar#
Document Routing: Custom Hashing
http://searchhub.org/2013/06/13/solr-cloud-document-routing/ numShards=4 router=compositeId
id = BigCo!doc5
q=my_query&shard.keys=BigCo!
Co-locate documents
SolrCloud Collections API
/admin/collections?action=CREATE|DELETE|RELOAD|CREATE&name=mycollection
Each shard is assigned a hash range
Each shard also has a state which defaults to 'ACTIVE'
Seamless on-the-fly splitting – no downtime required
● Retried on failures
● /admin/collections?
action=SPLITSHARD&collection=mycollection
– &shard=shardId
● A lower-level CoreAdmin API comes free!
– /admin/cores?action=SPLIT&core=core0&targetCore=core1&targetCore=core2
– /admin/cores?action=SPLIT&core=core0&path=/path/to/index/1&path=/path/to/index/2
https://issues.apache.org/jira/browse/SOLR-4816
1) Document routing: Updates are routed directly to the correct shard leader eliminating document routing at the server.
2) Optional parallel update execution: Updates for each shard are executed in a separate thread so parallel indexing can occur across the cluster.
https://issues.apache.org/jira/browse/SOLR-3076
Solr(Cloud) should support block joins
https://issues.apache.org/jira/browse/SOLR-5025
Implement true re-sharding for SolrCloud ==Unresolved
from Google Plus RSS Feed for 101157854606139706613 http://www.slideshare.net/shalinmangar/solr-cloud-shardsplitting
via LifeLong Community
No comments:
Post a Comment