Re: solr4.1 createNodeSet requires ip addresses?
Hi, I created a ticket and try to describe here https://issues.apache.org/jira/browse/SOLR-4471 Actually search speed, ram and memory usage on solr 4.x compared with 3.6. looks good, only the network is blocked by full copy index from slave. André On 16.02.13 03:25, Mark Miller markrmil...@gmail.com wrote: For 4.2, I'll try and put in https://issues.apache.org/jira/browse/SOLR-4078 soon. Not sure about the behavior your seeing - you might want to file a JIRA issue. - Mark On Feb 15, 2013, at 8:17 PM, Gary Yngve gary.yn...@gmail.com wrote: Hi all, I've been unable to get the collections create API to work with createNodeSet containing hostnames, both localhost and external hostnames. I've only been able to get it working when using explicit IP addresses. It looks like zk stores the IP addresses in the clusterstate.json and live_nodes. Is it possible that Solr Cloud is not doing any hostname resolving but just looking for an explicit match with createNodeSet? This is kind of annoying, in that I am working with EC2 instances and consider it pretty lame to need to use elastic IPs for internal use. I'm hacking around it now (looking up the eth0 inet addr on each machine), but I'm not happy about it. Has anyone else found a better solution? The reason I want to specify explicit nodes for collections is so I can have just one zk ensemble managing collections across different environments that will go up and down independently of each other. Thanks, Gary
solr4.1 createNodeSet requires ip addresses?
Hi all, I've been unable to get the collections create API to work with createNodeSet containing hostnames, both localhost and external hostnames. I've only been able to get it working when using explicit IP addresses. It looks like zk stores the IP addresses in the clusterstate.json and live_nodes. Is it possible that Solr Cloud is not doing any hostname resolving but just looking for an explicit match with createNodeSet? This is kind of annoying, in that I am working with EC2 instances and consider it pretty lame to need to use elastic IPs for internal use. I'm hacking around it now (looking up the eth0 inet addr on each machine), but I'm not happy about it. Has anyone else found a better solution? The reason I want to specify explicit nodes for collections is so I can have just one zk ensemble managing collections across different environments that will go up and down independently of each other. Thanks, Gary
Re: solr4.1 createNodeSet requires ip addresses?
For 4.2, I'll try and put in https://issues.apache.org/jira/browse/SOLR-4078 soon. Not sure about the behavior your seeing - you might want to file a JIRA issue. - Mark On Feb 15, 2013, at 8:17 PM, Gary Yngve gary.yn...@gmail.com wrote: Hi all, I've been unable to get the collections create API to work with createNodeSet containing hostnames, both localhost and external hostnames. I've only been able to get it working when using explicit IP addresses. It looks like zk stores the IP addresses in the clusterstate.json and live_nodes. Is it possible that Solr Cloud is not doing any hostname resolving but just looking for an explicit match with createNodeSet? This is kind of annoying, in that I am working with EC2 instances and consider it pretty lame to need to use elastic IPs for internal use. I'm hacking around it now (looking up the eth0 inet addr on each machine), but I'm not happy about it. Has anyone else found a better solution? The reason I want to specify explicit nodes for collections is so I can have just one zk ensemble managing collections across different environments that will go up and down independently of each other. Thanks, Gary
