spring:
shardingsphere:
orchestration:
testname1:
orchestration-type: registry_center,distributed_lock_management
instance-type: zookeeper
server-lists:
192.178.32.45:9001,192.178.32.45:9002,192.178.32.45:9003
namespace: testnamspace1
props:
overwrite: false
retry-interval-milliseconds: 10
time-to-live-seconds: 10
max-retries: 10
operation-timeout-milliseconds: 10
digest:
testname2:
orchestration-type: configuration_center
instance-type: apollo
server-lists:
192.178.32.45:9001,192.178.32.45:9002,192.178.32.45:9003
namespace: testnamspace2
props:
overwrite: true
retry-interval-milliseconds: 10
time-to-live-seconds: 10
max-retries: 10
operation-timeout-milliseconds: 10
digest:
sunbufu <[email protected]> 于2019年11月27日周三 上午9:08写道：
> Hi, In the result of discussion, orchestration-type is better than
> center-type. cause it is not good to introduce new concepts.
>
> —————————
> Haisheng Sun (sunbufu)
> Apache ShardingSphere
>
> On 11/27/2019 08:45, guangyuan wang <[email protected]> wrote:
> Dear All
>
> As the registry center interface was used as distributed lock management
> and config center, I think it's better to split it into three parts, they
> are: config center, registry center, distributed lock management.
> And the configuration yml file, looks like these:
>
> spring:
> shardingsphere:
> orchestration:
> testname1:
> center-type: registry_center,distributed_lock_management
> instance-type: zookeeper
> server-lists:
> 192.178.32.45:9001,192.178.32.45:9002,192.178.32.45:9003
> namespace: testnamspace1
> props:
> overwrite: false
> retry-interval-milliseconds: 10
> time-to-live-seconds: 10
> max-retries: 10
> operation-timeout-milliseconds: 10
> digest:
> testname2:
> center-type: configuration_center
> instance-type: apollo
> server-lists:
> 192.178.32.45:9001,192.178.32.45:9002,192.178.32.45:9003
> namespace: testnamspace2
> props:
> overwrite: true
> retry-interval-milliseconds: 10
> time-to-live-seconds: 10
> max-retries: 10
> operation-timeout-milliseconds: 10
> digest:
>
>
