Problem:
- Product Name: VisiBroker
- Product Version: 5.2.1 and above
- Product Component: Naming Service
How do master/slave Name Services share database schema?
Resolution:
In the master/slave Name Service properties, it is required to set:
vbroker.naming.masterServer
vbroker.naming.slaveServer
Also, in the startup script, the <master NS name> and <slave NS name> are used:
>nameserv -config <ns.property file> <master | slave NS name>
In the database, 4 tables are created after both the Master and Slave are started:
vbins_<master NS name>_cluster_tbl
vbins_<master NS name>_ctx_tbl
vbins_<master NS name>_graph_tbl
vbins_<master NS name>_meta_tbl
Therefore, both the Master and the Slave Naming Services share the same schema in this case. Slave does not create additional schema. This behavior only applies to the master/slave configuration.
Support Case # 579461
#NamingService
#database
#VisiNaming
#VisiBroker
#Security




