[jira] [Commented] (SOLR-6762) bin/solr create_collection not working due to not finding configName but the configSet exists
[
https://issues.apache.org/jira/browse/SOLR-6762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14218144#comment-14218144
]
ASF subversion and git services commented on SOLR-6762:
---
Commit 1640598 from [~thelabdude] in branch 'dev/trunk'
[ https://svn.apache.org/r1640598 ]
SOLR-6762: use collection.configName parameter instead of configSet when
creating a collection
bin/solr create_collection not working due to not finding configName but the
configSet exists
-
Key: SOLR-6762
URL: https://issues.apache.org/jira/browse/SOLR-6762
Project: Solr
Issue Type: Bug
Reporter: Timothy Potter
Assignee: Timothy Potter
On trunk, when doing:
bin/solr create_collection -n foo2 -c sample_techproducts_configs
The collection cannot be created because of:
Connecting to ZooKeeper at localhost:9983
Uploading
/Users/timpotter/dev/lw/projects/solr_trunk_co/solr/server/solr/configsets/sample_techproducts_configs/conf
for config sample_techproducts_configs to ZooKeeper at localhost:9983
Creating new collection 'foo2' using command:
http://192.168.1.2:7574/solr/admin/collections?action=CREATEname=foo2numShards=1replicationFactor=1maxShardsPerNode=1configSet=sample_techproducts_configs
{
responseHeader:{
status:0,
QTime:16121},
failure:{:org.apache.solr.client.solrj.impl.HttpSolrServer$RemoteSolrException:Error
CREATEing SolrCore 'foo2_shard1_replica1': Unable to create core
[foo2_shard1_replica1] Caused by: Could not find configName for collection
foo2 found:[data_driven_schema_configs, sample_techproducts_configs]}}
The bin/solr create_collection command uploads the
sample_techproducts_configs configset but the create collection seems to
require the configName instead.
Logs:
INFO - 2014-11-19 16:14:38.001;
org.apache.solr.cloud.OverseerCollectionProcessor; Overseer Collection
Processor: Get the message id:/overseer/collection-queue-work/qn-14
message:{
operation:create,
fromApi:true,
name:foo2,
replicationFactor:1,
numShards:1,
maxShardsPerNode:1}
WARN - 2014-11-19 16:14:38.002;
org.apache.solr.cloud.OverseerCollectionProcessor;
OverseerCollectionProcessor.processMessage : create , {
operation:create,
fromApi:true,
name:foo2,
replicationFactor:1,
numShards:1,
maxShardsPerNode:1}
WARN - 2014-11-19 16:14:38.002;
org.apache.solr.cloud.OverseerCollectionProcessor; Could not obtain config
name
INFO - 2014-11-19 16:14:38.003;
org.apache.solr.cloud.DistributedQueue$LatchWatcher; NodeChildrenChanged
fired on path /overseer/queue state SyncConnected
INFO - 2014-11-19 16:14:38.004;
org.apache.solr.cloud.Overseer$ClusterStateUpdater; building a new
collection: foo2
INFO - 2014-11-19 16:14:38.004;
org.apache.solr.cloud.Overseer$ClusterStateUpdater; Create collection foo2
with shards [shard1]
INFO - 2014-11-19 16:14:38.004;
org.apache.solr.cloud.Overseer$ClusterStateUpdater; state version foo2 1
INFO - 2014-11-19 16:14:38.006;
org.apache.solr.common.cloud.ZkStateReader$2; A cluster state change:
WatchedEvent state:SyncConnected type:NodeDataChanged
path:/clusterstate.json, has occurred - updating... (live nodes size: 2)
INFO - 2014-11-19 16:14:38.103;
org.apache.solr.cloud.OverseerCollectionProcessor; Creating SolrCores for new
collection foo2, shardNames [shard1] , replicationFactor : 1
INFO - 2014-11-19 16:14:38.103;
org.apache.solr.cloud.OverseerCollectionProcessor; Creating shard
foo2_shard1_replica1 as part of slice shard1 of collection foo2 on
192.168.1.2:8983_solr
INFO - 2014-11-19 16:14:38.106;
org.apache.solr.handler.admin.CoreAdminHandler; core create command
numShards=1shard=shard1name=foo2_shard1_replica1action=CREATEcollection=foo2wt=javabinqt=/admin/coresversion=2
INFO - 2014-11-19 16:14:38.107; org.apache.solr.cloud.ZkController;
publishing core=foo2_shard1_replica1 state=down collection=foo2
INFO - 2014-11-19 16:14:38.108; org.apache.solr.cloud.ZkController; look for
our core node name
INFO - 2014-11-19 16:14:38.108;
org.apache.solr.cloud.DistributedQueue$LatchWatcher; NodeChildrenChanged
fired on path /overseer/queue state SyncConnected
INFO - 2014-11-19 16:14:38.109;
org.apache.solr.cloud.Overseer$ClusterStateUpdater; Update state numShards=1
message={
operation:state,
numShards:1,
shard:shard1,
roles:null,
state:down,
core:foo2_shard1_replica1,
collection:foo2,
node_name:192.168.1.2:8983_solr,
base_url:http://192.168.1.2:8983/solr}
INFO - 2014-11-19 16:14:38.211;
org.apache.solr.common.cloud.ZkStateReader$2; A cluster state change:
WatchedEvent state:SyncConnected type:NodeDataChanged
path:/clusterstate.json, has occurred - updating...
[jira] [Commented] (SOLR-6762) bin/solr create_collection not working due to not finding configName but the configSet exists
[
https://issues.apache.org/jira/browse/SOLR-6762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14218158#comment-14218158
]
ASF subversion and git services commented on SOLR-6762:
---
Commit 1640600 from [~thelabdude] in branch 'dev/branches/branch_5x'
[ https://svn.apache.org/r1640600 ]
SOLR-6762: use collection.configName parameter instead of configSet when
creating a collection
bin/solr create_collection not working due to not finding configName but the
configSet exists
-
Key: SOLR-6762
URL: https://issues.apache.org/jira/browse/SOLR-6762
Project: Solr
Issue Type: Bug
Reporter: Timothy Potter
Assignee: Timothy Potter
Fix For: 5.0
On trunk, when doing:
bin/solr create_collection -n foo2 -c sample_techproducts_configs
The collection cannot be created because of:
Connecting to ZooKeeper at localhost:9983
Uploading
/Users/timpotter/dev/lw/projects/solr_trunk_co/solr/server/solr/configsets/sample_techproducts_configs/conf
for config sample_techproducts_configs to ZooKeeper at localhost:9983
Creating new collection 'foo2' using command:
http://192.168.1.2:7574/solr/admin/collections?action=CREATEname=foo2numShards=1replicationFactor=1maxShardsPerNode=1configSet=sample_techproducts_configs
{
responseHeader:{
status:0,
QTime:16121},
failure:{:org.apache.solr.client.solrj.impl.HttpSolrServer$RemoteSolrException:Error
CREATEing SolrCore 'foo2_shard1_replica1': Unable to create core
[foo2_shard1_replica1] Caused by: Could not find configName for collection
foo2 found:[data_driven_schema_configs, sample_techproducts_configs]}}
The bin/solr create_collection command uploads the
sample_techproducts_configs configset but the create collection seems to
require the configName instead.
Logs:
INFO - 2014-11-19 16:14:38.001;
org.apache.solr.cloud.OverseerCollectionProcessor; Overseer Collection
Processor: Get the message id:/overseer/collection-queue-work/qn-14
message:{
operation:create,
fromApi:true,
name:foo2,
replicationFactor:1,
numShards:1,
maxShardsPerNode:1}
WARN - 2014-11-19 16:14:38.002;
org.apache.solr.cloud.OverseerCollectionProcessor;
OverseerCollectionProcessor.processMessage : create , {
operation:create,
fromApi:true,
name:foo2,
replicationFactor:1,
numShards:1,
maxShardsPerNode:1}
WARN - 2014-11-19 16:14:38.002;
org.apache.solr.cloud.OverseerCollectionProcessor; Could not obtain config
name
INFO - 2014-11-19 16:14:38.003;
org.apache.solr.cloud.DistributedQueue$LatchWatcher; NodeChildrenChanged
fired on path /overseer/queue state SyncConnected
INFO - 2014-11-19 16:14:38.004;
org.apache.solr.cloud.Overseer$ClusterStateUpdater; building a new
collection: foo2
INFO - 2014-11-19 16:14:38.004;
org.apache.solr.cloud.Overseer$ClusterStateUpdater; Create collection foo2
with shards [shard1]
INFO - 2014-11-19 16:14:38.004;
org.apache.solr.cloud.Overseer$ClusterStateUpdater; state version foo2 1
INFO - 2014-11-19 16:14:38.006;
org.apache.solr.common.cloud.ZkStateReader$2; A cluster state change:
WatchedEvent state:SyncConnected type:NodeDataChanged
path:/clusterstate.json, has occurred - updating... (live nodes size: 2)
INFO - 2014-11-19 16:14:38.103;
org.apache.solr.cloud.OverseerCollectionProcessor; Creating SolrCores for new
collection foo2, shardNames [shard1] , replicationFactor : 1
INFO - 2014-11-19 16:14:38.103;
org.apache.solr.cloud.OverseerCollectionProcessor; Creating shard
foo2_shard1_replica1 as part of slice shard1 of collection foo2 on
192.168.1.2:8983_solr
INFO - 2014-11-19 16:14:38.106;
org.apache.solr.handler.admin.CoreAdminHandler; core create command
numShards=1shard=shard1name=foo2_shard1_replica1action=CREATEcollection=foo2wt=javabinqt=/admin/coresversion=2
INFO - 2014-11-19 16:14:38.107; org.apache.solr.cloud.ZkController;
publishing core=foo2_shard1_replica1 state=down collection=foo2
INFO - 2014-11-19 16:14:38.108; org.apache.solr.cloud.ZkController; look for
our core node name
INFO - 2014-11-19 16:14:38.108;
org.apache.solr.cloud.DistributedQueue$LatchWatcher; NodeChildrenChanged
fired on path /overseer/queue state SyncConnected
INFO - 2014-11-19 16:14:38.109;
org.apache.solr.cloud.Overseer$ClusterStateUpdater; Update state numShards=1
message={
operation:state,
numShards:1,
shard:shard1,
roles:null,
state:down,
core:foo2_shard1_replica1,
collection:foo2,
node_name:192.168.1.2:8983_solr,
base_url:http://192.168.1.2:8983/solr}
INFO - 2014-11-19 16:14:38.211;
org.apache.solr.common.cloud.ZkStateReader$2; A cluster state change:
WatchedEvent state:SyncConnected type:NodeDataChanged
