Re: Regarding Solr Cloud issue...

[Chris]

I am also trying with something like -

java -Durl=http://domainname.com:1981/solr/web/update-Dtype=application/json
-jar /solr4RA/example1/exampledocs/post.jar
/root/Desktop/web/*.json

but it is giving error -

19:06:22 ERROR SolrCore org.apache.solr.common.SolrException: Unknown
command: subDomain [12]

org.apache.solr.common.SolrException: Unknown command: subDomain [12]
at 
org.apache.solr.handler.loader.JsonLoader$SingleThreadedJsonLoader.processUpdate(JsonLoader.java:152)
at 
org.apache.solr.handler.loader.JsonLoader$SingleThreadedJsonLoader.load(JsonLoader.java:101)
at org.apache.solr.handler.loader.JsonLoader.load(JsonLoader.java:65)
at 
org.apache.solr.handler.UpdateRequestHandler$1.load(UpdateRequestHandler.java:92)
at 
org.apache.solr.handler.ContentStreamHandlerBase.handleRequestBody(ContentStreamHandlerBase.java:74)
at 
org.apache.solr.handler.RequestHandlerBase.handleRequest(RequestHandlerBase.java:135)
at org.apache.solr.core.SolrCore.execute(SolrCore.java:1859)
at 
org.apache.solr.servlet.SolrDispatchFilter.execute(SolrDispatchFilter.java:703)
at 
org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:406)
at 
org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:195)
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.content(AbstractHttpConnection.java:953)
at 
org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.content(AbstractHttpConnection.java:1014)
at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:861)
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)




On Thu, Oct 17, 2013 at 6:31 PM, Chris  wrote:

> Wow thanks for all that, i just upgraded, linked my plugins & it seems
> fine so far, but i have run into another issue
>
> while adding a document to the solr cloud it says -
> org.apache.solr.common.SolrException: Unknown document router
> '{name=compositeId}'
>
> in the clusterstate.json i can see -
>
>  "shard5":{
> "range":"4ccc-7fff",
> "state":"active",
> "replicas":{"core_node4":{
> "state":"active",
> "base_url":"http://64.251.14.47:1984/solr";,
> "core":"web_shard5_replica1",
> "node_name":"64.251.14.47:1984_solr",
> "leader":"true",
> "maxShardsPerNode":"2",
> "router":{"name":"compositeId"},
> "replicationFactor":"1"},
>
> I am using this to add -
>
>
>  CloudSolrServer solrCoreCloud = new 
> CloudSolrServer(cloudURL);
>
>  solrCoreCloud.setDefaultCollection("web");
>
>UpdateResponse up = solrCoreCloud.addBean(resultItem);
>UpdateResponse upr = solrCoreCloud.commit();
>
> Please advice.
>
>
>
>
>
> On Wed, Oct 16, 2013 at 9:49 PM, Shawn Heisey  wrote:
>
>> On 10/16/2013 4:51 AM, Chris wrote:
>> > Also, is there any easy way upgrading to 4.5 without having to change
>> most
>> > of my plugi

Re: Regarding Solr Cloud issue...

[Chris]

Wow thanks for all that, i just upgraded, linked my plugins & it seems fine
so far, but i have run into another issue

while adding a document to the solr cloud it says -
org.apache.solr.common.SolrException: Unknown document router
'{name=compositeId}'

in the clusterstate.json i can see -

 "shard5":{
"range":"4ccc-7fff",
"state":"active",
"replicas":{"core_node4":{
"state":"active",
"base_url":"http://64.251.14.47:1984/solr";,
"core":"web_shard5_replica1",
"node_name":"64.251.14.47:1984_solr",
"leader":"true",
"maxShardsPerNode":"2",
"router":{"name":"compositeId"},
"replicationFactor":"1"},

I am using this to add -

   CloudSolrServer solrCoreCloud = new 
CloudSolrServer(cloudURL);
   solrCoreCloud.setDefaultCollection("web");
   UpdateResponse up = solrCoreCloud.addBean(resultItem);
   UpdateResponse upr = solrCoreCloud.commit();

Please advice.





On Wed, Oct 16, 2013 at 9:49 PM, Shawn Heisey  wrote:

> On 10/16/2013 4:51 AM, Chris wrote:
> > Also, is there any easy way upgrading to 4.5 without having to change
> most
> > of my plugins & configuration files?
>
> Upgrading is something that should be done carefully.  If you can, it's
> always recommended that you try it out on dev hardware with your real
> index data beforehand, so you can deal with any problems that arise
> without causing problems for your production cluster.  Upgrading
> SolrCloud is particularly tricky, because for a while you will be
> running different versions on different machines in your cluster.
>
> If you're using your own custom software to go with Solr, or you're
> using third-party plugins that aren't included in the Solr download,
> upgrading might take more effort than usual.  Also, if you are doing
> anything in your config/schema that changes the format of the Lucene
> index, you may find that it can't be upgraded without completely
> rebuilding the index.  Examples of this are changing the postings format
> or docValues format.  This is a very nasty complication with SolrCloud,
> because those configurations affect the entire cluster.  In that case,
> the whole index may need to be rebuilt without custom formats before
> upgrading is attempted.
>
> If you don't have any of the complications mentioned in the preceding
> paragraph, upgrading is usually a very simple process:
>
> *) Shut down Solr.
> *) Delete the extracted WAR file directory.
> *) Replace solr.war with the new war from dist/ in the download.
> **) Usually it must actually be named solr.war, which means renaming it.
> *) Delete and replace other jars copied from the download.
> *) Change luceneMatchVersion in all solrconfig.xml files. **
> *) Start Solr back up.
>
> ** With SolrCloud, you can't actually change the luceneMatchVersion
> until all of your servers have been upgraded.
>
> A full reindex is strongly recommended.  With SolrCloud, it normally
> needs to wait until all servers are upgraded.  In situations where it
> won't work at all without a reindex, upgrading SolrCloud can be very
> challenging.
>
> It's strongly recommended that you look over CHANGES.txt and compare the
> new example config/schema with the example from the old version, to see
> if there are any changes that you might want to incorporate into your
> own config.  As with luceneMatchVersion, if you're running SolrCloud,
> those changes might need to wait until you're fully upgraded.
>
> Side note: When upgrading to a new minor version, config changes aren't
> normally required.  They will usually be required when upgrading major
> versions, such as 3.x to 4.x.
>
> If you *do* have custom plugins that aren't included in the Solr
> download, you may have to recompile them for the new version, or wait
> for the vendor to create a new version before you upgrade.
>
> This is only the tip of the iceberg, but a lot of the rest of it depends
> greatly on your configurations.
>
> Thanks,
> Shawn
>
>

Re: Regarding Solr Cloud issue...

[Shawn Heisey]

On 10/16/2013 4:51 AM, Chris wrote:
> Also, is there any easy way upgrading to 4.5 without having to change most
> of my plugins & configuration files?

Upgrading is something that should be done carefully.  If you can, it's
always recommended that you try it out on dev hardware with your real
index data beforehand, so you can deal with any problems that arise
without causing problems for your production cluster.  Upgrading
SolrCloud is particularly tricky, because for a while you will be
running different versions on different machines in your cluster.

If you're using your own custom software to go with Solr, or you're
using third-party plugins that aren't included in the Solr download,
upgrading might take more effort than usual.  Also, if you are doing
anything in your config/schema that changes the format of the Lucene
index, you may find that it can't be upgraded without completely
rebuilding the index.  Examples of this are changing the postings format
or docValues format.  This is a very nasty complication with SolrCloud,
because those configurations affect the entire cluster.  In that case,
the whole index may need to be rebuilt without custom formats before
upgrading is attempted.

If you don't have any of the complications mentioned in the preceding
paragraph, upgrading is usually a very simple process:

*) Shut down Solr.
*) Delete the extracted WAR file directory.
*) Replace solr.war with the new war from dist/ in the download.
**) Usually it must actually be named solr.war, which means renaming it.
*) Delete and replace other jars copied from the download.
*) Change luceneMatchVersion in all solrconfig.xml files. **
*) Start Solr back up.

** With SolrCloud, you can't actually change the luceneMatchVersion
until all of your servers have been upgraded.

A full reindex is strongly recommended.  With SolrCloud, it normally
needs to wait until all servers are upgraded.  In situations where it
won't work at all without a reindex, upgrading SolrCloud can be very
challenging.

It's strongly recommended that you look over CHANGES.txt and compare the
new example config/schema with the example from the old version, to see
if there are any changes that you might want to incorporate into your
own config.  As with luceneMatchVersion, if you're running SolrCloud,
those changes might need to wait until you're fully upgraded.

Side note: When upgrading to a new minor version, config changes aren't
normally required.  They will usually be required when upgrading major
versions, such as 3.x to 4.x.

If you *do* have custom plugins that aren't included in the Solr
download, you may have to recompile them for the new version, or wait
for the vendor to create a new version before you upgrade.

This is only the tip of the iceberg, but a lot of the rest of it depends
greatly on your configurations.

Thanks,
Shawn

Re: Regarding Solr Cloud issue...

[Chris]

very well, i will try the same, maybe an auto update tool should be also
put on the line...just a thought ...


On Wed, Oct 16, 2013 at 6:20 PM,  wrote:

> Hm, good question. I haven't really done any upgrading yet, because I just
> reinstall and reindex everything. I would replace jars with the new ones
> (if needed - check release notes for version 4.4.0 and 4.5.0 where all the
> versions of external tools [tika, maven, etc.] are stated) and deploy the
> updated WAR file to servlet container.
>
> Primoz
>
>
>
>
> From:   Chris 
> To: solr-user 
> Date:   16.10.2013 14:30
> Subject:Re: Regarding Solr Cloud issue...
>
>
>
> oh great. Thanks Primoz.
>
> is there any simple way to do the upgrade to 4.5 without having to change
> my configurations? update a few jar files etc?
>
>
> On Wed, Oct 16, 2013 at 4:58 PM,  wrote:
>
> > >>> Also, another issue that needs to be raised is the creation of cores
> > from
> > >>> the "core admin" section of the gui, doesnt really work well, it
> > creates
> > >>> files but then they do not work (again i am using 4.4)
> >
> > From my experience "core admin" section of the GUI does not work well in
> > SolrCloud domain. If I am not mistaken this was somehow fixed in 4.5.0
> > which acts much better.
> >
> > I would use only HTTP requests ("cores and collections API") with
> > SolrCloud and would use GUI only for viewing the state of cluster and
> > cores.
> >
> > Primoz
> >
> >
> >
>
>

Re: Regarding Solr Cloud issue...

[primoz . skale]

Hm, good question. I haven't really done any upgrading yet, because I just 
reinstall and reindex everything. I would replace jars with the new ones 
(if needed - check release notes for version 4.4.0 and 4.5.0 where all the 
versions of external tools [tika, maven, etc.] are stated) and deploy the 
updated WAR file to servlet container.

Primoz




From:   Chris 
To: solr-user 
Date:   16.10.2013 14:30
Subject:    Re: Regarding Solr Cloud issue...



oh great. Thanks Primoz.

is there any simple way to do the upgrade to 4.5 without having to change
my configurations? update a few jar files etc?


On Wed, Oct 16, 2013 at 4:58 PM,  wrote:

> >>> Also, another issue that needs to be raised is the creation of cores
> from
> >>> the "core admin" section of the gui, doesnt really work well, it
> creates
> >>> files but then they do not work (again i am using 4.4)
>
> From my experience "core admin" section of the GUI does not work well in
> SolrCloud domain. If I am not mistaken this was somehow fixed in 4.5.0
> which acts much better.
>
> I would use only HTTP requests ("cores and collections API") with
> SolrCloud and would use GUI only for viewing the state of cluster and
> cores.
>
> Primoz
>
>
>

Re: Regarding Solr Cloud issue...

[Chris]

oh great. Thanks Primoz.

is there any simple way to do the upgrade to 4.5 without having to change
my configurations? update a few jar files etc?


On Wed, Oct 16, 2013 at 4:58 PM,  wrote:

> >>> Also, another issue that needs to be raised is the creation of cores
> from
> >>> the "core admin" section of the gui, doesnt really work well, it
> creates
> >>> files but then they do not work (again i am using 4.4)
>
> From my experience "core admin" section of the GUI does not work well in
> SolrCloud domain. If I am not mistaken this was somehow fixed in 4.5.0
> which acts much better.
>
> I would use only HTTP requests ("cores and collections API") with
> SolrCloud and would use GUI only for viewing the state of cluster and
> cores.
>
> Primoz
>
>
>

Re: Regarding Solr Cloud issue...

[primoz . skale]

>>> Also, another issue that needs to be raised is the creation of cores 
from
>>> the "core admin" section of the gui, doesnt really work well, it 
creates
>>> files but then they do not work (again i am using 4.4)

>From my experience "core admin" section of the GUI does not work well in 
SolrCloud domain. If I am not mistaken this was somehow fixed in 4.5.0 
which acts much better.

I would use only HTTP requests ("cores and collections API") with 
SolrCloud and would use GUI only for viewing the state of cluster and 
cores.

Primoz

Re: Regarding Solr Cloud issue...

[Chris]

quot;compositeId"},
>>   "Reference":{
>> "shards":{
>>   "shard1":{
>> "range":"8000-b332",
>> "state":"active",
>> "replicas":{"core_node1":{
>> "state":"active",
>> "core":"Reference_shard1_replica1",
>> "node_name":"64.251.14.47:1984_solr",
>> "base_url":"http://64.251.14.47:1984/solr";,
>> "leader":"true"}}},
>>   "shard3":{
>> "range":"e666-1998",
>> "state":"active",
>> "replicas":{"core_node2":{
>> "state":"active",
>> "core":"Reference_shard3_replica1",
>> "node_name":"64.251.14.47:1985_solr",
>> "base_url":"http://64.251.14.47:1985/solr";,
>> "leader":"true"}}},
>>   "shard4":{
>> "range":"1999-4ccb",
>> "state":"active",
>> "replicas":{"core_node5":{
>> "state":"active",
>> "core":"Reference_shard4_replica1",
>> "node_name":"64.251.14.47:1982_solr",
>> "base_url":"http://64.251.14.47:1982/solr";,
>> "leader":"true"}}},
>>   "shard5":{
>> "range":"4ccc-7fff",
>> "state":"active",
>> "replicas":{"core_node4":{
>> "state":"active",
>> "core":"Reference_shard5_replica1",
>> "node_name":"64.251.14.47:1983_solr",
>> "base_url":"http://64.251.14.47:1983/solr";,
>> "leader":"true"}}},
>>   "shard2":{
>> "range":null,
>> "state":"active",
>> "replicas":{"core_node3":{
>> "state":"active",
>> "core":"Reference_shard2_replica1",
>> "node_name":"64.251.14.47:1981_solr",
>> "base_url":"http://64.251.14.47:1981/solr";,
>> "leader":"true",
>> "router":"compositeId"},
>>   "web":{
>> "shards":{
>>   "shard1":{
>> "range":"8000-b332",
>> "state":"active",
>>     "replicas":{
>>   "core_node4":{
>> "state":"active",
>> "core":"web_shard1_replica2",
>> "node_name":"64.251.14.47:1983_solr",
>> "base_url":"http://64.251.14.47:1983/solr"},
>>   "core_node2":{
>> "state":"active",
>> "core":"web_shard1_replica1",
>> "node_name":"64.251.14.47:1981_solr",
>> "base_url":"http://64.251.14.47:1981/solr";,
>> "leader":"true"}}},
>>   "shard2":{
>> "range":"b333-e665",
>> "state":"active",
>> "replicas":{
>>   "core_node6":{
>> "state":"active",
>> "core":"web_shard2_replica1",
>> "node_name":"64.251.14.47:1982_solr",
>> "base_url":"http://64.251.14.47:1982/solr"},
>>   "core_node7":{
>> "state":"active",
>> "core":"web_shard2_replica2",
>> "node_name":"64.251.14.47:1984_solr",
>>     "base_url":"http://64.251.14.47:1984/solr";,
>> "leader":"true"}}},
>>   "shard3&q

Re: Regarding Solr Cloud issue...

[Chris]

e"}}},
>   "shard4":{
> "range":"1999-4ccb",
> "state":"active",
> "replicas":{"core_node5":{
> "state":"active",
> "core":"Reference_shard4_replica1",
> "node_name":"64.251.14.47:1982_solr",
> "base_url":"http://64.251.14.47:1982/solr";,
> "leader":"true"}}},
>   "shard5":{
> "range":"4ccc-7fff",
> "state":"active",
> "replicas":{"core_node4":{
> "state":"active",
> "core":"Reference_shard5_replica1",
> "node_name":"64.251.14.47:1983_solr",
> "base_url":"http://64.251.14.47:1983/solr";,
>     "leader":"true"}}},
>   "shard2":{
> "range":null,
> "state":"active",
> "replicas":{"core_node3":{
> "state":"active",
> "core":"Reference_shard2_replica1",
> "node_name":"64.251.14.47:1981_solr",
> "base_url":"http://64.251.14.47:1981/solr";,
> "leader":"true",
> "router":"compositeId"},
>   "web":{
> "shards":{
>   "shard1":{
> "range":"8000-b332",
> "state":"active",
> "replicas":{
>   "core_node4":{
> "state":"active",
> "core":"web_shard1_replica2",
> "node_name":"64.251.14.47:1983_solr",
> "base_url":"http://64.251.14.47:1983/solr"},
>   "core_node2":{
> "state":"active",
> "core":"web_shard1_replica1",
> "node_name":"64.251.14.47:1981_solr",
> "base_url":"http://64.251.14.47:1981/solr";,
> "leader":"true"}}},
>   "shard2":{
> "range":"b333-e665",
> "state":"active",
> "replicas":{
>   "core_node6":{
> "state":"active",
> "core":"web_shard2_replica1",
> "node_name":"64.251.14.47:1982_solr",
> "base_url":"http://64.251.14.47:1982/solr"},
>   "core_node7":{
> "state":"active",
> "core":"web_shard2_replica2",
> "node_name":"64.251.14.47:1984_solr",
> "base_url":"http://64.251.14.47:1984/solr";,
> "leader":"true"}}},
>   "shard3":{
> "range":"e666-1998",
> "state":"active",
> "replicas":{
>   "core_node9":{
> "state":"active",
> "core":"web_shard3_replica1",
> "node_name":"64.251.14.47:1985_solr",
> "base_url":"http://64.251.14.47:1985/solr"},
>   "core_node1":{
> "state":"active",
> "core":"web_shard3_replica2",
>     "node_name":"64.251.14.47:1981_solr",
> "base_url":"http://64.251.14.47:1981/solr";,
> "leader":"true"}}},
>   "shard4":{
> "range":"1999-4ccb",
> "state":"active",
> "replicas":{
>   "core_node3":{
> "state":"active",
> "core":"web_shard4_replica2",
> "node_name":"64.251.14.47:1982_solr",
> "base_url":"http://64.251.14.47:1982/solr"},
>   "core_node5":{
> "state":"active",
> "core":"web_shard4_repli

Re: Regarding Solr Cloud issue...

[Chris]

"replicas":{
  "core_node4":{
"state":"active",
"core":"image_shard3_replica2",
"node_name":"64.251.14.47:1982_solr",
"base_url":"http://64.251.14.47:1982/solr"},
  "core_node7":{
"state":"active",
"core":"image_shard3_replica1",
"node_name":"64.251.14.47:1983_solr",
"base_url":"http://64.251.14.47:1983/solr";,
"leader":"true"}}},
  "shard4":{
"range":"1999-4ccb",
"state":"active",
"replicas":{
  "core_node2":{
"state":"active",
"core":"image_shard4_replica1",
"node_name":"64.251.14.47:1985_solr",
"base_url":"http://64.251.14.47:1985/solr"},
  "core_node6":{
"state":"active",
"core":"image_shard4_replica2",
"node_name":"64.251.14.47:1981_solr",
"base_url":"http://64.251.14.47:1981/solr";,
"leader":"true"}}},
  "shard5":{
"range":"4ccc-7fff",
"state":"active",
"replicas":{
  "core_node8":{
"state":"active",
"core":"image_shard5_replica2",
"node_name":"64.251.14.47:1983_solr",
"base_url":"http://64.251.14.47:1983/solr"},
  "core_node10":{
"state":"active",
"core":"image_shard5_replica1",
"node_name":"64.251.14.47:1984_solr",
"base_url":"http://64.251.14.47:1984/solr";,
"leader":"true",
"router":"compositeId"},
  "Reference":{
"shards":{
  "shard1":{
"range":"8000-b332",
"state":"active",
"replicas":{"core_node1":{
"state":"active",
"core":"Reference_shard1_replica1",
"node_name":"64.251.14.47:1984_solr",
"base_url":"http://64.251.14.47:1984/solr";,
"leader":"true"}}},
  "shard3":{
"range":"e666-1998",
"state":"active",
"replicas":{"core_node2":{
"state":"active",
"core":"Reference_shard3_replica1",
"node_name":"64.251.14.47:1985_solr",
"base_url":"http://64.251.14.47:1985/solr";,
"leader":"true"}}},
  "shard4":{
"range":"1999-4ccb",
"state":"active",
"replicas":{"core_node5":{
"state":"active",
"core":"Reference_shard4_replica1",
"node_name":"64.251.14.47:1982_solr",
"base_url":"http://64.251.14.47:1982/solr";,
"leader":"true"}}},
  "shard5":{
"range":"4ccc-7fff",
"state":"active",
"replicas":{"core_node4":{
"state":"active",
"core":"Reference_shard5_replica1",
"node_name":"64.251.14.47:1983_solr",
"base_url":"http://64.251.14.47:1983/solr";,
"leader":"true"}}},
  "shard2":{
"range":null,
"state":"active",
"replicas":{"core_node3":{
"state":"active",
"core":"Reference_shard2_replica1",
"node_name":"64.251.14.47:1981_solr",
"base_url":"http://64.251.14.47:1981/solr";,
"leader":"true",
"router":"compositeId"},
  "web":{
"shards":{
  "shard1":{
"rang

Re: Regarding Solr Cloud issue...

[primoz . skale]

Yap, you are right - I only created extra replicas with cores API. For a 
new shard I had to use "split shard" command.

My apologies.

Primož



From:   Shalin Shekhar Mangar 
To: solr-user@lucene.apache.org
Date:   16.10.2013 10:45
Subject:    Re: Regarding Solr Cloud issue...



If the initial collection was created with a numShards parameter (and 
hence
compositeId router then there was no way to create a new logical shard. 
You
can add replicas with the core admin API but only to shards that already
exist. A new logical shard can only be created by splitting an existing 
one.

The "createshard" API also has the same limitation -- it cannot create a
shard for a collection with compositeId router. It is supposed to be used
for collections with custom sharding (i.e. "implicit" router). In such
collections, there is no concept of a hash range and routing is done
explicitly by the user using the "shards" parameter in the request or by
sending the request to the target core/node directly.

So, in summary, attempting to add a new logical shard to a collection with
compositeId router via CoreAdmin APIs is wrong, unsupported and should be
disallowed. Adding replicas to existing logical shards is okay though.


On Wed, Oct 16, 2013 at 12:56 PM,  wrote:

> If I am not mistaken the only way to create a new shard from a 
collection
> in 4.4.0 was to use cores API. That worked fine for me until I used
> *other* cores API commands. Those usually produced null ranges.
>
> In 4.5.0 this is fixed with newly added commands "createshard" etc. to 
the
> collections API, right?
>
> Primoz
>
>
>
> From:   Shalin Shekhar Mangar 
> To:     solr-user@lucene.apache.org
> Date:   16.10.2013 09:06
> Subject:Re: Regarding Solr Cloud issue...
>
>
>
> Chris, can you post your complete clusterstate.json? Do all shards have 
a
> null range? Also, did you issue any core admin CREATE commands apart 
from
> the create collection api.
>
> Primoz, I was able to reproduce this but by doing an illegal operation.
> Suppose I create a collection with numShards=5 and then I issue a core
> admin create command such as:
>
> 
http://localhost:8983/solr/admin/cores?action=CREATE&name=xyz&collection=mycollection51&shard=shard6

>
>
> Then a "shard6" is added to the collection with a null range. This is a
> bug
> because we should never allow such a core admin create to succeed 
anyway.
> I'll open an issue.
>
>
>
> On Wed, Oct 16, 2013 at 11:49 AM,  wrote:
>
> > I sometimes also do get null ranges when doing colletions/cores API
> > actions CREATE or/and UNLOAD, etc... In 4.4.0 that was not easily 
fixed
> > because zkCli had problems with "putfile" command, but in 4.5.0 it 
works
> > OK. All you have to do is "download" clusterstate.json from ZK ("get
> > /clusterstate.json"), fix ranges to appropriate values and upload the
> file
> > back to ZK with zkCli.
> >
> > But why those null ranges happen at all is beyond me :)
> >
> > Primoz
> >
> >
> >
> > From:   Shalin Shekhar Mangar 
> > To: solr-user@lucene.apache.org
> > Date:   16.10.2013 07:37
> > Subject:Re: Regarding Solr Cloud issue...
> >
> >
> >
> > I'm sorry I am not able to reproduce this issue.
> >
> > I started 5 solr-4.4 instances.
> > I copied example directory into example1, example2, example3 and
> example4
> > cd example; java -Dbootstrap_confdir=./solr/collection1/conf
> > -Dcollection.configName=myconf -DzkRun -DnumShards=1 -jar start.jar
> > cd example1; java -Djetty.port=7574 -DzkHost=localhost:9983 -jar
> start.jar
> > cd example2; java -Djetty.port=7575 -DzkHost=localhost:9983 -jar
> start.jar
> > cd example3; java -Djetty.port=7576 -DzkHost=localhost:9983 -jar
> start.jar
> > cd example4; java -Djetty.port=7577 -DzkHost=localhost:9983 -jar
> start.jar
> >
> > After that I invoked:
> >
> >
>
> 
http://localhost:8983/solr/admin/collections?action=CREATE&name=mycollection51&numShards=5&replicationFactor=1

>
> >
> >
> > I can see all shards having non-null ranges in clusterstate.
> >
> >
> > On Tue, Oct 15, 2013 at 8:47 PM, Chris  wrote:
> >
> > > Hi Shalin,.
> > >
> > > Thank you for your quick reply. I appreciate all the help.
> > >
> > > I started the solr cloud servers first...with 5 nodes.
> > >
> > > then i issued a command like below to create the shards -
> > >
> > >
> > >
> >
> >
>
> 
http://localhost:8983/solr/ad

Re: Regarding Solr Cloud issue...

[Shalin Shekhar Mangar]

If the initial collection was created with a numShards parameter (and hence
compositeId router then there was no way to create a new logical shard. You
can add replicas with the core admin API but only to shards that already
exist. A new logical shard can only be created by splitting an existing one.

The "createshard" API also has the same limitation -- it cannot create a
shard for a collection with compositeId router. It is supposed to be used
for collections with custom sharding (i.e. "implicit" router). In such
collections, there is no concept of a hash range and routing is done
explicitly by the user using the "shards" parameter in the request or by
sending the request to the target core/node directly.

So, in summary, attempting to add a new logical shard to a collection with
compositeId router via CoreAdmin APIs is wrong, unsupported and should be
disallowed. Adding replicas to existing logical shards is okay though.


On Wed, Oct 16, 2013 at 12:56 PM,  wrote:

> If I am not mistaken the only way to create a new shard from a collection
> in 4.4.0 was to use cores API. That worked fine for me until I used
> *other* cores API commands. Those usually produced null ranges.
>
> In 4.5.0 this is fixed with newly added commands "createshard" etc. to the
> collections API, right?
>
> Primoz
>
>
>
> From:   Shalin Shekhar Mangar 
> To:     solr-user@lucene.apache.org
> Date:   16.10.2013 09:06
> Subject:Re: Regarding Solr Cloud issue...
>
>
>
> Chris, can you post your complete clusterstate.json? Do all shards have a
> null range? Also, did you issue any core admin CREATE commands apart from
> the create collection api.
>
> Primoz, I was able to reproduce this but by doing an illegal operation.
> Suppose I create a collection with numShards=5 and then I issue a core
> admin create command such as:
>
> http://localhost:8983/solr/admin/cores?action=CREATE&name=xyz&collection=mycollection51&shard=shard6
>
>
> Then a "shard6" is added to the collection with a null range. This is a
> bug
> because we should never allow such a core admin create to succeed anyway.
> I'll open an issue.
>
>
>
> On Wed, Oct 16, 2013 at 11:49 AM,  wrote:
>
> > I sometimes also do get null ranges when doing colletions/cores API
> > actions CREATE or/and UNLOAD, etc... In 4.4.0 that was not easily fixed
> > because zkCli had problems with "putfile" command, but in 4.5.0 it works
> > OK. All you have to do is "download" clusterstate.json from ZK ("get
> > /clusterstate.json"), fix ranges to appropriate values and upload the
> file
> > back to ZK with zkCli.
> >
> > But why those null ranges happen at all is beyond me :)
> >
> > Primoz
> >
> >
> >
> > From:   Shalin Shekhar Mangar 
> > To: solr-user@lucene.apache.org
> > Date:   16.10.2013 07:37
> > Subject:Re: Regarding Solr Cloud issue...
> >
> >
> >
> > I'm sorry I am not able to reproduce this issue.
> >
> > I started 5 solr-4.4 instances.
> > I copied example directory into example1, example2, example3 and
> example4
> > cd example; java -Dbootstrap_confdir=./solr/collection1/conf
> > -Dcollection.configName=myconf -DzkRun -DnumShards=1 -jar start.jar
> > cd example1; java -Djetty.port=7574 -DzkHost=localhost:9983 -jar
> start.jar
> > cd example2; java -Djetty.port=7575 -DzkHost=localhost:9983 -jar
> start.jar
> > cd example3; java -Djetty.port=7576 -DzkHost=localhost:9983 -jar
> start.jar
> > cd example4; java -Djetty.port=7577 -DzkHost=localhost:9983 -jar
> start.jar
> >
> > After that I invoked:
> >
> >
>
> http://localhost:8983/solr/admin/collections?action=CREATE&name=mycollection51&numShards=5&replicationFactor=1
>
> >
> >
> > I can see all shards having non-null ranges in clusterstate.
> >
> >
> > On Tue, Oct 15, 2013 at 8:47 PM, Chris  wrote:
> >
> > > Hi Shalin,.
> > >
> > > Thank you for your quick reply. I appreciate all the help.
> > >
> > > I started the solr cloud servers first...with 5 nodes.
> > >
> > > then i issued a command like below to create the shards -
> > >
> > >
> > >
> >
> >
>
> http://localhost:8983/solr/admin/collections?action=CREATE&name=mycollection&numShards=5&replicationFactor=1
>
> >
> > > <
> > >
> >
> >
>
> http://localhost:8983/solr/admin/collections?action=CREATE&name=mycollection&numShards=3&replicationFactor=4
>
> >
> > > >
> >

Re: Regarding Solr Cloud issue...

[primoz . skale]

If I am not mistaken the only way to create a new shard from a collection 
in 4.4.0 was to use cores API. That worked fine for me until I used 
*other* cores API commands. Those usually produced null ranges. 

In 4.5.0 this is fixed with newly added commands "createshard" etc. to the 
collections API, right?

Primoz



From:   Shalin Shekhar Mangar 
To: solr-user@lucene.apache.org
Date:   16.10.2013 09:06
Subject:    Re: Regarding Solr Cloud issue...



Chris, can you post your complete clusterstate.json? Do all shards have a
null range? Also, did you issue any core admin CREATE commands apart from
the create collection api.

Primoz, I was able to reproduce this but by doing an illegal operation.
Suppose I create a collection with numShards=5 and then I issue a core
admin create command such as:
http://localhost:8983/solr/admin/cores?action=CREATE&name=xyz&collection=mycollection51&shard=shard6


Then a "shard6" is added to the collection with a null range. This is a 
bug
because we should never allow such a core admin create to succeed anyway.
I'll open an issue.



On Wed, Oct 16, 2013 at 11:49 AM,  wrote:

> I sometimes also do get null ranges when doing colletions/cores API
> actions CREATE or/and UNLOAD, etc... In 4.4.0 that was not easily fixed
> because zkCli had problems with "putfile" command, but in 4.5.0 it works
> OK. All you have to do is "download" clusterstate.json from ZK ("get
> /clusterstate.json"), fix ranges to appropriate values and upload the 
file
> back to ZK with zkCli.
>
> But why those null ranges happen at all is beyond me :)
>
> Primoz
>
>
>
> From:   Shalin Shekhar Mangar 
> To: solr-user@lucene.apache.org
> Date:   16.10.2013 07:37
> Subject:Re: Regarding Solr Cloud issue...
>
>
>
> I'm sorry I am not able to reproduce this issue.
>
> I started 5 solr-4.4 instances.
> I copied example directory into example1, example2, example3 and 
example4
> cd example; java -Dbootstrap_confdir=./solr/collection1/conf
> -Dcollection.configName=myconf -DzkRun -DnumShards=1 -jar start.jar
> cd example1; java -Djetty.port=7574 -DzkHost=localhost:9983 -jar 
start.jar
> cd example2; java -Djetty.port=7575 -DzkHost=localhost:9983 -jar 
start.jar
> cd example3; java -Djetty.port=7576 -DzkHost=localhost:9983 -jar 
start.jar
> cd example4; java -Djetty.port=7577 -DzkHost=localhost:9983 -jar 
start.jar
>
> After that I invoked:
>
> 
http://localhost:8983/solr/admin/collections?action=CREATE&name=mycollection51&numShards=5&replicationFactor=1

>
>
> I can see all shards having non-null ranges in clusterstate.
>
>
> On Tue, Oct 15, 2013 at 8:47 PM, Chris  wrote:
>
> > Hi Shalin,.
> >
> > Thank you for your quick reply. I appreciate all the help.
> >
> > I started the solr cloud servers first...with 5 nodes.
> >
> > then i issued a command like below to create the shards -
> >
> >
> >
>
> 
http://localhost:8983/solr/admin/collections?action=CREATE&name=mycollection&numShards=5&replicationFactor=1

>
> > <
> >
>
> 
http://localhost:8983/solr/admin/collections?action=CREATE&name=mycollection&numShards=3&replicationFactor=4

>
> > >
> >
> > Please advice.
> >
> > Regards,
> > Chris
> >
> >
> > On Tue, Oct 15, 2013 at 8:07 PM, Shalin Shekhar Mangar <
> > shalinman...@gmail.com> wrote:
> >
> > > How did you create these shards? Can you tell us how to reproduce 
the
> > > issue?
> > >
> > > Any shard in a collection with compositeId router should never have
> null
> > > ranges.
> > >
> > >
> > > On Tue, Oct 15, 2013 at 7:07 PM, Chris  wrote:
> > >
> > > > Hi,
> > > >
> > > > I am using solr 4.4 as cloud. while creating shards i see that the
> last
> > > > shard has range of "null". i am not sure if this is a bug.
> > > >
> > > > I am stuck with having null value for the range in 
clusterstate.json
> > > > (attached below)
> > > >
> > > > "shard5":{ "range":null, "state":"active",
> "replicas":{"core_node1":{
> > > > "state":"active", "core":"Web_shard5_replica1",
> > > > "node_name":"domain-name.com:1981_solr", "base_url":"
> > > > http://domain-name.com:1981/solr";, "leader":"true",
> > > > "router":"compositeId"},
> > > >
> > > > I tried to use zookeeper cli to change this, but it was not able 
to.
> I
> > > > tried to locate this file, but didn't find it anywhere.
> > > >
> > > > Can you please let me know how do i change the range from null to
> > > something
> > > > meaningful? i have the range that i need, so if i can find the 
file,
> > > maybe
> > > > i can change it manually.
> > > >
> > > > My next question is - can we have a catch all for ranges, i mean 
if
> > > things
> > > > don't match any other range then insert in this shard..is this
> > possible?
> > > >
> > > > Kindly advice.
> > > > Chris
> > > >
> > >
> > >
> > >
> > > --
> > > Regards,
> > > Shalin Shekhar Mangar.
> > >
> >
>
>
>
> --
> Regards,
> Shalin Shekhar Mangar.
>
>


-- 
Regards,
Shalin Shekhar Mangar.

Re: Regarding Solr Cloud issue...

[Shalin Shekhar Mangar]

Chris, can you post your complete clusterstate.json? Do all shards have a
null range? Also, did you issue any core admin CREATE commands apart from
the create collection api.

Primoz, I was able to reproduce this but by doing an illegal operation.
Suppose I create a collection with numShards=5 and then I issue a core
admin create command such as:
http://localhost:8983/solr/admin/cores?action=CREATE&name=xyz&collection=mycollection51&shard=shard6

Then a "shard6" is added to the collection with a null range. This is a bug
because we should never allow such a core admin create to succeed anyway.
I'll open an issue.



On Wed, Oct 16, 2013 at 11:49 AM,  wrote:

> I sometimes also do get null ranges when doing colletions/cores API
> actions CREATE or/and UNLOAD, etc... In 4.4.0 that was not easily fixed
> because zkCli had problems with "putfile" command, but in 4.5.0 it works
> OK. All you have to do is "download" clusterstate.json from ZK ("get
> /clusterstate.json"), fix ranges to appropriate values and upload the file
> back to ZK with zkCli.
>
> But why those null ranges happen at all is beyond me :)
>
> Primoz
>
>
>
> From:   Shalin Shekhar Mangar 
> To: solr-user@lucene.apache.org
> Date:   16.10.2013 07:37
> Subject:Re: Regarding Solr Cloud issue...
>
>
>
> I'm sorry I am not able to reproduce this issue.
>
> I started 5 solr-4.4 instances.
> I copied example directory into example1, example2, example3 and example4
> cd example; java -Dbootstrap_confdir=./solr/collection1/conf
> -Dcollection.configName=myconf -DzkRun -DnumShards=1 -jar start.jar
> cd example1; java -Djetty.port=7574 -DzkHost=localhost:9983 -jar start.jar
> cd example2; java -Djetty.port=7575 -DzkHost=localhost:9983 -jar start.jar
> cd example3; java -Djetty.port=7576 -DzkHost=localhost:9983 -jar start.jar
> cd example4; java -Djetty.port=7577 -DzkHost=localhost:9983 -jar start.jar
>
> After that I invoked:
>
> http://localhost:8983/solr/admin/collections?action=CREATE&name=mycollection51&numShards=5&replicationFactor=1
>
>
> I can see all shards having non-null ranges in clusterstate.
>
>
> On Tue, Oct 15, 2013 at 8:47 PM, Chris  wrote:
>
> > Hi Shalin,.
> >
> > Thank you for your quick reply. I appreciate all the help.
> >
> > I started the solr cloud servers first...with 5 nodes.
> >
> > then i issued a command like below to create the shards -
> >
> >
> >
>
> http://localhost:8983/solr/admin/collections?action=CREATE&name=mycollection&numShards=5&replicationFactor=1
>
> > <
> >
>
> http://localhost:8983/solr/admin/collections?action=CREATE&name=mycollection&numShards=3&replicationFactor=4
>
> > >
> >
> > Please advice.
> >
> > Regards,
> > Chris
> >
> >
> > On Tue, Oct 15, 2013 at 8:07 PM, Shalin Shekhar Mangar <
> > shalinman...@gmail.com> wrote:
> >
> > > How did you create these shards? Can you tell us how to reproduce the
> > > issue?
> > >
> > > Any shard in a collection with compositeId router should never have
> null
> > > ranges.
> > >
> > >
> > > On Tue, Oct 15, 2013 at 7:07 PM, Chris  wrote:
> > >
> > > > Hi,
> > > >
> > > > I am using solr 4.4 as cloud. while creating shards i see that the
> last
> > > > shard has range of "null". i am not sure if this is a bug.
> > > >
> > > > I am stuck with having null value for the range in clusterstate.json
> > > > (attached below)
> > > >
> > > > "shard5":{ "range":null, "state":"active",
> "replicas":{"core_node1":{
> > > > "state":"active", "core":"Web_shard5_replica1",
> > > > "node_name":"domain-name.com:1981_solr", "base_url":"
> > > > http://domain-name.com:1981/solr";, "leader":"true",
> > > > "router":"compositeId"},
> > > >
> > > > I tried to use zookeeper cli to change this, but it was not able to.
> I
> > > > tried to locate this file, but didn't find it anywhere.
> > > >
> > > > Can you please let me know how do i change the range from null to
> > > something
> > > > meaningful? i have the range that i need, so if i can find the file,
> > > maybe
> > > > i can change it manually.
> > > >
> > > > My next question is - can we have a catch all for ranges, i mean if
> > > things
> > > > don't match any other range then insert in this shard..is this
> > possible?
> > > >
> > > > Kindly advice.
> > > > Chris
> > > >
> > >
> > >
> > >
> > > --
> > > Regards,
> > > Shalin Shekhar Mangar.
> > >
> >
>
>
>
> --
> Regards,
> Shalin Shekhar Mangar.
>
>


-- 
Regards,
Shalin Shekhar Mangar.

Re: Regarding Solr Cloud issue...

[primoz . skale]

I sometimes also do get null ranges when doing colletions/cores API 
actions CREATE or/and UNLOAD, etc... In 4.4.0 that was not easily fixed 
because zkCli had problems with "putfile" command, but in 4.5.0 it works 
OK. All you have to do is "download" clusterstate.json from ZK ("get 
/clusterstate.json"), fix ranges to appropriate values and upload the file 
back to ZK with zkCli. 

But why those null ranges happen at all is beyond me :)

Primoz



From:   Shalin Shekhar Mangar 
To: solr-user@lucene.apache.org
Date:   16.10.2013 07:37
Subject:    Re: Regarding Solr Cloud issue...



I'm sorry I am not able to reproduce this issue.

I started 5 solr-4.4 instances.
I copied example directory into example1, example2, example3 and example4
cd example; java -Dbootstrap_confdir=./solr/collection1/conf
-Dcollection.configName=myconf -DzkRun -DnumShards=1 -jar start.jar
cd example1; java -Djetty.port=7574 -DzkHost=localhost:9983 -jar start.jar
cd example2; java -Djetty.port=7575 -DzkHost=localhost:9983 -jar start.jar
cd example3; java -Djetty.port=7576 -DzkHost=localhost:9983 -jar start.jar
cd example4; java -Djetty.port=7577 -DzkHost=localhost:9983 -jar start.jar

After that I invoked:
http://localhost:8983/solr/admin/collections?action=CREATE&name=mycollection51&numShards=5&replicationFactor=1


I can see all shards having non-null ranges in clusterstate.


On Tue, Oct 15, 2013 at 8:47 PM, Chris  wrote:

> Hi Shalin,.
>
> Thank you for your quick reply. I appreciate all the help.
>
> I started the solr cloud servers first...with 5 nodes.
>
> then i issued a command like below to create the shards -
>
>
> 
http://localhost:8983/solr/admin/collections?action=CREATE&name=mycollection&numShards=5&replicationFactor=1

> <
> 
http://localhost:8983/solr/admin/collections?action=CREATE&name=mycollection&numShards=3&replicationFactor=4

> >
>
> Please advice.
>
> Regards,
> Chris
>
>
> On Tue, Oct 15, 2013 at 8:07 PM, Shalin Shekhar Mangar <
> shalinman...@gmail.com> wrote:
>
> > How did you create these shards? Can you tell us how to reproduce the
> > issue?
> >
> > Any shard in a collection with compositeId router should never have 
null
> > ranges.
> >
> >
> > On Tue, Oct 15, 2013 at 7:07 PM, Chris  wrote:
> >
> > > Hi,
> > >
> > > I am using solr 4.4 as cloud. while creating shards i see that the 
last
> > > shard has range of "null". i am not sure if this is a bug.
> > >
> > > I am stuck with having null value for the range in clusterstate.json
> > > (attached below)
> > >
> > > "shard5":{ "range":null, "state":"active", 
"replicas":{"core_node1":{
> > > "state":"active", "core":"Web_shard5_replica1",
> > > "node_name":"domain-name.com:1981_solr", "base_url":"
> > > http://domain-name.com:1981/solr";, "leader":"true",
> > > "router":"compositeId"},
> > >
> > > I tried to use zookeeper cli to change this, but it was not able to. 
I
> > > tried to locate this file, but didn't find it anywhere.
> > >
> > > Can you please let me know how do i change the range from null to
> > something
> > > meaningful? i have the range that i need, so if i can find the file,
> > maybe
> > > i can change it manually.
> > >
> > > My next question is - can we have a catch all for ranges, i mean if
> > things
> > > don't match any other range then insert in this shard..is this
> possible?
> > >
> > > Kindly advice.
> > > Chris
> > >
> >
> >
> >
> > --
> > Regards,
> > Shalin Shekhar Mangar.
> >
>



-- 
Regards,
Shalin Shekhar Mangar.

Re: Regarding Solr Cloud issue...

[Shalin Shekhar Mangar]

I'm sorry I am not able to reproduce this issue.

I started 5 solr-4.4 instances.
I copied example directory into example1, example2, example3 and example4
cd example; java -Dbootstrap_confdir=./solr/collection1/conf
-Dcollection.configName=myconf -DzkRun -DnumShards=1 -jar start.jar
cd example1; java -Djetty.port=7574 -DzkHost=localhost:9983 -jar start.jar
cd example2; java -Djetty.port=7575 -DzkHost=localhost:9983 -jar start.jar
cd example3; java -Djetty.port=7576 -DzkHost=localhost:9983 -jar start.jar
cd example4; java -Djetty.port=7577 -DzkHost=localhost:9983 -jar start.jar

After that I invoked:
http://localhost:8983/solr/admin/collections?action=CREATE&name=mycollection51&numShards=5&replicationFactor=1

I can see all shards having non-null ranges in clusterstate.


On Tue, Oct 15, 2013 at 8:47 PM, Chris  wrote:

> Hi Shalin,.
>
> Thank you for your quick reply. I appreciate all the help.
>
> I started the solr cloud servers first...with 5 nodes.
>
> then i issued a command like below to create the shards -
>
>
> http://localhost:8983/solr/admin/collections?action=CREATE&name=mycollection&numShards=5&replicationFactor=1
> <
> http://localhost:8983/solr/admin/collections?action=CREATE&name=mycollection&numShards=3&replicationFactor=4
> >
>
> Please advice.
>
> Regards,
> Chris
>
>
> On Tue, Oct 15, 2013 at 8:07 PM, Shalin Shekhar Mangar <
> shalinman...@gmail.com> wrote:
>
> > How did you create these shards? Can you tell us how to reproduce the
> > issue?
> >
> > Any shard in a collection with compositeId router should never have null
> > ranges.
> >
> >
> > On Tue, Oct 15, 2013 at 7:07 PM, Chris  wrote:
> >
> > > Hi,
> > >
> > > I am using solr 4.4 as cloud. while creating shards i see that the last
> > > shard has range of "null". i am not sure if this is a bug.
> > >
> > > I am stuck with having null value for the range in clusterstate.json
> > > (attached below)
> > >
> > > "shard5":{ "range":null, "state":"active", "replicas":{"core_node1":{
> > > "state":"active", "core":"Web_shard5_replica1",
> > > "node_name":"domain-name.com:1981_solr", "base_url":"
> > > http://domain-name.com:1981/solr";, "leader":"true",
> > > "router":"compositeId"},
> > >
> > > I tried to use zookeeper cli to change this, but it was not able to. I
> > > tried to locate this file, but didn't find it anywhere.
> > >
> > > Can you please let me know how do i change the range from null to
> > something
> > > meaningful? i have the range that i need, so if i can find the file,
> > maybe
> > > i can change it manually.
> > >
> > > My next question is - can we have a catch all for ranges, i mean if
> > things
> > > don't match any other range then insert in this shard..is this
> possible?
> > >
> > > Kindly advice.
> > > Chris
> > >
> >
> >
> >
> > --
> > Regards,
> > Shalin Shekhar Mangar.
> >
>



-- 
Regards,
Shalin Shekhar Mangar.

Re: Regarding Solr Cloud issue...

[Chris]

Hi Shalin,.

Thank you for your quick reply. I appreciate all the help.

I started the solr cloud servers first...with 5 nodes.

then i issued a command like below to create the shards -

http://localhost:8983/solr/admin/collections?action=CREATE&name=mycollection&numShards=5&replicationFactor=1

Please advice.

Regards,
Chris


On Tue, Oct 15, 2013 at 8:07 PM, Shalin Shekhar Mangar <
shalinman...@gmail.com> wrote:

> How did you create these shards? Can you tell us how to reproduce the
> issue?
>
> Any shard in a collection with compositeId router should never have null
> ranges.
>
>
> On Tue, Oct 15, 2013 at 7:07 PM, Chris  wrote:
>
> > Hi,
> >
> > I am using solr 4.4 as cloud. while creating shards i see that the last
> > shard has range of "null". i am not sure if this is a bug.
> >
> > I am stuck with having null value for the range in clusterstate.json
> > (attached below)
> >
> > "shard5":{ "range":null, "state":"active", "replicas":{"core_node1":{
> > "state":"active", "core":"Web_shard5_replica1",
> > "node_name":"domain-name.com:1981_solr", "base_url":"
> > http://domain-name.com:1981/solr";, "leader":"true",
> > "router":"compositeId"},
> >
> > I tried to use zookeeper cli to change this, but it was not able to. I
> > tried to locate this file, but didn't find it anywhere.
> >
> > Can you please let me know how do i change the range from null to
> something
> > meaningful? i have the range that i need, so if i can find the file,
> maybe
> > i can change it manually.
> >
> > My next question is - can we have a catch all for ranges, i mean if
> things
> > don't match any other range then insert in this shard..is this possible?
> >
> > Kindly advice.
> > Chris
> >
>
>
>
> --
> Regards,
> Shalin Shekhar Mangar.
>

Re: Regarding Solr Cloud issue...

[Shalin Shekhar Mangar]

How did you create these shards? Can you tell us how to reproduce the issue?

Any shard in a collection with compositeId router should never have null
ranges.


On Tue, Oct 15, 2013 at 7:07 PM, Chris  wrote:

> Hi,
>
> I am using solr 4.4 as cloud. while creating shards i see that the last
> shard has range of "null". i am not sure if this is a bug.
>
> I am stuck with having null value for the range in clusterstate.json
> (attached below)
>
> "shard5":{ "range":null, "state":"active", "replicas":{"core_node1":{
> "state":"active", "core":"Web_shard5_replica1",
> "node_name":"domain-name.com:1981_solr", "base_url":"
> http://domain-name.com:1981/solr";, "leader":"true",
> "router":"compositeId"},
>
> I tried to use zookeeper cli to change this, but it was not able to. I
> tried to locate this file, but didn't find it anywhere.
>
> Can you please let me know how do i change the range from null to something
> meaningful? i have the range that i need, so if i can find the file, maybe
> i can change it manually.
>
> My next question is - can we have a catch all for ranges, i mean if things
> don't match any other range then insert in this shard..is this possible?
>
> Kindly advice.
> Chris
>



-- 
Regards,
Shalin Shekhar Mangar.

Regarding Solr Cloud issue...

[Chris]

Hi,

I am using solr 4.4 as cloud. while creating shards i see that the last
shard has range of "null". i am not sure if this is a bug.

I am stuck with having null value for the range in clusterstate.json
(attached below)

"shard5":{ "range":null, "state":"active", "replicas":{"core_node1":{
"state":"active", "core":"Web_shard5_replica1",
"node_name":"domain-name.com:1981_solr", "base_url":"
http://domain-name.com:1981/solr";, "leader":"true",
"router":"compositeId"},

I tried to use zookeeper cli to change this, but it was not able to. I
tried to locate this file, but didn't find it anywhere.

Can you please let me know how do i change the range from null to something
meaningful? i have the range that i need, so if i can find the file, maybe
i can change it manually.

My next question is - can we have a catch all for ranges, i mean if things
don't match any other range then insert in this shard..is this possible?

Kindly advice.
Chris

Regarding Solr Cloud issue...

[Chris]

Hi,

I am using solr 4.4 as cloud. while creating shards i see that the last
shard has range of "null". i am not sure if this is a bug.

I am stuck with having null value for the range in clusterstate.json
(attached below)

"shard5":{ "range":null, "state":"active", "replicas":{"core_node1":{
"state":"active", "core":"Web_shard5_replica1",
"node_name":"domain-name.com:1981_solr", "base_url":"
http://domain-name.com:1981/solr";, "leader":"true",
"router":"compositeId"},

I tried to use zookeeper cli to change this, but it was not able to. I
tried to locate this file, but didn't find it anywhere.

Can you please let me know how do i change the range from null to something
meaningful? i have the range that i need, so if i can find the file, maybe
i can change it manually.

My next question is - can we have a catch all for ranges, i mean if things
don't match any other range then insert in this shard..is this possible?

Kindly advice.

Chris