# Create geo partition table error on multi-region setup

**URL:** <https://forum.yugabyte.com/t/create-geo-partition-table-error-on-multi-region-setup/3963>\
**Category:** General\
**Created:** [October 25, 2024, 7:10pm UTC](https://forum.yugabyte.com/t/create-geo-partition-table-error-on-multi-region-setup/3963 "2024-10-25T19:10:11Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![tryyuga](https://avatars.discourse-cdn.com/v4/letter/t/d07c76/32.png) [@tryyuga](https://forum.yugabyte.com/u/tryyuga)\
**Post date:** [October 25, 2024, 7:10pm UTC](https://forum.yugabyte.com/t/create-geo-partition-table-error-on-multi-region-setup/3963/1 "2024-10-25T19:10:11Z")

</div>

hello, I have 3 regions with nine node total and everything seems to be working. I’m testing this geo partition table on the main master,and got the error, cannot figure out what I should be looking at…I started all nodes using “yugabyted”

drop TABLESPACE us\_east1 ;  
CREATE TABLESPACE us\_east1 WITH (  
replica\_placement=‘{“num\_replicas”: 3,  
“placement\_blocks”:[  
{“cloud”:“ib”,“region”:“us-east1”,“zone”:“us-east1-1a”,“min\_num\_replicas”:1},  
{“cloud”:“ib”,“region”:“us-east1”,“zone”:“us-east1-1b”,“min\_num\_replicas”:1},  
{“cloud”:“ib”,“region”:“us-east1”,“zone”:“us-east1-1c”,“min\_num\_replicas”:1}  
]}’  
);  
drop TABLE parent\_test;  
CREATE TABLE parent\_test (  
id character varying(36) not null ,  
client\_id character varying(255) ,  
details\_json character varying(5110) ,  
error character varying(255) ,  
ip\_address character varying(255) ,  
realm\_id character varying(255) ,  
session\_id character varying(255) ,  
event\_time bigint not null ,  
type character varying(255) ,  
user\_id character varying(255) ,  
created\_date timestamp without time zone ,  
geo\_partition VARCHAR,  
CONSTRAINT test\_pk PRIMARY KEY (id, event\_time,geo\_partition)  
) PARTITION BY LIST (geo\_partition );

–Create child tables for each of the geos in the respective tablespaces:  
CREATE TABLE child\_test\_east1 PARTITION OF parent\_test (  
id ,  
client\_id ,  
details\_json ,  
error ,  
ip\_address ,  
realm\_id ,  
session\_id ,  
event\_time ,  
type ,  
user\_id ,  
created\_date ,  
geo\_partition ,  
PRIMARY KEY (id HASH, event\_time, geo\_partition)  
) FOR VALUES IN (‘EAST1’) TABLESPACE us\_east1;

ERROR: Invalid table definition: Error creating table yugabyte.child\_test\_east1 on the master: Not enough tablet servers in the requested placements. Need at least 2, have 0

---

<div class="post-metadata">

**Author:** ![FranckPachot](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.yugabyte.com/franckpachot/32/353_2.png) [@FranckPachot](https://forum.yugabyte.com/u/FranckPachot)\
**Post date:** [October 25, 2024, 9:15pm UTC](https://forum.yugabyte.com/t/create-geo-partition-table-error-on-multi-region-setup/3963/2 "2024-10-25T21:15:59Z")

</div>

Hi, are you sure that you have set the cloud location when starting yugabyted, for example with `--cloud_location ib.us-east1.us-east1-1a` for the nodes in us-east1-1a?

---

<div class="post-metadata">

**Author:** ![tryyuga](https://avatars.discourse-cdn.com/v4/letter/t/d07c76/32.png) [@tryyuga](https://forum.yugabyte.com/u/tryyuga)\
**Post date:** [October 25, 2024, 10:47pm UTC](https://forum.yugabyte.com/t/create-geo-partition-table-error-on-multi-region-setup/3963/3 "2024-10-25T22:47:46Z")

</div>

> [@tryyuga](#):
>
> region”:“us-east1”,

Thanks for responding FranckPachot! Yes I did when I created used the param -cloud\_location, but after lookng at this for last 2 days, i realize it’s user error, I had misspell region”:“us-east1” which should be region”:“us-east-1” so now it works on table creation. thanks!

---

<div class="post-metadata">

**Author:** ![tryyuga](https://avatars.discourse-cdn.com/v4/letter/t/d07c76/32.png) [@tryyuga](https://forum.yugabyte.com/u/tryyuga)\
**Post date:** [October 25, 2024, 10:49pm UTC](https://forum.yugabyte.com/t/create-geo-partition-table-error-on-multi-region-setup/3963/4 "2024-10-25T22:49:10Z")

</div>

It’s not an obvious understanding of the error message, wished it was reworded but then it does make sense after I thought about it