Re: Core mismatch in org.apache.solr.update.StreamingSolrClients Errors for ConcurrentUpdateSolrClient
okay, to make everything clear, here are the steps: - Creating configs etc and then running: ./zkcli.sh -cmd upconfig -n CoreA -d /path/to/core/configs/CoreA/conf/ -z zk1:2181,zk2:2182,zk3:2183 - Then going to http://someserver:8983/solr/#/~cores - Clicking Add Core: http://lucene.472066.n3.nabble.com/file/n4222345/Screen_Shot_2015-08-11_at_14.png Repateding the last step on other node as well So this is invalid (incl https://wiki.apache.org/solr/CoreAdmin)? - Zeki ama calismiyor... Calissa yapar... -- View this message in context: http://lucene.472066.n3.nabble.com/Core-mismatch-in-org-apache-solr-update-StreamingSolrClients-Errors-for-ConcurrentUpdateSolrClient-tp4222335p4222345.html Sent from the Solr - User mailing list archive at Nabble.com.
Re: Core mismatch in org.apache.solr.update.StreamingSolrClients Errors for ConcurrentUpdateSolrClient
thanks for the details Anshum :) I got one more question, could this kind of error logging might be also triggered by the amount of incoming requests? I can see these errors only on prod env, but testing env is totally fine, although the creation process is exactly the same - Zeki ama calismiyor... Calissa yapar... -- View this message in context: http://lucene.472066.n3.nabble.com/Core-mismatch-in-org-apache-solr-update-StreamingSolrClients-Errors-for-ConcurrentUpdateSolrClient-tp4222335p4222348.html Sent from the Solr - User mailing list archive at Nabble.com.
Re: Core mismatch in org.apache.solr.update.StreamingSolrClients Errors for ConcurrentUpdateSolrClient
How did you create your collections? Also, is that verbatim from the logs or is it just because you obfuscated that part while posting it here? On Mon, Aug 10, 2015 at 11:02 PM, deniz denizdurmu...@gmail.com wrote: Hello Anshum, thanks for the quick reply I know it is being forwarded one node to the leader node, but for collection names, it shows different collections while master node address is correct. Dunno if I am missing some points but my concern is the bold parts below: ERROR - 2015-08-11 05:04:34.592; [*CoreA* shard1 core_node2 *CoreA*] org.apache.solr.update.StreamingSolrClients$1; error org.apache.solr.common.SolrException: Bad Request request: http://server:8983/solr/*CoreB*/update?update.distrib=TOLEADERdistrib.from=http%3A%2F%2Fserver2%3A8983%2Fsolr%2F*CoreB*%2Fwt=javabinversion=2 So this is also normal? Anshum Gupta wrote Hi Deniz, Seems like the update that's being forwarded from a non-leader (original node that received the request) is failing. This could be due to multiple reasons, including issue with your schema vs document that you sent. To elaborate more, here's how a typical batched request in SolrCloud works. 1. Batch sent from client. 2. Received by node X. 3. All documents that have their shard leader on node X, are processed and distributed to the replicas by node X. All other documents which belong to a shard who's leader isn't on Node X, get forwarded using the ConcurrentUpdateSolrClient to their respective leaders. There's nothing *strange* about this log, other than the fact that the update failed (and would have failed even if you would have directly sent the document to this node). Hope this made things clear. -- Anshum Gupta - Zeki ama calismiyor... Calissa yapar... -- View this message in context: http://lucene.472066.n3.nabble.com/Core-mismatch-in-org-apache-solr-update-StreamingSolrClients-Errors-for-ConcurrentUpdateSolrClient-tp4222335p4222338.html Sent from the Solr - User mailing list archive at Nabble.com. -- Anshum Gupta
Re: Core mismatch in org.apache.solr.update.StreamingSolrClients Errors for ConcurrentUpdateSolrClient
Hello Anshum, thanks for the quick reply I know it is being forwarded one node to the leader node, but for collection names, it shows different collections while master node address is correct. Dunno if I am missing some points but my concern is the bold parts below: ERROR - 2015-08-11 05:04:34.592; [*CoreA* shard1 core_node2 *CoreA*] org.apache.solr.update.StreamingSolrClients$1; error org.apache.solr.common.SolrException: Bad Request request: http://server:8983/solr/*CoreB*/update?update.distrib=TOLEADERdistrib.from=http%3A%2F%2Fserver2%3A8983%2Fsolr%2F*CoreB*%2Fwt=javabinversion=2 So this is also normal? Anshum Gupta wrote Hi Deniz, Seems like the update that's being forwarded from a non-leader (original node that received the request) is failing. This could be due to multiple reasons, including issue with your schema vs document that you sent. To elaborate more, here's how a typical batched request in SolrCloud works. 1. Batch sent from client. 2. Received by node X. 3. All documents that have their shard leader on node X, are processed and distributed to the replicas by node X. All other documents which belong to a shard who's leader isn't on Node X, get forwarded using the ConcurrentUpdateSolrClient to their respective leaders. There's nothing *strange* about this log, other than the fact that the update failed (and would have failed even if you would have directly sent the document to this node). Hope this made things clear. -- Anshum Gupta - Zeki ama calismiyor... Calissa yapar... -- View this message in context: http://lucene.472066.n3.nabble.com/Core-mismatch-in-org-apache-solr-update-StreamingSolrClients-Errors-for-ConcurrentUpdateSolrClient-tp4222335p4222338.html Sent from the Solr - User mailing list archive at Nabble.com.
Re: Core mismatch in org.apache.solr.update.StreamingSolrClients Errors for ConcurrentUpdateSolrClient
bq. adding it on admin interface of solr Did you not use Collections Admin API? If you try to create your own cores using the core admin APIs instead of using Collection Admin APIs, you could really end up shooting yourself in your feet. Also, the only supported mechanism to create a collection in Solr is via the Collection APIs. On Mon, Aug 10, 2015 at 11:13 PM, deniz denizdurmu...@gmail.com wrote: I have created by simply creating configs and then using upconfig to upload to zookeeper, then adding it on admin interface of solr. I have only changed the ips of server and server1 and changed the core/collection names to CoreA and CoreB, in the logs CoreA and CoreB are different collections with different names. - Zeki ama calismiyor... Calissa yapar... -- View this message in context: http://lucene.472066.n3.nabble.com/Core-mismatch-in-org-apache-solr-update-StreamingSolrClients-Errors-for-ConcurrentUpdateSolrClient-tp4222335p4222341.html Sent from the Solr - User mailing list archive at Nabble.com. -- Anshum Gupta
Re: Core mismatch in org.apache.solr.update.StreamingSolrClients Errors for ConcurrentUpdateSolrClient
I have created by simply creating configs and then using upconfig to upload to zookeeper, then adding it on admin interface of solr. I have only changed the ips of server and server1 and changed the core/collection names to CoreA and CoreB, in the logs CoreA and CoreB are different collections with different names. - Zeki ama calismiyor... Calissa yapar... -- View this message in context: http://lucene.472066.n3.nabble.com/Core-mismatch-in-org-apache-solr-update-StreamingSolrClients-Errors-for-ConcurrentUpdateSolrClient-tp4222335p4222341.html Sent from the Solr - User mailing list archive at Nabble.com.
Re: Core mismatch in org.apache.solr.update.StreamingSolrClients Errors for ConcurrentUpdateSolrClient
It's not entirely invalid but the only supported mechanism to create collections is via the Collections admin API: https://cwiki.apache.org/confluence/display/solr/Collections+API On Mon, Aug 10, 2015 at 11:53 PM, deniz denizdurmu...@gmail.com wrote: okay, to make everything clear, here are the steps: - Creating configs etc and then running: ./zkcli.sh -cmd upconfig -n CoreA -d /path/to/core/configs/CoreA/conf/ -z zk1:2181,zk2:2182,zk3:2183 - Then going to http://someserver:8983/solr/#/~cores - Clicking Add Core: http://lucene.472066.n3.nabble.com/file/n4222345/Screen_Shot_2015-08-11_at_14.png Repateding the last step on other node as well So this is invalid (incl https://wiki.apache.org/solr/CoreAdmin)? - Zeki ama calismiyor... Calissa yapar... -- View this message in context: http://lucene.472066.n3.nabble.com/Core-mismatch-in-org-apache-solr-update-StreamingSolrClients-Errors-for-ConcurrentUpdateSolrClient-tp4222335p4222345.html Sent from the Solr - User mailing list archive at Nabble.com. -- Anshum Gupta
Re: Core mismatch in org.apache.solr.update.StreamingSolrClients Errors for ConcurrentUpdateSolrClient
Hi Deniz, Seems like the update that's being forwarded from a non-leader (original node that received the request) is failing. This could be due to multiple reasons, including issue with your schema vs document that you sent. To elaborate more, here's how a typical batched request in SolrCloud works. 1. Batch sent from client. 2. Received by node X. 3. All documents that have their shard leader on node X, are processed and distributed to the replicas by node X. All other documents which belong to a shard who's leader isn't on Node X, get forwarded using the ConcurrentUpdateSolrClient to their respective leaders. There's nothing *strange* about this log, other than the fact that the update failed (and would have failed even if you would have directly sent the document to this node). Hope this made things clear. On Mon, Aug 10, 2015 at 10:45 PM, deniz denizdurmu...@gmail.com wrote: I have a simple 2-node(5.1) cloud env with 6 different cores. One of the cores(CoreB) has some update issue which I am aware of, but the error logs on solr, I am seeing these below: ERROR - 2015-08-11 05:04:34.592; [*CoreA shard1 core_node2 CoreA*] org.apache.solr.update.StreamingSolrClients$1; error org.apache.solr.common.SolrException: Bad Request request: * http://server:8983/solr/CoreB*/update?update.distrib=TOLEADERdistrib.from=http%3A%2F%2Fserver2%3A8983%2Fsolr%2FCoreB%2Fwt=javabinversion=2 at org.apache.solr.client.solrj.impl.ConcurrentUpdateSolrClient$Runner.run(ConcurrentUpdateSolrClient.java:241) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) ERROR - 2015-08-11 05:09:30.260; [CoreA shard1 core_node2 CoreA] org.apache.solr.update.StreamingSolrClients$1; error org.apache.solr.common.SolrException: Bad Request request: http://server:8983/solr/CoreB/update?update.distrib=TOLEADERdistrib.from=http%3A%2F%2Fserver2%3A8983%2Fsolr%2FCoreB%2Fwt=javabinversion=2 at org.apache.solr.client.solrj.impl.ConcurrentUpdateSolrClient$Runner.run(ConcurrentUpdateSolrClient.java:241) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) ERROR - 2015-08-11 05:20:49.710; [gaysuser shard1 core_node2 gaysuser] org.apache.solr.update.StreamingSolrClients$1; error org.apache.solr.common.SolrException: Bad Request request: http://server:8983/solr/CoreB/update?update.distrib=TOLEADERdistrib.from=http%3A%2F%2Fserver2%3A8983%2Fsolr%2FCoreB%2Fwt=javabinversion=2 at org.apache.solr.client.solrj.impl.ConcurrentUpdateSolrClient$Runner.run(ConcurrentUpdateSolrClient.java:241) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) ERROR - 2015-08-11 05:23:29.868; [CoreA shard1 core_node2 CoreA] org.apache.solr.update.StreamingSolrClients$1; error org.apache.solr.common.SolrException: Bad Request request: http://server:8983/solr/CoreB/update?update.distrib=TOLEADERdistrib.from=http%3A%2F%2Fserver2%3A8983%2Fsolr%2FCoreB%2Fwt=javabinversion=2 at org.apache.solr.client.solrj.impl.ConcurrentUpdateSolrClient$Runner.run(ConcurrentUpdateSolrClient.java:241) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) is this normal and just an issue with the wrong logging params or there is something wrong with the configs of the cloud - Zeki ama calismiyor... Calissa yapar... -- View this message in context: http://lucene.472066.n3.nabble.com/Core-mismatch-in-org-apache-solr-update-StreamingSolrClients-Errors-for-ConcurrentUpdateSolrClient-tp4222335.html Sent from the Solr - User mailing list archive at Nabble.com. -- Anshum Gupta
