数据税务企业+;Solr:无法查询表:范围的碎片不可用
我们最近将现有的Cassandra集群移动到DSE,并尝试创建一个启用solr搜索的新密钥空间 我们遵循了DataStax企业入门指南@ 我们的数据税务企业+;Solr:无法查询表:范围的碎片不可用,solr,datastax-enterprise,Solr,Datastax Enterprise,我们最近将现有的Cassandra集群移动到DSE,并尝试创建一个启用solr搜索的新密钥空间 我们遵循了DataStax企业入门指南@ 我们的nodetool状态如下 Datacenter: nephos-1 ==================== Status=Up/Down |/ State=Normal/Leaving/Joining/Moving -- Address Load Tokens Owns Host ID
nodetool状态如下
Datacenter: nephos-1
====================
Status=Up/Down
|/ State=Normal/Leaving/Joining/Moving
-- Address Load Tokens Owns Host ID Rack
UN 10.129.196.6 578.42 GB 256 21.4% 043a2f6b-af67-433b-82c9-545521840183 r1
UN 10.129.196.21 657.12 GB 256 18.4% 91ef191a-90b3-448e-93fc-b96bc20134b3 r1
UN 10.129.196.4 572.69 GB 256 18.5% 706a78a4-02a0-45b5-91ec-78a1466a5b83 r1
UN 10.129.196.20 633.65 GB 256 23.0% b13c9af9-510b-4c84-994d-e7dd76d70335 r1
UN 10.129.196.5 472.11 GB 256 18.6% ca217361-0390-4eb2-ac09-5303d5f639d0 r1
```
我们的键空间配置如下所示:
CREATE KEYSPACE nhanes_ks3 WITH replication = {
'class': 'NetworkTopologyStrategy',
'nephos-1': '3'
};
java.io.IOException: Unavailable shards for ranges: [(-7387413954048418055,-7385338481486867046], (-7968649137587749694,-7963978319820795254], (1313382724605553296,1319385075089218248], (-518923653484422343,-505515211219774468], (4878421572270955033,4914518257072996455], (-844700479033064369,-776944140537025276], (-69308347594152481,-68921876667069098], (4871809831310454903,4876975265107356578], (3271109328123695599,3274195026207869261], (-8483313673665218401,-8454834139936236432], (-3395613676758459575,-3372444966011531863],
我们得到的具体错误如下:
CREATE KEYSPACE nhanes_ks3 WITH replication = {
'class': 'NetworkTopologyStrategy',
'nephos-1': '3'
};
java.io.IOException: Unavailable shards for ranges: [(-7387413954048418055,-7385338481486867046], (-7968649137587749694,-7963978319820795254], (1313382724605553296,1319385075089218248], (-518923653484422343,-505515211219774468], (4878421572270955033,4914518257072996455], (-844700479033064369,-776944140537025276], (-69308347594152481,-68921876667069098], (4871809831310454903,4876975265107356578], (3271109328123695599,3274195026207869261], (-8483313673665218401,-8454834139936236432], (-3395613676758459575,-3372444966011531863],
根据OpsCenter和up,我们所有的节点都处于活动状态。Killachaos您还看到了吗?如果是这样的话,你能提供dsetool环的输出吗?抱歉,htran,我没有遵循这一点,因为我们决定寻求另一种解决方案。这是我们当前的dse环-dsetool“未知”的工作负载非常麻烦。您在什么时候获得了范围错误的不可用碎片?关于核心创造?询问?我的怀疑是,由于dsetool无法确定该节点是否为搜索节点,因此用于确定要查询数据的节点的ShardLoter也无法正常工作。错误发生在我们尝试设置它时的查询上。但是,当前的节点都是“普通cassandra节点”(不是搜索)。