# How to enable gloabl namespace and register the same?

**URL:** <https://community.temporal.io/t/how-to-enable-gloabl-namespace-and-register-the-same/2768>\
**Category:** Community Support\
**Tags:** xdc, deployment\
**Created:** [August 23, 2021, 10:36am UTC](https://community.temporal.io/t/how-to-enable-gloabl-namespace-and-register-the-same/2768 "2021-08-23T10:36:53Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![madhu](https://avatars.discourse-cdn.com/v4/letter/m/a8b319/32.png) [@madhu](https://community.temporal.io/u/madhu)\
**Post date:** [August 23, 2021, 10:36am UTC](https://community.temporal.io/t/how-to-enable-gloabl-namespace-and-register-the-same/2768/1 "2021-08-23T10:36:53Z")

</div>

Hi i am running tctl using docker compose, and i am looking to setup global namespace.

I have added the following to my development.yaml file  
global:  
membership:  
maxJoinDuration: 30s  
broadcastAddress: “127.0.0.1”  
port: 7936  
services:  
frontend:  
rpc:  
grpcPort: 7233  
membershipPort: 7933  
bindOnLocalHost: true  
clusterMetadata:  
enableGlobalNamespace: true  
replicationConsumer:  
type: rpc  
failoverVersionIncrement: 10  
masterClusterName: “active”  
currentClusterName: “dr”  
clusterInformation:  
active:  
enabled: true  
initialFailoverVersion: 1  
rpcName: “frontend”  
rpcAddress: “192.168.1.27:8933”  
dr:  
enabled: true  
initialFailoverVersion: 2  
rpcName: “frontend”  
rpcAddress: “127.0.0.1:7933”

and when i try to register a global name space from tctl or java SDK it fails with message

"  
/etc/temporal # tctl --ns xdc n re --gd true  
Error: Register namespace operation failed.  
Error Details: rpc error: code = InvalidArgument desc = Cannot register global namespace when not enabled  
(‘export TEMPORAL\_CLI\_SHOW\_STACKS=1’ to see stack traces)  
/etc/temporal # "

Not sure what i am missin, i am trying to follow the [instructions suggested here](https://community.temporal.io/t/global-domain-registration-in-java-sdk/282)

---

<div class="post-metadata">

**Author:** ![madhu](https://avatars.discourse-cdn.com/v4/letter/m/a8b319/32.png) [@madhu](https://community.temporal.io/u/madhu)\
**Post date:** [August 23, 2021, 11:10am UTC](https://community.temporal.io/t/how-to-enable-gloabl-namespace-and-register-the-same/2768/2 "2021-08-23T11:10:09Z")

</div>

I think this is possibly because the namespace settings are hard coded in the config template i guess

> <https://github.com/temporalio/temporal/blob/514776cfafe47311e787c8729751d1f389dceec4/docker/config_template.yaml#L257-L267>

---

<div class="post-metadata">

**Author:** ![madhu](https://avatars.discourse-cdn.com/v4/letter/m/a8b319/32.png) [@madhu](https://community.temporal.io/u/madhu)\
**Post date:** [August 23, 2021, 11:21am UTC](https://community.temporal.io/t/how-to-enable-gloabl-namespace-and-register-the-same/2768/3 "2021-08-23T11:21:45Z")

</div>

also looks like there is no way to override these in k8s too using helms. the same template gets used in k8s too.

---

<div class="post-metadata">

**Author:** ![madhu](https://avatars.discourse-cdn.com/v4/letter/m/a8b319/32.png) [@madhu](https://community.temporal.io/u/madhu)\
**Post date:** [August 23, 2021, 4:58pm UTC](https://community.temporal.io/t/how-to-enable-gloabl-namespace-and-register-the-same/2768/4 "2021-08-23T16:58:37Z")

</div>

finally i was able to create an [example xdc setup with in single docker compose](https://github.com/kkcmadhu/docker-compose/blob/patch-1/docker-compose-mysql-xdc.yml) (where two temporal server/clusers runs (temporal-active and temporal-standby) and share the same network(temporal-network) so that replication can happen between the two clusters.

In this example one can web the temporal web on port 8088 for the active cluster( temporal-active-web) and on port 8099 one can track the passive cluster ( temporal-standalone-web)

I was able to set up xdc, register a global namespace, with this setup.

I logged into standby web console and was able to view the namespaces and workflows.

So far so good…

Now to simulate cluster failure,

I explcitly brought down temporal-active server and temporal-active-mysql ( regional failure)

logged on the temporal-standby-admin-console and performed a fail over with

`tctl --ns xdc n up --ac standby`  
The fail over command was successful in tctl also the web, [http://localhost:8009/namespaces/xdc/settings](http://localhost:8009/namespaces/xdc/settings) i saw the namespaces got swapped (stand by was made active)

i verified that http:///localhost:8008 is not accessible (as i have already brought down temporal-active)

However, even after the switch, my standby workers donot seem to kick in. no actvity/worfkow tasks are being dispatched to the standby worker connected to temporal-standby-server .

I also see this error in the standby temporl-standby- server’s log after fail over

```auto
temporal-standby | {"level":"error","ts":"2021-08-23T16:57:55.228Z","msg":"Failed to get replication tasks","service":"history","error":"last connection error: connection error: desc = \"transport: Error while dialing dial tcp 192.168.0.4:7233: connect: no route to host\"; last resolver error: dns: A record lookup error: lookup temporal-active on 127.0.0.11:53: read udp 127.0.0.1:34603->127.0.0.11:53: i/o timeout","logging-call-at":"replicationTaskFetcher.go:395","stacktrace":"go.temporal.io/server/common/log.(*zapLogger).Error\n\t/temporal/common/log/zap_logger.go:143\ngo.temporal.io/server/service/history.(*replicationTaskFetcherWorker).getMessages\n\t/temporal/service/history/replicationTaskFetcher.go:395\ngo.temporal.io/server/service/history.(*replicationTaskFetcherWorker).fetchTasks\n\t/temporal/service/history/replicationTaskFetcher.go:338"}
temporal-standby | {"level":"error","ts":"2021-08-23T16:57:55.271Z","msg":"Failed to get replication tasks","service":"worker","component":"replicator","component":"replication-task-processor","xdc-source-cluster":"active","error":"last connection error: connection error: desc = \"transport: Error while dialing dial tcp 192.168.0.4:7233: connect: no route to host\"; last resolver error: dns: A record lookup error: lookup temporal-active on 127.0.0.11:53: read udp 127.0.0.1:37973->127.0.0.11:53: i/o timeout","logging-call-at":"namespace_replication_message_processor.go:157","stacktrace":"go.temporal.io/server/common/log.(*zapLogger).Error\n\t/temporal/common/log/zap_logger.go:143\ngo.temporal.io/server/service/worker/replicator.(*namespaceReplicationMessageProcessor).getAndHandleNamespaceReplicationTasks\n\t/temporal/service/worker/replicator/namespace_replication_message_processor.go:157\ngo.temporal.io/server/service/worker/replicator.(*namespaceReplicationMessageProcessor).processorLoop\n\t/temporal/service/worker/replicator/namespace_replication_message_processor.go:121"}

```

---

<div class="post-metadata">

**Author:** ![madhu](https://avatars.discourse-cdn.com/v4/letter/m/a8b319/32.png) [@madhu](https://community.temporal.io/u/madhu)\
**Post date:** [August 24, 2021, 10:27am UTC](https://community.temporal.io/t/how-to-enable-gloabl-namespace-and-register-the-same/2768/5 "2021-08-24T10:27:11Z")

</div>

filed a bug [Temporal Failover to standby cluster not happening · Issue #1847 · temporalio/temporal · GitHub](https://github.com/temporalio/temporal/issues/1847) for standby cluster not picking up things after fail over