Thanks for everyone's feedback regarding the capacity planning question. My main objective here is to size my servers accordingly and keep the related data on the same server, as much as possible. It seems a custom affinity function that takes into account the server classes (defined based on capacity) is the potential solution as suggested. Naveen -- I will keep in mind your suggestion as well, regarding partitioning the huge data sets. thanks.
Any feedback regarding my other questions: Data pin to cache: How do I make sure certain data never gets evicted (with native persistence enabled)? For example, I want my dimension data to always stay in cache. How do I implement service pipelining in apache ignite? Would continuous query be the mechanism? Any examples? Streaming: Are there examples on how to define watermarks, i.e., input completeness with regard to the event timestamp? On Fri, Jan 4, 2019 at 3:33 AM Naveen <naveen.band...@gmail.com> wrote: > Regarding your question on capacity planning > > Not sure we have any work around to have data equally getting distributed > to > fulfill your requirement technically and do the sizing. But > non-technically, > you can change your design to include state as well as part of your > affinity > key along with the country and rest of the fields you have, so that data > pertaining to India can be segregated into chunks of data which is state > wise and if you see statewide data is definitely not so huge compared to > country as a whole and same time relevant data is also getting stored on a > single node. Your design also should permit this to keep state name as > part > of your affinity key to resolve this use case. > > > Thanks > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
