[Pgpool-general] [pgpool problem] about streaming replication and load balancing.

イジュヨン elijah9 at gmail.com
Tue Nov 15 03:54:32 UTC 2011


yes, i am sure.

I tried it)

I tried a test how to change backend_hostname0 and backend_hostname1.
(like as
..
backend_hostname0='192.168.3.141'
backend_weight0 = 1     # but not changed 'backend_weight0'
backend_hostname1='192.168.3.160'
backend_weight1 = 1000    # not changed 'backend_weight1' too.
...
)

then pgpool has always connected backend_hostname0(192.168.3.141).

i think that this mean is 'can not reading pgpool load balancing' or 'can
not reading PG server after backend_hostname0'.

what do you have a idea about something please?


2011/11/11 Martín Marqués <martin.marques at gmail.com>

> Are you sure that pgpool can connect to the second PG server?
>
> 2011/11/10 イジュヨン <elijah9 at gmail.com>:
> > hello, developers and anybody using pgpool.
> >
> > i have a something problem about 'streaming replication' and 'load
> > balancing'.
> > i don't know what mail address for to ask like this problem. then i send
> > this asking mail to you.
> >
> > (if i mistake this doing, please teach me that i can ask mailling list.)
> >
> > well, my question is this)
> >
> > <server spac>
> >  - my 1st postgresql server(os:ubuntu10.4, ip:192.168.3.160, postgresql
> > version 9.1) run normal operations.
> >
> >    (i checked that requested query success by use log)
> >
> >  - my 2nd postgresql server(os:ubuntu10.4, ip:192.168.3.141, postgresql
> > version 9.1) run normal operations too.
> >    (i checked it too.)
> >
> >  - my pgpool server(ip:192.168.3.160 - with 1st postgresql server, pgpool
> > version 3.1 -
> >
> http://ftp2.jp.postgresql.org/pub/postgresql/projects/pgFoundry/pgpool/pgpool-II-3.1.tar.gz
> )
> > run normal operations too.
> >
> >    (i checked that requested query success by use log too.)
> >
> >
> > <pgpool conf information>
> > # cat pgpool.conf
> > listen_addresses = '*'
> > port = 9999
> > socket_dir = '/tmp'
> > pcp_port = 9898
> >
> > pcp_socket_dir = '/tmp'
> > backend_hostname0 = '192.168.3.160'
> > backend_port0 = 5432
> > backend_weight0 = 1
> > backend_data_directory0 = '/DbCenter_master/data'
> > backend_flag0 = 'ALLOW_TO_FAILOVER'
> >
> > backend_hostname1 = '192.168.3.141'
> > backend_port1 = 5432
> > backend_weight1 = 1000
> > backend_flag1 = 'ALLOW_TO_FAILOVER'
> > enable_pool_hba = on
> > authentication_timeout = 60
> > ssl = off
> > num_init_children = 32
> >
> > max_pool = 4
> > child_life_time = 300
> > child_max_connections = 0
> > connection_life_time = 0
> > client_idle_limit = 0
> > log_destination = 'syslog'
> > print_timestamp = on
> > log_connections = on
> > log_hostname = on
> >
> > log_statement = on
> > log_per_node_statement = on
> > log_standby_delay = 'if_over_threshold'
> > syslog_facility = 'LOCAL0'
> > syslog_ident = 'pgpool'
> > debug_level = 0
> > pid_file_name = '/var/run/pgpool/pgpool.pid'
> >
> > logdir = '/tmp'
> > connection_cache = off
> > reset_query_list = 'ABORT; DISCARD ALL'
> > replication_mode = off
> > replicate_select = off
> > insert_lock = off
> > lobj_lock_table = ''
> > replication_stop_on_mismatch = off
> >
> > failover_if_affected_tuples_mismatch = off
> > load_balance_mode = on
> > ignore_leading_white_space = on
> > white_function_list = ''
> > black_function_list = 'currval,lastval,nextval,setval'
> > master_slave_mode = on
> >
> > master_slave_sub_mode = 'stream'
> > sr_check_period = 10
> > sr_check_user = 'repl_user'
> > sr_check_password = 'password'
> > delay_threshold = 10000000
> > follow_master_command = 'date > /DataCenter_nas/abc'
> >
> > parallel_mode = off
> > enable_query_cache = off
> > pgpool2_hostname = ''
> > system_db_hostname  = 'localhost'
> > system_db_port = 5432
> > system_db_dbname = 'pgpool'
> > system_db_schema = 'pgpool_catalog'
> >
> > system_db_user = 'pgpool'
> > system_db_password = ''
> > health_check_period = 0
> > health_check_timeout = 20
> > health_check_user = 'nobody'
> > health_check_password = ''
> > failover_command = 'date > /DataCenter_nas/abc2'
> >
> > failback_command = 'date > /DataCenter_nas/abc3'
> > fail_over_on_backend_error = on
> > recovery_user = 'nobody'
> > recovery_password = ''
> > recovery_1st_stage_command = ''
> > recovery_2nd_stage_command = ''
> >
> > recovery_timeout = 90
> > client_idle_limit_in_recovery = 0
> > relcache_expire = 0
> > #-------------- the end of pgpool conf---------------
> >
> >
> > <i tried it>
> > i send query request to pgpool, and 1st postgresql catch it always.
> >
> > it is a wrong working
> >  why i did set pgpools to 1:1000 about backend_weight0 and
> backend_weight1
> > values.(look my pgpool.conf file)
> > i think that this case's good working is almost catch 2nd postgresql
> server.
> >
> > i don't know this working reason(about wrong pgpool's load balancing and
> > after backend_hostname1 setting values).
> >
> > do you have to teach me about this problem or something idea?
> > I hope your help. please help me.
> >
> >
> > i waiting your mail.
> > thanks.
> >
> >
> > _______________________________________________
> > Pgpool-general mailing list
> > Pgpool-general at pgfoundry.org
> > http://pgfoundry.org/mailman/listinfo/pgpool-general
> >
> >
>
>
>
> --
> Martín Marqués
> select 'martin.marques' || '@' || 'gmail.com'
> DBA, Programador, Administrador
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://pgfoundry.org/pipermail/pgpool-general/attachments/20111115/2d51bc3f/attachment.html>


More information about the Pgpool-general mailing list