Bakai Ádám created KUDU-3547:
--------------------------------

             Summary: kudu master add failes if new master port is not the 
default value
                 Key: KUDU-3547
                 URL: https://issues.apache.org/jira/browse/KUDU-3547
             Project: Kudu
          Issue Type: Bug
          Components: master
            Reporter: Bakai Ádám


Tried this script on de87aca3dd29177658790cffeb7a1de0c8d69231 :
{code:java}
PATH=$PATH:./binPATH=$PATH:../../src/kudu/scripts/
cleanup(){    kill %1 %2 %3 %4 %5 %6 %7 %8 %9 %10pkill kudu# sudo fuser -k -9 
9873/tcpfuser -k -9 8765/tcp
pkill kudupkill kudu-masterpkill kudu-tserver../src/kudu/scripts/stop_kudu.sh
sleep 1}
cleanup
rm -rf master-0/ tserver-0/ tserver-1 tserver-2 master-1 
master-2create_stuff(){    rm -rf  $1/data $1/wal $1/log
mkdir -p $1/data $1/wal $1/log}
create_stuff master-0create_stuff tserver-0create_stuff tserver-1create_stuff 
tserver-2create_stuff master-1
sync

$PWD/bin/kudu-tserver --fs_data_dirs=$PWD/tserver-0/data 
--fs_wal_dir=$PWD/tserver-0/wal --log_dir=$PWD/tserver-0/log 
--rpc_bind_addresses=127.0.0.1:9870 --time_source=system_unsync 
--unlock_unsafe_flags --webserver_interface=127.0.0.1 --webserver_port=9871 
--tserver_master_addrs=127.0.0.1:8764 --memory_limit_hard_bytes=17916750506 
&$PWD/bin/kudu-tserver --fs_data_dirs=$PWD/tserver-1/data 
--fs_wal_dir=$PWD/tserver-1/wal --log_dir=$PWD/tserver-1/log 
--rpc_bind_addresses=127.0.0.1:9872 --time_source=system_unsync 
--unlock_unsafe_flags --webserver_interface=127.0.0.1 --webserver_port=9873 
--tserver_master_addrs=127.0.0.1:8764 --memory_limit_hard_bytes=17916750506 
&$PWD/bin/kudu-tserver --fs_data_dirs=$PWD/tserver-2/data 
--fs_wal_dir=$PWD/tserver-2/wal --log_dir=$PWD/tserver-2/log 
--rpc_bind_addresses=127.0.0.1:9874 --time_source=system_unsync 
--unlock_unsafe_flags --webserver_interface=127.0.0.1 --webserver_port=9875 
--tserver_master_addrs=127.0.0.1:8764 --memory_limit_hard_bytes=17916750506 &
sleep 1
$PWD/bin/kudu-master --master_addresses=127.0.0.1:8764 
--fs_data_dirs=$PWD/master-0/data --fs_wal_dir=$PWD/master-0/wal 
--log_dir=$PWD/master-0/log --rpc_bind_addresses=127.0.0.1:8764 
--time_source=system_unsync --unlock_unsafe_flags  --webserver_port=8765 &

#/home/abakai/kudu_1_16_2/kudu/a/b/bin/kudu-master 
--master_addresses=127.0.0.1:8764 
--fs_data_dirs=/home/abakai/kudu_1_16_2/kudu/a/b/master-0/data 
--fs_wal_dir=/home/abakai/kudu_1_16_2/kudu/a/b/master-0/wal 
--log_dir=/home/abakai/kudu_1_16_2/kudu/a/b/master-0/log 
--rpc_bind_addresses=127.0.0.1:8764 --time_source=system_unsync 
--unlock_unsafe_flags --webserver_port=8765 
--webserver_doc_root=/home/abakai/kudu_1_16_2/kudu/a/b/../../www 
kudu master list localhost:8764
sleep 1kudu master add 127.0.0.1:8764 127.0.0.1:8766 
--fs_data_dirs=$PWD/master-1/data --fs_wal_dir=$PWD/master-1/wal -logtostderr 
-v 99 &>test123
kudu master list localhost:8764
 {code}
New master is not added to the master quorum. 
There is a workaround, adding rpc_bind_address to the arguments:
{code:java}
kudu master add 127.0.0.1:8764 127.0.0.1:8766 --fs_data_dirs=$PWD/master-1/data 
--fs_wal_dir=$PWD/master-1/wal -logtostderr -v 1 
--rpc_bind_addresses=127.0.0.1:8766 
 {code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to