Unsupported fillfactor Parameter and Exceeding Tablet Replica Limit in YugabyteDB – Solutions and Best Practices?

[kamleshkumar]

Question on Exceeding Tablet Replica Limit: “While creating an index, I received the following error: SQL Error [XX000]: ERROR: Invalid table definition: Error creating index... The requested number of tablet replicas would cause the total running tablet replica count (198) to exceed the safe system maximum (197). What is the best approach to handle this issue? Should I add more nodes to my cluster or adjust my sharding strategy to reduce the number of tablets? Any guidance on best practices for managing tablet replicas in large databases would be appreciated.”

Question on Unsupported “fillfactor” Parameter: “I encountered an error when trying to set the fillfactor parameter in my SQL queries, specifically: SQL Error [22023]: ERROR: unrecognized parameter "fillfactor". Is the fillfactor setting unsupported in YugabyteDB? If so, is there an alternative way to optimize table fill rates in Yugabyte, or should I just remove this parameter from my queries?”

I am using yugabyte AEON sandbox cluster.

[dorian_yugabyte]

Hi @kamleshkumar

@kamleshkumar

Question on Exceeding Tablet Replica Limit:

Looks like you’re hitting too many tablets error. Explained in yb-tserver configuration reference | YugabyteDB Docs (see “max number of tablet replicas”)

The solutions are:

• Create fewer tablets either when creating an table/index or as a setting (see yb-tserver configuration reference | YugabyteDB Docs )
• Use colocation Colocating tables and databases | YugabyteDB Docs
• Have better hardware resources

Not recommended:

• Disabling the limits

@kamleshkumar

fillfactor". Is the fillfactor setting unsupported in YugabyteDB? If so, is there an alternative way to optimize table fill rates in Yugabyte, or should I just remove this parameter from my queries?”

fillfactor doesn’t apply in YugabyteDB and you can omit it.