By Enes Akar
Co-founder & CTO, Hazelcast Cloud
Enes was one of the early developers of Hazelcast. He joined the company in 2011 with a passion for making distributed computing incredible simple. From 2012 to 2017, he headed the engineering team as VP of Engineering. Since 2017, he has led the development of Hazelcast Cloud, which is enterprise-grade Hazelcast software as a fully managed service in the cloud. Prior to joining Hazelcast, Enes worked in software development and software engineering at telecommunications companies, including Alcatel-Lucent and Ericsson. He holds a Bachelor of Science in Computer Engineering and an MBA from Bogazici University, Istanbul.
View all blogs by the authorDec 31, 2013
Hazelcast: When to increase Partition Count?
Hazelcast stores data in partitions. Default partition number is 271.
You can increase the partition number, if data size per partition is bigger than 100 Mb.
Why?
By consistent hashing* algorithm, partitions are migrated when nodes join or leave the cluster. While a partition is migrating, operations related to this partition are retried. So migration should be completed as soon as possible. Small partitions cause quick migrations and more responsive cluster.