Problema con Pgbench y Pgpool-II

From: Lazaro Rubén García Martinez <lgarciam(at)vnz(dot)uci(dot)cu>
To: "pgsql-es-ayuda(at)postgresql(dot)org" <pgsql-es-ayuda(at)postgresql(dot)org>
Subject: Problema con Pgbench y Pgpool-II
Date: 2011-06-06 15:22:23
Message-ID: 294D3D02D5E18D42827B2ECFEADEB6880BE1F2DCAB@mx-interno.vnz.uci.cu
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-es-ayuda

Hola a todos en la lista, les escribo porque tengo un problema cuando trato de probar el balance de carga de Pgpool-II con Pgbench. Sucede que mientras los nodos de base de datos están activos, todo funciona correctamente pero si durante la ejecución de la prueba detengo uno de los servidores, entonces la prueba falla. Lo que no comprendo es que normalmente cuando los clientes se concetan a la base a traves de pgpool-II, y uno de los nodos fallase, pgpool realiza failover y todo continua funcionando de forma tranparente al usuario, sin embargo mediante pgbech no ocurre lo mismo. Sería de gran ayuda para mi si me pudieran ayudar a entender que es lo que está sucediendo. El mensaje que arroja la ejecución de la prueba es el siguiente:

pgbench -U postgres -h 10.13.4.200 -p 9999 -n -f /home/pasaporte/Desktop/tesisPredefensa/balanceCarga/test.sql -c 80 -t 100 tesis
Password:
Client 23 aborted in state 2: FATAL: terminating connection due to administrator command
Client 25 aborted in state 2: FATAL: terminating connection due to administrator command
Client 41 aborted in state 1: FATAL: terminating connection due to administrator command
Client 52 aborted in state 1: FATAL: terminating connection due to administrator command
Client 58 aborted in state 0: FATAL: terminating connection due to administrator command
Client 67 aborted in state 2: FATAL: terminating connection due to administrator command
Client 70 aborted in state 2: FATAL: terminating connection due to administrator command
Client 71 aborted in state 0: FATAL: terminating connection due to administrator command
Client 77 aborted in state 2. Probably the backend died while processing.
Client 0 aborted in state 2. Probably the backend died while processing.
Client 1 aborted in state 0. Probably the backend died while processing.
Client 2 aborted in state 0. Probably the backend died while processing.
Client 3 aborted in state 0. Probably the backend died while processing.
Client 4 aborted in state 3. Probably the backend died while processing.
Client 5 aborted in state 2. Probably the backend died while processing.
Client 7 aborted in state 1. Probably the backend died while processing.
Client 8 aborted in state 3. Probably the backend died while processing.
Client 9 aborted in state 0. Probably the backend died while processing.
Client 10 aborted in state 1. Probably the backend died while processing.
Client 11 aborted in state 0. Probably the backend died while processing.
Client 12 aborted in state 0. Probably the backend died while processing.
Client 13 aborted in state 0. Probably the backend died while processing.
Client 14 aborted in state 0. Probably the backend died while processing.
Client 16 aborted in state 1. Probably the backend died while processing.
Client 17 aborted in state 3. Probably the backend died while processing.
Client 18 aborted in state 2. Probably the backend died while processing.
Client 19 aborted in state 0. Probably the backend died while processing.
Client 20 aborted in state 3. Probably the backend died while processing.
Client 21 aborted in state 2. Probably the backend died while processing.
Client 22 aborted in state 0. Probably the backend died while processing.
Client 24 aborted in state 0. Probably the backend died while processing.
Client 26 aborted in state 1. Probably the backend died while processing.
Client 27 aborted in state 1. Probably the backend died while processing.
Client 28 aborted in state 1. Probably the backend died while processing.
Client 30 aborted in state 2. Probably the backend died while processing.
Client 31 aborted in state 2. Probably the backend died while processing.
Client 33 aborted in state 1. Probably the backend died while processing.
Client 34 aborted in state 2. Probably the backend died while processing.
Client 35 aborted in state 0. Probably the backend died while processing.
Client 36 aborted in state 2. Probably the backend died while processing.
Client 37 aborted in state 3. Probably the backend died while processing.
Client 38 aborted in state 1. Probably the backend died while processing.
Client 39 aborted in state 1. Probably the backend died while processing.
Client 40 aborted in state 2. Probably the backend died while processing.
Client 42 aborted in state 0. Probably the backend died while processing.
Client 43 aborted in state 0. Probably the backend died while processing.
Client 44 aborted in state 1. Probably the backend died while processing.
Client 45 aborted in state 3. Probably the backend died while processing.
Client 46 aborted in state 3. Probably the backend died while processing.
Client 47 aborted in state 1. Probably the backend died while processing.
Client 48 aborted in state 0. Probably the backend died while processing.
Client 50 aborted in state 1. Probably the backend died while processing.
Client 51 aborted in state 2. Probably the backend died while processing.
Client 53 aborted in state 2. Probably the backend died while processing.
Client 54 aborted in state 0. Probably the backend died while processing.
Client 56 aborted in state 1. Probably the backend died while processing.
Client 57 aborted in state 1. Probably the backend died while processing.
Client 59 aborted in state 3. Probably the backend died while processing.
Client 60 aborted in state 2. Probably the backend died while processing.
Client 61 aborted in state 2. Probably the backend died while processing.
Client 62 aborted in state 3. Probably the backend died while processing.
Client 63 aborted in state 3. Probably the backend died while processing.
Client 64 aborted in state 1. Probably the backend died while processing.
Client 65 aborted in state 2. Probably the backend died while processing.
Client 66 aborted in state 3. Probably the backend died while processing.
Client 68 aborted in state 2. Probably the backend died while processing.
Client 69 aborted in state 1. Probably the backend died while processing.
Client 72 aborted in state 1. Probably the backend died while processing.
Client 73 aborted in state 0. Probably the backend died while processing.
Client 74 aborted in state 1. Probably the backend died while processing.
Client 75 aborted in state 0. Probably the backend died while processing.
Client 76 aborted in state 3. Probably the backend died while processing.
Client 78 aborted in state 2. Probably the backend died while processing.
Client 79 aborted in state 0. Probably the backend died while processing.
Client 6 aborted in state 3. Probably the backend died while processing.
Client 15 aborted in state 1. Probably the backend died while processing.
Client 29 aborted in state 3. Probably the backend died while processing.
Client 32 aborted in state 2. Probably the backend died while processing.
Client 49 aborted in state 0. Probably the backend died while processing.
Client 55 aborted in state 1. Probably the backend died while processing.
transaction type: Custom query
scaling factor: 1
number of clients: 80
number of transactions per client: 100
number of transactions actually processed: 1263/8000
tps = 72.758393 (including connections establishing)
tps = 79.386750 (excluding connections establishing)

Saludos y muchas gracias por su tiempo.

Responses

Browse pgsql-es-ayuda by date

  From Date Subject
Next Message Eduardo Morras 2011-06-06 15:40:59 Re: Tablas no modificables
Previous Message Jaime Casanova 2011-06-05 19:24:44 Re: No suficiente espacio en Disco