date:20110920

[Pgpool-general] Data not same on both nodes, streaming replication & load balancing

2011-09-20 Thread Armin Nesiren

Hi everyone,

I have configuration pgpool streaming replication & load balancing
configuration with two nodes.
pgpool version is 3.1.0-alpha2 (hatsuiboshi), postgres on both nodes is
9.0.4

Reason why I have use this version is that latest stable version (at that
time) 3.0.1 was everything
but not stable.

Anyway.. I have situation now.. that my slave node is containing different
data from master node.
I select something from master and get one result, and same query from slave
and I get different result.

How to prevent this happening, and how it is possible that this happened.
How to know data my other data is health?

Thanks.

-- 
Armin
___
Pgpool-general mailing list
Pgpool-general@pgfoundry.org
http://pgfoundry.org/mailman/listinfo/pgpool-general

Re: [Pgpool-general] Data not same on both nodes, streaming replication & load balancing

2011-09-20 Thread Daniel . Crespo

Hi everyone,

 

I have configuration pgpool streaming replication & load balancing
configuration with two nodes.

pgpool version is 3.1.0-alpha2 (hatsuiboshi), postgres on both nodes is
9.0.4

 

Reason why I have use this version is that latest stable version (at
that time) 3.0.1 was everything

but not stable.

 

Anyway.. I have situation now.. that my slave node is containing
different data from master node.

I select something from master and get one result, and same query from
slave and I get different result.

 

How to prevent this happening, and how it is possible that this
happened.

How to know data my other data is health?

 

This is specific to PostgreSQL 9.x Streaming Replication. Please check:
http://www.postgresql.org/docs/9.0/interactive/warm-standby.html#STREAMI
NG-REPLICATION

 

-Daniel

___
Pgpool-general mailing list
Pgpool-general@pgfoundry.org
http://pgfoundry.org/mailman/listinfo/pgpool-general

Re: [Pgpool-general] seemingly hung pgpool process consuming 100% CPU

2011-09-20 Thread Lonni J Friedman

I tried to do that, but pgpool refuses to start reporting:
-bash: /usr/lib/debug/usr/sbin/pgpool.debug: bad ELF interpreter: No
such file or directory

I'm puzzled why it fails, as it was built on the same server where I
built the (working) release build of pgpool.

$ file /usr/lib/debug/usr/sbin/pgpool.debug
/usr/lib/debug/usr/sbin/pgpool.debug: ELF 64-bit LSB executable,
x86-64, version 1 (GNU/Linux), dynamically linked (uses shared libs),
for GNU/Linux 2.6.18, not stripped
$ file /usr/sbin/pgpool
/usr/sbin/pgpool: ELF 64-bit LSB executable, x86-64, version 1 (SYSV),
dynamically linked (uses shared libs), for GNU/Linux 2.6.18, stripped




On Mon, Sep 19, 2011 at 7:10 PM, Tatsuo Ishii  wrote:
> It's really hard to find the cause of the problem from a stack trace
> without symbol tables... Is it possible to reinstalll pgpool binary
> with debug symbols?
> --
> Tatsuo Ishii
> SRA OSS, Inc. Japan
> English: http://www.sraoss.co.jp/index_en.php
> Japanese: http://www.sraoss.co.jp
>
>> This happened again.  I ran the gdb command that you requested,
>> however it occurred to me that the output may not be all that useful
>> since I'm not running a debug build of pgpool:
>> ###
>> # gdb pgpool 2343
>> GNU gdb (GDB) Red Hat Enterprise Linux (7.1-29.el6)
>> Copyright (C) 2010 Free Software Foundation, Inc.
>> License GPLv3+: GNU GPL version 3 or later 
>> This is free software: you are free to change and redistribute it.
>> There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
>> and "show warranty" for details.
>> This GDB was configured as "x86_64-redhat-linux-gnu".
>> For bug reporting instructions, please see:
>> ...
>> Reading symbols from /usr/sbin/pgpool...(no debugging symbols found)...done.
>> Attaching to program: /usr/sbin/pgpool, process 2343
>> Reading symbols from /usr/lib64/libpq.so.5...(no debugging symbols
>> found)...done.
>> Loaded symbols for /usr/lib64/libpq.so.5
>> Reading symbols from /usr/lib64/libpcp.so.0...(no debugging symbols
>> found)...done.
>> Loaded symbols for /usr/lib64/libpcp.so.0
>> Reading symbols from /lib64/libpam.so.0...(no debugging symbols 
>> found)...done.
>> Loaded symbols for /lib64/libpam.so.0
>> Reading symbols from /usr/lib64/libssl.so.10...(no debugging symbols
>> found)...done.
>> Loaded symbols for /usr/lib64/libssl.so.10
>> Reading symbols from /usr/lib64/libcrypto.so.10...(no debugging
>> symbols found)...done.
>> Loaded symbols for /usr/lib64/libcrypto.so.10
>> Reading symbols from /lib64/libcrypt.so.1...(no debugging symbols 
>> found)...done.
>> Loaded symbols for /lib64/libcrypt.so.1
>> Reading symbols from /lib64/libresolv.so.2...(no debugging symbols
>> found)...done.
>> Loaded symbols for /lib64/libresolv.so.2
>> Reading symbols from /lib64/libnsl.so.1...(no debugging symbols 
>> found)...done.
>> Loaded symbols for /lib64/libnsl.so.1
>> Reading symbols from /lib64/libm.so.6...(no debugging symbols found)...done.
>> Loaded symbols for /lib64/libm.so.6
>> Reading symbols from /lib64/libc.so.6...(no debugging symbols found)...done.
>> Loaded symbols for /lib64/libc.so.6
>> Reading symbols from /lib64/libgssapi_krb5.so.2...(no debugging
>> symbols found)...done.
>> Loaded symbols for /lib64/libgssapi_krb5.so.2
>> Reading symbols from /usr/lib64/libldap_r-2.4.so.2...(no debugging
>> symbols found)...done.
>> Loaded symbols for /usr/lib64/libldap_r-2.4.so.2
>> Reading symbols from /lib64/libpthread.so.0...(no debugging symbols
>> found)...done.
>> [Thread debugging using libthread_db enabled]
>> Loaded symbols for /lib64/libpthread.so.0
>> Reading symbols from /lib64/libaudit.so.1...(no debugging symbols 
>> found)...done.
>> Loaded symbols for /lib64/libaudit.so.1
>> Reading symbols from /lib64/libdl.so.2...(no debugging symbols found)...done.
>> Loaded symbols for /lib64/libdl.so.2
>> Reading symbols from /lib64/libkrb5.so.3...(no debugging symbols 
>> found)...done.
>> Loaded symbols for /lib64/libkrb5.so.3
>> Reading symbols from /lib64/libcom_err.so.2...(no debugging symbols
>> found)...done.
>> Loaded symbols for /lib64/libcom_err.so.2
>> Reading symbols from /lib64/libk5crypto.so.3...(no debugging symbols
>> found)...done.
>> Loaded symbols for /lib64/libk5crypto.so.3
>> Reading symbols from /lib64/libz.so.1...(no debugging symbols found)...done.
>> Loaded symbols for /lib64/libz.so.1
>> Reading symbols from /usr/lib64/libfreebl3.so...(no debugging symbols
>> found)...done.
>> Loaded symbols for /usr/lib64/libfreebl3.so
>> Reading symbols from /lib64/ld-linux-x86-64.so.2...(no debugging
>> symbols found)...done.
>> Loaded symbols for /lib64/ld-linux-x86-64.so.2
>> Reading symbols from /lib64/libkrb5support.so.0...(no debugging
>> symbols found)...done.
>> Loaded symbols for /lib64/libkrb5support.so.0
>> Reading symbols from /lib64/libkeyutils.so.1...(no debugging symbols
>> found)...done.
>> Loaded symbols for /lib64/libkeyutils.so.1
>> Reading sym

Re: [Pgpool-general] seemingly hung pgpool process consuming 100% CPU

2011-09-20 Thread Lonni J Friedman

Nevermind, I figured out what I was doing wrong.  Now I just need for
this to hang again.

On Tue, Sep 20, 2011 at 9:08 AM, Lonni J Friedman  wrote:
> I tried to do that, but pgpool refuses to start reporting:
> -bash: /usr/lib/debug/usr/sbin/pgpool.debug: bad ELF interpreter: No
> such file or directory
>
> I'm puzzled why it fails, as it was built on the same server where I
> built the (working) release build of pgpool.
>
> $ file /usr/lib/debug/usr/sbin/pgpool.debug
> /usr/lib/debug/usr/sbin/pgpool.debug: ELF 64-bit LSB executable,
> x86-64, version 1 (GNU/Linux), dynamically linked (uses shared libs),
> for GNU/Linux 2.6.18, not stripped
> $ file /usr/sbin/pgpool
> /usr/sbin/pgpool: ELF 64-bit LSB executable, x86-64, version 1 (SYSV),
> dynamically linked (uses shared libs), for GNU/Linux 2.6.18, stripped
>
>
>
>
> On Mon, Sep 19, 2011 at 7:10 PM, Tatsuo Ishii  wrote:
>> It's really hard to find the cause of the problem from a stack trace
>> without symbol tables... Is it possible to reinstalll pgpool binary
>> with debug symbols?
>> --
>> Tatsuo Ishii
>> SRA OSS, Inc. Japan
>> English: http://www.sraoss.co.jp/index_en.php
>> Japanese: http://www.sraoss.co.jp
>>
>>> This happened again.  I ran the gdb command that you requested,
>>> however it occurred to me that the output may not be all that useful
>>> since I'm not running a debug build of pgpool:
>>> ###
>>> # gdb pgpool 2343
>>> GNU gdb (GDB) Red Hat Enterprise Linux (7.1-29.el6)
>>> Copyright (C) 2010 Free Software Foundation, Inc.
>>> License GPLv3+: GNU GPL version 3 or later 
>>> 
>>> This is free software: you are free to change and redistribute it.
>>> There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
>>> and "show warranty" for details.
>>> This GDB was configured as "x86_64-redhat-linux-gnu".
>>> For bug reporting instructions, please see:
>>> ...
>>> Reading symbols from /usr/sbin/pgpool...(no debugging symbols found)...done.
>>> Attaching to program: /usr/sbin/pgpool, process 2343
>>> Reading symbols from /usr/lib64/libpq.so.5...(no debugging symbols
>>> found)...done.
>>> Loaded symbols for /usr/lib64/libpq.so.5
>>> Reading symbols from /usr/lib64/libpcp.so.0...(no debugging symbols
>>> found)...done.
>>> Loaded symbols for /usr/lib64/libpcp.so.0
>>> Reading symbols from /lib64/libpam.so.0...(no debugging symbols 
>>> found)...done.
>>> Loaded symbols for /lib64/libpam.so.0
>>> Reading symbols from /usr/lib64/libssl.so.10...(no debugging symbols
>>> found)...done.
>>> Loaded symbols for /usr/lib64/libssl.so.10
>>> Reading symbols from /usr/lib64/libcrypto.so.10...(no debugging
>>> symbols found)...done.
>>> Loaded symbols for /usr/lib64/libcrypto.so.10
>>> Reading symbols from /lib64/libcrypt.so.1...(no debugging symbols 
>>> found)...done.
>>> Loaded symbols for /lib64/libcrypt.so.1
>>> Reading symbols from /lib64/libresolv.so.2...(no debugging symbols
>>> found)...done.
>>> Loaded symbols for /lib64/libresolv.so.2
>>> Reading symbols from /lib64/libnsl.so.1...(no debugging symbols 
>>> found)...done.
>>> Loaded symbols for /lib64/libnsl.so.1
>>> Reading symbols from /lib64/libm.so.6...(no debugging symbols found)...done.
>>> Loaded symbols for /lib64/libm.so.6
>>> Reading symbols from /lib64/libc.so.6...(no debugging symbols found)...done.
>>> Loaded symbols for /lib64/libc.so.6
>>> Reading symbols from /lib64/libgssapi_krb5.so.2...(no debugging
>>> symbols found)...done.
>>> Loaded symbols for /lib64/libgssapi_krb5.so.2
>>> Reading symbols from /usr/lib64/libldap_r-2.4.so.2...(no debugging
>>> symbols found)...done.
>>> Loaded symbols for /usr/lib64/libldap_r-2.4.so.2
>>> Reading symbols from /lib64/libpthread.so.0...(no debugging symbols
>>> found)...done.
>>> [Thread debugging using libthread_db enabled]
>>> Loaded symbols for /lib64/libpthread.so.0
>>> Reading symbols from /lib64/libaudit.so.1...(no debugging symbols 
>>> found)...done.
>>> Loaded symbols for /lib64/libaudit.so.1
>>> Reading symbols from /lib64/libdl.so.2...(no debugging symbols 
>>> found)...done.
>>> Loaded symbols for /lib64/libdl.so.2
>>> Reading symbols from /lib64/libkrb5.so.3...(no debugging symbols 
>>> found)...done.
>>> Loaded symbols for /lib64/libkrb5.so.3
>>> Reading symbols from /lib64/libcom_err.so.2...(no debugging symbols
>>> found)...done.
>>> Loaded symbols for /lib64/libcom_err.so.2
>>> Reading symbols from /lib64/libk5crypto.so.3...(no debugging symbols
>>> found)...done.
>>> Loaded symbols for /lib64/libk5crypto.so.3
>>> Reading symbols from /lib64/libz.so.1...(no debugging symbols found)...done.
>>> Loaded symbols for /lib64/libz.so.1
>>> Reading symbols from /usr/lib64/libfreebl3.so...(no debugging symbols
>>> found)...done.
>>> Loaded symbols for /usr/lib64/libfreebl3.so
>>> Reading symbols from /lib64/ld-linux-x86-64.so.2...(no debugging
>>> symbols found)...done.
>>> Loaded symbols for /lib64/ld-linux-x86-64.so.2
>>> Reading symb

[Pgpool-general] Pgpool-II connection problems when monitoring Heartbeat

2011-09-20 Thread Maria Antonia Lajus Marrero

Hello, I need anyone help me!!!

I'm pretty new working with cluster tools. I've a 4 node scheme to
ensure high availability, replication, connection pooling and load
balancing, 2 nodes are balancers and 2 are SQL(backends). Each
balancer has an instance of pgPool-II 3.0.3 and Heartbeat 2.1.3. the
SQL nodes have an instance of PostgreSQL 8.3.9. All of this solution
is on CentOS 5.5 operating system.
The pgPool-II service is monitoring by Heartbeat. The problem is, that
every morning after the servers are kept in a specific time without
attending requests, PGPool service's stop and every morning database
servers are down.
I need someone who can tell me what's happening. If this time is a
problem in the pgpool.conf configuration file or if a problem on the
issue of integration of the tools versions.
I wonder if there is any problem with the use of PostgreSQL version
8.3.9 and 3.0.3 pgPool-II?
I appreciate all the help you can give me.

This is the pgpool.conf file structure.

listen_addresses = '*'
port = 5432
pcp_port = 9898
socket_dir = '/var/run/postgresql'
pcp_socket_dir = '/var/run/postgresql'
backend_socket_dir = '/var/run/postgresql'
pcp_timeout = 10
num_init_children = 300
max_pool = 3
child_life_time = 300
connection_life_time = 0
child_max_connections = 0
client_idle_limit = 0
authentication_timeout = 60
logdir = '/var/run/postgresql'
pid_file_name=%26%2339%3B%2Fvar%2Frun%2Fpgpool%2Fpgpool%2Epid%26%2339%3B
replication_mode = true
load_balance_mode = true
replication_stop_on_mismatch = true
failover_if_affected_tuples_mismatch = false
replicate_select = false
reset_query_list = 'ABORT; DISCARD ALL'
white_function_list = ''
black_function_list = 'nextval,setval'
print_timestamp = true
master_slave_mode = false
delay_threshold = 0
log_standby_delay = 'none'
connection_cache = true
health_check_timeout = 20
health_check_period = 0
health_check_user = 'pgpool2'
#failover_command = '/var/lib/pgsql/data/pgpool-failover %d %h %p %D %m %M'
failover_command = ''
#failback_command = '/var/lib/pgsql/data/pgpool-failback %d %h %p %D %m %M'
failback_command = ''
fail_over_on_backend_error = true
insert_lock = false
ignore_leading_white_space = true
log_statement = false
log_per_node_statement = false
log_connections = true
log_hostname=false
parallel_mode = false
enable_query_cache = false
pgpool2_hostname=%26%2339%3Bbalanceador03%26%2339%3B
system_db_hostname=%26%2339%3Blocalhost%26%2339%3B
system_db_port = 5432
system_db_dbname=%26%2339%3Bpgpool%26%2339%3B
system_db_schema = 'pgpool_catalog'
system_db_user = 'pgpool'
system_db_password = ''
backend_hostname0 = '15.120.190.12'
backend_port0 = 5432
backend_weight0 = 1
backend_data_directory0 = '/var/lib/pgsql/data/'
backend_hostname1 = '15.120.190.11'
backend_port1 = 5432
backend_weight1 = 1
backend_data_directory1 = '/var/lib/pgsql/data/'
enable_pool_hba = true
recovery_user = 'pgpool2'
recovery_password = ''
recovery_1st_stage_command = 'base-backup'
#recovery_1st_stage_command = ''
recovery_2nd_stage_command = 'pgpool-recovery-pitr'
#recovery_2nd_stage_command = ''
recovery_timeout = 300
client_idle_limit_in_recovery = 0
lobj_lock_table = ''
ssl = false
debug_level = 0


Mary
___
Pgpool-general mailing list
Pgpool-general@pgfoundry.org
http://pgfoundry.org/mailman/listinfo/pgpool-general

Re: [Pgpool-general] Pgpool-II connection problems when monitoring Heartbeat

2011-09-20 Thread Maria Antonia Lajus Marrero

Hello, I need anyone help me!!!

I'm pretty new working with cluster tools. I've a 4 node scheme to
ensure high availability, replication, connection pooling and load
balancing, 2 nodes are balancers and 2 are SQL(backends). Each
balancer has an instance of pgPool-II 3.0.3 and Heartbeat 2.1.3. the
SQL nodes have an instance of PostgreSQL 8.3.9. All of this solution
is on CentOS 5.5 operating system.
The pgPool-II service is monitoring by Heartbeat. The problem is, that
every morning after the servers are kept in a specific time without
attending requests, PGPool service's stop and every morning database
servers are down.
I need someone who can tell me what's happening. If this time is a
problem in the pgpool.conf configuration file or if a problem on the
issue of integration of the tools versions.
I wonder if there is any problem with the use of PostgreSQL version
8.3.9 and 3.0.3 pgPool-II?
I appreciate all the help you can give me.

This is the pgpool.conf file structure.

listen_addresses = '*'
port = 5432
pcp_port = 9898
socket_dir = '/var/run/postgresql'
pcp_socket_dir = '/var/run/postgresql'
backend_socket_dir = '/var/run/postgresql'
pcp_timeout = 10
num_init_children = 300
max_pool = 3
child_life_time = 300
connection_life_time = 0
child_max_connections = 0
client_idle_limit = 0
authentication_timeout = 60
logdir = '/var/run/postgresql'
pid_file_name = '/var/run/pgpool/pgpool.pid'
replication_mode = true
load_balance_mode = true
replication_stop_on_mismatch = true
failover_if_affected_tuples_mismatch = false
replicate_select = false
reset_query_list = 'ABORT; DISCARD ALL'
white_function_list = ''
black_function_list = 'nextval,setval'
print_timestamp = true
master_slave_mode = false
delay_threshold = 0
log_standby_delay = 'none'
connection_cache = true
health_check_timeout = 20
health_check_period = 0
health_check_user = 'pgpool2'
#failover_command = '/var/lib/pgsql/data/pgpool-failover %d %h %p %D %m %M'
failover_command = ''
#failback_command = '/var/lib/pgsql/data/pgpool-failback %d %h %p %D %m %M'
failback_command = ''
fail_over_on_backend_error = true
insert_lock = false
ignore_leading_white_space = true
log_statement = false
log_per_node_statement = false
log_connections = true
log_hostname = false
parallel_mode = false
enable_query_cache = false
pgpool2_hostname = 'balanceador03'
system_db_hostname = 'localhost'
system_db_port = 5432
system_db_dbname = 'pgpool'
system_db_schema = 'pgpool_catalog'
system_db_user = 'pgpool'
system_db_password = ''
backend_hostname0 = '15.120.190.12'
backend_port0 = 5432
backend_weight0 = 1
backend_data_directory0 = '/var/lib/pgsql/data/'
backend_hostname1 = '15.120.190.11'
backend_port1 = 5432
backend_weight1 = 1
backend_data_directory1 = '/var/lib/pgsql/data/'
enable_pool_hba = true
recovery_user = 'pgpool2'
recovery_password = ''
recovery_1st_stage_command = 'base-backup'
#recovery_1st_stage_command = ''
recovery_2nd_stage_command = 'pgpool-recovery-pitr'
#recovery_2nd_stage_command = ''
recovery_timeout = 300
client_idle_limit_in_recovery = 0
lobj_lock_table = ''
ssl = false
debug_level = 0


Mary
___
Pgpool-general mailing list
Pgpool-general@pgfoundry.org
http://pgfoundry.org/mailman/listinfo/pgpool-general

Re: [Pgpool-general] Pgpool-II connection problems when monitoring Heartbeat

2011-09-20 Thread Tatsuo Ishii

Please provide logging of pgpool and PostgreSQL when the problem
occured.  In the mean time, I don't see particular problem with
PostgreSQL 8.3.9 and pgpool-II 3.0.3 combo.
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese: http://www.sraoss.co.jp

> Hello, I need anyone help me!!!
> 
> I'm pretty new working with cluster tools. I've a 4 node scheme to
> ensure high availability, replication, connection pooling and load
> balancing, 2 nodes are balancers and 2 are SQL(backends). Each
> balancer has an instance of pgPool-II 3.0.3 and Heartbeat 2.1.3. the
> SQL nodes have an instance of PostgreSQL 8.3.9. All of this solution
> is on CentOS 5.5 operating system.
> The pgPool-II service is monitoring by Heartbeat. The problem is, that
> every morning after the servers are kept in a specific time without
> attending requests, PGPool service's stop and every morning database
> servers are down.
> I need someone who can tell me what's happening. If this time is a
> problem in the pgpool.conf configuration file or if a problem on the
> issue of integration of the tools versions.
> I wonder if there is any problem with the use of PostgreSQL version
> 8.3.9 and 3.0.3 pgPool-II?
> I appreciate all the help you can give me.
> 
> This is the pgpool.conf file structure.
> 
> listen_addresses = '*'
> port = 5432
> pcp_port = 9898
> socket_dir = '/var/run/postgresql'
> pcp_socket_dir = '/var/run/postgresql'
> backend_socket_dir = '/var/run/postgresql'
> pcp_timeout = 10
> num_init_children = 300
> max_pool = 3
> child_life_time = 300
> connection_life_time = 0
> child_max_connections = 0
> client_idle_limit = 0
> authentication_timeout = 60
> logdir = '/var/run/postgresql'
> pid_file_name=%26%2339%3B%2Fvar%2Frun%2Fpgpool%2Fpgpool%2Epid%26%2339%3B
> replication_mode = true
> load_balance_mode = true
> replication_stop_on_mismatch = true
> failover_if_affected_tuples_mismatch = false
> replicate_select = false
> reset_query_list = 'ABORT; DISCARD ALL'
> white_function_list = ''
> black_function_list = 'nextval,setval'
> print_timestamp = true
> master_slave_mode = false
> delay_threshold = 0
> log_standby_delay = 'none'
> connection_cache = true
> health_check_timeout = 20
> health_check_period = 0
> health_check_user = 'pgpool2'
> #failover_command = '/var/lib/pgsql/data/pgpool-failover %d %h %p %D %m %M'
> failover_command = ''
> #failback_command = '/var/lib/pgsql/data/pgpool-failback %d %h %p %D %m %M'
> failback_command = ''
> fail_over_on_backend_error = true
> insert_lock = false
> ignore_leading_white_space = true
> log_statement = false
> log_per_node_statement = false
> log_connections = true
> log_hostname=false
> parallel_mode = false
> enable_query_cache = false
> pgpool2_hostname=%26%2339%3Bbalanceador03%26%2339%3B
> system_db_hostname=%26%2339%3Blocalhost%26%2339%3B
> system_db_port = 5432
> system_db_dbname=%26%2339%3Bpgpool%26%2339%3B
> system_db_schema = 'pgpool_catalog'
> system_db_user = 'pgpool'
> system_db_password = ''
> backend_hostname0 = '15.120.190.12'
> backend_port0 = 5432
> backend_weight0 = 1
> backend_data_directory0 = '/var/lib/pgsql/data/'
> backend_hostname1 = '15.120.190.11'
> backend_port1 = 5432
> backend_weight1 = 1
> backend_data_directory1 = '/var/lib/pgsql/data/'
> enable_pool_hba = true
> recovery_user = 'pgpool2'
> recovery_password = ''
> recovery_1st_stage_command = 'base-backup'
> #recovery_1st_stage_command = ''
> recovery_2nd_stage_command = 'pgpool-recovery-pitr'
> #recovery_2nd_stage_command = ''
> recovery_timeout = 300
> client_idle_limit_in_recovery = 0
> lobj_lock_table = ''
> ssl = false
> debug_level = 0
> 
> 
> Mary
> ___
> Pgpool-general mailing list
> Pgpool-general@pgfoundry.org
> http://pgfoundry.org/mailman/listinfo/pgpool-general
___
Pgpool-general mailing list
Pgpool-general@pgfoundry.org
http://pgfoundry.org/mailman/listinfo/pgpool-general

Re: [Pgpool-general] Data not same on both nodes, streaming replication & load balancing

2011-09-20 Thread Tatsuo Ishii

Pgpool-II is not responsible for replication itself when operated with
streaming replication. Are you sure that streaming replicaton is
working? If so, you'd better to send questions to postgresql-general.
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese: http://www.sraoss.co.jp

> I have configuration pgpool streaming replication & load balancing
> configuration with two nodes.
> 
> pgpool version is 3.1.0-alpha2 (hatsuiboshi), postgres on both nodes is
> 9.0.4
> 
>  
> 
> Reason why I have use this version is that latest stable version (at
> that time) 3.0.1 was everything
> 
> but not stable.
> 
>  
> 
> Anyway.. I have situation now.. that my slave node is containing
> different data from master node.
> 
> I select something from master and get one result, and same query from
> slave and I get different result.
> 
>  
> 
> How to prevent this happening, and how it is possible that this
> happened.
> 
> How to know data my other data is health?
> 
>  
> 
> This is specific to PostgreSQL 9.x Streaming Replication. Please check:
> http://www.postgresql.org/docs/9.0/interactive/warm-standby.html#STREAMI
> NG-REPLICATION
> 
>  
> 
> -Daniel
> 
___
Pgpool-general mailing list
Pgpool-general@pgfoundry.org
http://pgfoundry.org/mailman/listinfo/pgpool-general

[Pgpool-general] Data not same on both nodes, streaming replication & load balancing

Re: [Pgpool-general] Data not same on both nodes, streaming replication & load balancing

Re: [Pgpool-general] seemingly hung pgpool process consuming 100% CPU

Re: [Pgpool-general] seemingly hung pgpool process consuming 100% CPU

[Pgpool-general] Pgpool-II connection problems when monitoring Heartbeat

Re: [Pgpool-general] Pgpool-II connection problems when monitoring Heartbeat

Re: [Pgpool-general] Pgpool-II connection problems when monitoring Heartbeat

Re: [Pgpool-general] Data not same on both nodes, streaming replication & load balancing

8 matches

Site Navigation

Mail list logo

Footer information