dubbo--Administrator Guide __ Management

Original address: http://blog.csdn.net/wilsonke/article/details/39935801

2014-10-09 18:36 3613 People read comments (0) Collection report

Directory (?) [+]

Administrator's Guide installation manual sample provider installation sample consumer installation Zookeeper Registration Center installation Redis Registration Center installation Easy Registration Center installation Simple Monitoring Center installation Management Control Taian Shipping Dimension Manual Management Console operation dimension

Recommended use of Zookeeper Registration center

You can only run demo provider and demo Consumer, which are configured by default to discover each other through the multicast registry, suggesting that they run on different machines, and that if you are on the same machine, you need to set up Unicast=false: that is: multicast ://224.5.6.7:1234?unicast=false, otherwise the unicast message to consumers may be preempted by the provider, two consumers in the same machine, only the multicast registry has this problem. You can also run multiple demo provider and demo Consumer to verify the soft load balance, demo Consumer can start multiple instances directly, and multiple demo provider have port conflicts, can run on different machines, or modify demo Provider the value of the Dubbo.protocol.port in the Conf/dubbo.properties configuration under the installation directory. You can also increase the run Simple Monitor Center, which is configured by default to discover provider and consumer through the multicast registry, and to show their dependencies and the number and time of calls between them. You can also change the multicast registry to Zookeeper Registration center, install zookeeper Registry, modify the Demo Proivder,demo consumer,simple monitor the installation directory of the three conf/ Dubbo.properties, change the value of dubbo.registry.address to zookeeper://127.0.0.1:2181, the same, if replaced by Redis registry, change the value to redis:// 127.0.0.1:6379, if replaced by simple Registry, the value is changed to dubbo://127.0.0.1:9090
Note: The multicast address cannot be matched to 127.0.0.1, nor can it be fitted to the machine's IP address, which must be a D-segment broadcast address, that is, any address between 224.0.0.0 and 239.255.255.255 Installation Manual

(+) (#) Sample Provider Installation

(+) (#)

Installation:

wget HTTP://CODE.ALIBABATECH.COM/MVN/RELEASES/COM/ALIBABA/DUBBO-DEMO-PROVIDER/2.4.1/ Dubbo-demo-provider-2.4.1-assembly.tar.gz Tar zxvf dubbo-demo-provider-2.4.1-assembly.tar.gz CD dubbo-demo-provider-2.4.1

Configuration:

VI conf/dubbo.properties

Start:

./bin/start.sh

Stop:

./bin/stop.sh

Reboot :

./bin/restart.sh

Debugging:

./bin/start.sh Debug

System State:

./bin/dump.sh

main control entrance:

./bin/server.sh start/bin/server.sh stop/bin/server.sh restart./bin/server.sh Debug./bin/server.sh dump

Standard output:

Tail-f Logs/stdout.log

command line: (See:telnet Command Reference)

Telnet 127.0.0.1 20880
Help

Or:

echo Status | nc-i 1 127.0.0.1 20880 Sample Consumer Installation

(+) (#)

Installation:

wget HTTP://CODE.ALIBABATECH.COM/MVN/RELEASES/COM/ALIBABA/DUBBO-DEMO-CONSUMER/2.4.1/ Dubbo-demo-consumer-2.4.1-assembly.tar.gz Tar zxvf dubbo-demo-consumer-2.4.1-assembly.tar.gz CD dubbo-demo-consumer-2.4.1

Configuration:

VI conf/dubbo.properties

Start:

./bin/start.sh Tail-f Logs/stdout.log

Stop:

./bin/stop.sh

Reboot :

./bin/restart.sh

Debugging:

./bin/start.sh Debug

System State:

./bin/dump.sh

main control entrance:

./bin/server.sh start/bin/server.sh stop/bin/server.sh restart./bin/server.sh Debug./bin/server.sh dump

Standard output:

Tail-f Logs/stdout.log

Zookeeper Registration Center installation

(+) (#)

It is recommended that you use the Zookeeper Registration Center client dubbo-2.3.3 above

Zookeeper is a sub project of Apache Hadoop, which is relatively strong and suggests a production environment that uses the registry.

Dubbo does not make any intrusion modifications to the zookeeper server, simply install the native zookeeper server, and all registry logic adapters are completed when the zookeeper client is invoked.

If necessary, consider using Taobao's zookeeper monitoring: http://rdc.taobao.com/team/jm/archives/1450

Installation:

wget http://www.apache.org/dist//zookeeper/zookeeper-3.3.3/zookeeper-3.3.3.tar.gz tar zxvf zookeeper-3.3.3.tar.gz CD zookeeper-3.3.3 CP conf/zoo_sample.cfg conf/zoo.cfg

Configuration:

VI conf/zoo.cfg

If you do not need a cluster, the contents of the zoo.cfg are as follows: (The data directory needs to be changed to your real output directory) zoo.cfg

ticktime=2000 initlimit=10 synclimit=5 Datadir=/home/dubbo/zookeeper-3.3.3/data clientPort=2181

If a cluster is required, the contents of the zoo.cfg are as follows: (where the Data directory and server address are changed to the information you actually deploy the machine) zoo.cfg

ticktime=2000 initlimit=10 synclimit=5 datadir=/home/dubbo/zookeeper-3.3.3/data clientPort=2181 server.1= 10.20.153.10:2555:3555 server.2=10.20.153.11:2555:3555

and place the myID file under the Data directory: (DataDir in zoo.cfg above)

mkdir Data VI myID

myID indicates its own ID, corresponding to the above zoo.cfg in the number, the first table content is 1, the second table content is 2, the contents are as follows: myID

1

Start:

./bin/zkserver.sh Start

Stop:

./bin/zkserver.sh Stop

command line: (see:http://zookeeper.apache.org/doc/r3.3.3/zookeeperadmin.html)

Telnet 127.0.0.1 2181
Dump

Pre

echo Dump | NC 127.0.0.1 2181

Usage:

dubbo.registry.address=zookeeper://10.20.153.10:2181?backup=10.20.153.11:2181

Pre