Re: Deployment

2019-01-12 Thread amit sehas
Thanks for your response, i am understanding that the application will typically send the queries to coordinator nodes,if that coordinator does not respond within a certain time frame then the application will probably resend the query to a different coordinator node, under the assumption that

removing already joining node

2019-01-12 Thread Osman YOZGATLIOĞLU
Hello, I have one joining node. I decided to change cluster topology and I need to move this node to another cluster. How can I decommission joining node? I can't find exact case at google. Regards, Osman

Re: Deployment

2019-01-12 Thread Andy Tolbert
Hi Amit, a) If queries are submitted to co-ordinator nodes (i assume this includes > writes as well as reads) then: > -- is this the approach also followed for the initial data load? > Writes get sent to all replica nodes, and then the coordinator responds to the client as soon as enough

Re: Deployment

2019-01-12 Thread amit sehas
Thanks for your response, this leads to some further questions: a) If queries are submitted to co-ordinator nodes (i assume this includes writes as well as reads) then:  -- is this the approach also followed for the initial data load?   -- some select queries may not have restrictions on all

Re: Deployment

2019-01-12 Thread Rajesh Kishore
Application would send request to one of the node(called as coordinating node) & this coordinating node is aware of where your result lies(considering you have modelled your DB correctly, it should not result in scatter& gather kind of stuff) and thus delegate the query to respective node, so it