On 11/23/22 11:45, Aravind Reddy Jangam wrote:
I am using Java 11, Zookeeper 3.7.1, Solr 9.0.0
I installed & started three zookeeper instances
I ran below commands to bootstrap & upload configs to zookeeper
cd /opt/install/solr
./server/scripts/cloud-scripts/zkcli.sh -zkhost zk01:2181,zk02:2181,zk03:2181
-cmd makepath /solr-document1
./server/scripts/cloud-scripts/zkcli.sh -zkhost
zk01:2181,zk02:2181,zk03:2181/solr-document1 -cmd bootstrap -solrhome
/opt/solr/data
./server/scripts/cloud-scripts/zkcli.sh -zkhost
zk01:2181,zk02:2181,zk03:2181/solr-document1 -cmd upconfig -confname document1
-confdir /opt/solr/data/collection/document1/conf
./server/scripts/cloud-scripts/zkcli.sh -zkhost
zk01:2181,zk02:2181,zk03:2181/solr-document1 -cmd linkconfig -collection
document1 -confname document1
When i start solr, i get below error
can you please help with how to resolve this issue
same approach worked in solr 6.3.0 & I was able to start solr process
2022-11-23 14:48:32.531 INFO (main) [] o.a.s.c.CorePropertiesLocator Found 1
core definitions underneath /opt/solr/data
2022-11-23 14:48:32.532 INFO (main) [] o.a.s.c.CorePropertiesLocator Cores
are: [document1]
This looks very odd. A core name in cloud mode is usually something
like "collection1_shard1_replica_n1" ... not just "collection1".
If you are trying to bootstrap from standalone mode to cloud mode ...
don't do that. It causes headaches both with operation and trying to
get support. Start in cloud mode and create the collections you need
with the settings you need. If you are creating a collection with only
one shard, then it is possible to shut down the cloud nodes, copy the
data directory from the standalone core to one of the cores in the cloud
nodes, and restart the cloud nodes one by one so the index is seen, and
then properly copied to additional replicas.
But in general, it is always best to reindex from scratch whenever you
make a change. A lot of problems are avoided by doing that.
Thanks,
Shawn
