 <blockquote> <p>I want my data starting with particular ID to be at a predefined node because I know data will be accessed from that node heavily.</p> </blockquote> <p>Looks like that you talk about data locality problem, which is really important in bigdata-like computations (Spark, Hadoop, etc.). But the general approach for that isn't to pin data to specific node, but just to move your whole computation to the data itself.</p> <p>Pinning data to specific node may cause problems like:</p> <ul> <li>what should you do if your node goes down?</li> <li>how evenly will the data be distributed among the cluster? Will be there any hotspots/bottlenecks because of node over(under)-utilization?</li> <li>how can you scale your cluster in future?</li> </ul> <p>Moving computation to data has no issues with these questions, but the approach you going to choose - has.</p>