Altar for the most black priest

Pgpool-II 2.3 comming soon...

Today Tatsuo Ishii wrote interesting news at pgpool mailing list, version 2.3 coming this month.

What's new in 2.3:

- Adopt PostgreSQL 8.4 parser. On of the visible effects of this is,
 WITH clause can be load balanced.

- Allow to use INSERT/UPDATE including CURRENT_TIME_STAMP,
 CURRENT_DATE, now(). pgpool-II guarantees that each DB node will be
 populated exactly same value for these data type. For example
 consider following table:

 CREATE TABLE t1(id INTEGER PRIMARY KEY, regdate TIMESTAMP DEFAULT CURRENT_TIMESTAMP);

 Let's populate t1:

 INSERT INTO t1(id) VALUES(1);

 Actual query executed by pgpool-II is:

 INSERT INTO "t1"("id", "regdate") VALUES (1,'2009-11-15 21:35:01.783053+09');

 '2009-11-15 21:35:01.783053+09' is extraced from PostgreSQL by
 executing SELECT CURRENT_TIMESTAP. So t1 tables on all DB nodes has
 exactly same value.

- Add new directive log_per_node_statement.  If true, print all
 statements to the log. Similar to log_statement except that prints
 DB node id and backend process id info. Example:

 2009-11-15 21:34:12 LOG:   pid 22285: DB node id: 0 backend pid: 22301 statement: CREATE TABLE t1(id INTEGER PRIMARY KEY, regdate TIMESTAMP DEFAULT CURRENT_TIMESTAMP);
 2009-11-15 21:34:12 LOG:   pid 22285: DB node id: 1 backend pid: 22300 statement: CREATE TABLE t1(id INTEGER PRIMARY KEY, regdate TIMESTAMP DEFAULT CURRENT_TIMESTAMP);

Google Checkout over stunnel

Recently run HTTPS connection to website over stunnel + haproxy (not really important atm why such exotic idea). More important that hole operation goes smooth, quick and easy. Everything work until today when I read email from one of developers in over company.
He got problem with Google Checkout:

We encountered an error trying to access your server at https://some.website.at.web/GoogleCheckout/response -- 
the error we got is javax.net.ssl.SSLHandshakeException: Remote host closed connection during handshake

First I check connection with browser but everything looks ok as it should be. Start digg but google didn't help me alot. So I check Google Checkout documentation and find such thing:

There are also a number of measures you can take to keep your 
communications with Google Checkout secure:

    * Never share your Merchant Key with anyone.

    * Sign your shopping cart XML using HMAC SHA1 and your Merchant Key.
      Signing your shopping cart authenticates the cart you send and 
      verifies that your cart hasn't been tampered with during transmission.

    * Send order processing commands over a secure HTTPS connection.
      When sending order processing commands to Google, use an HTTPS connection
      secured by 128-bit SSL v3 or TLS connection (SSL v2 is not allowed). 
      Use your Merchant ID and Merchant Key as the username and password for 
      HTTP Basic Authentication.

    * Verify the authenticity of the server certificate presented to you.

    * Specify an HTTPS callback URL secured by SSL v3 or TLS using a valid
      certificate from a major Certifying Authority to receive Google notifications.
      Only accept messages authenticated by HTTP Basic Authentication, using 
      your Merchant ID and Merchant Key as the username and password. 
      Take a look at our list of accepted SSL certificates.

    * Validate messages sent to your callback URL before processing them.

Link

Looks still ok - SSL v3 or TLS . I recheck and SSL v3 is working. But Google Checkout doesn't like it.

Solution:

Change (/etc/stunnel/stunnel.conf)

; Protocol version (all, SSLv2, SSLv3, TLSv1)
sslVersion = SSLv3

to:

; Protocol version (all, SSLv2, SSLv3, TLSv1)
sslVersion = all

Because "SSLv3 or TLS" mean "SSLv3 and TLS" for google.

SSD #2

So today I could finally compare SUN SSD results with my SSD experience. I check two configurations:

- Dell R610, 12GB RAM, 4x50GB SSD RAID10
- Dell R610, 12GB RAM, 6x50GB SSD RAID10

SSD: SAMSUNG MCCOE50G Rev: 3D3Q

At both run clean CentOS with vdbench 5.01. Use same test as befor.

Tests
Server	i/o rate	MB/sec 1024**2	bytes i/o	read pct	resp time	resp max	resp stddev	cpu% sys+usr	cpu% sys
Random Read (4K) threads=32
HP DL360 G6 8x146GB SAS 15k RAID 10, 12GB RAM	2097,13	8,19	4096	100,00	15,257	407,631	13,818	0,3	0,2
HP DL360 G6 8x146GB SAS 15k RAID 50, 12GB RAM	1933,43	7,55	4096	100,00	16,549	416,267	15,998	0,3	0,2
DELL M600 2x146GB SAS 15K RAID1, 8GB RAM	595,50	2,33	4096	100,00	53,735	1313,692	66,092	0,2	0,2
DELL R610 4x50GB RAID10 12GB RAM SSD	16830,99	65,75	4096	100,00	1,9	28,730	0,566	1,8	1,7
DELL R610 6x50GB RAID10 12GB RAM SSD	18234,40	71,23	4096	100,00	1,753	22,646	0,439	2,1	1,9
Random Write (4K) threads=32
HP DL360 G6 8x146GB SAS 15k RAID 10, 12GB RAM	1963,12	7,67	4096	0,00	16,298	1511,424	15,338	0,4	0,3
HP DL360 G6 8x146GB SAS 15k RAID 50, 12GB RAM	1124,42	4,39	4096	0,00	28,457	1229,856	16,496	0,2	0,2
DELL M600 2x146GB SAS 15K RAID1, 8GB RAM	247,19	0,97	4096	0,00	129,457	1520,834	114,036	0,2	0,2
DELL R610 4x50GB RAID10 12GB RAM SSD	982,59	3,84	4096	0,00	32,564	339,488	16,693	0,3	0,3
DELL R610 6x50GB RAID10 12GB RAM SSD	1459,31	5,70	4096	0,00	21,926	243,077	10,288	0,2	0,2
50-50 Read/Write (4K) threads=32
HP DL360 G6 8x146GB SAS 15k RAID 10, 12GB RAM	1998,44	7,81	4096	50,03	16,010	702,082	29,572	0,3	0,3
HP DL360 G6 8x146GB SAS 15k RAID 50, 12GB RAM	1388,33	5,42	4096	50,02	23,047	1259,130	44,446	0,2	0,2
DELL M600 2x146GB SAS 15K RAID1, 8GB RAM	327,78	1,28	4096	49,95	97,625	1301,350	81,706	0,3	0,3
DELL R610 4x50GB RAID10 12GB RAM SSD	1674,78	6,54	4096	50,00	19,105	264,783	27,222	0,2	0,1
DELL R610 6x50GB RAID10 12GB RAM SSD	2413,06	9,43	4096	50,00	13,259	250,832	20,313	0,2	0,2
Sequential Read (MB/sec) threads=32
HP DL360 G6 8x146GB SAS 15k RAID 10, 12GB RAM	766,06	383,03	524288	100,00	41,769	1216,561	178,083	0,5	0,5
HP DL360 G6 8x146GB SAS 15k RAID 50, 12GB RAM	489,26	244,63	524288	100,00	65,407	2437,031	342,871	0,3	0,3
DELL M600 2x146GB SAS 15K RAID1, 8GB RAM	142,88	71,44	524288	100,00	223,902	1970,552	467,248	0,2	0,1
DELL R610 4x50GB RAID10 12GB RAM SSD	314,19	157,1	524288	100,00	101,837	980,956	275,867	0,1	0,1
DELL R610 6x50GB RAID10 12GB RAM SSD	453,45	226,72	524288	100,00	70,553	765,786	194,196	0,3	0,3
Sequential Write (MB/sec) threads=32
HP DL360 G6 8x146GB SAS 15k RAID 10, 12GB RAM	439,24	219,62	524288	0,00	72,853	590,213	46,006	0,2	0,2
HP DL360 G6 8x146GB SAS 15k RAID 50, 12GB RAM	1194,07	597,03	524288	0,00	26,797	155,358	5,514	0,6	0,6
DELL M600 2x146GB SAS 15K RAID1, 8GB RAM	140,25	70,13	524288	0,00	228,155	397,324	30,052	0,1	0,1
DELL R610 4x50GB RAID10 12GB RAM SSD	247,72	123,86	524288	0,00	129,175	244,959	14,121	0,1	0,1
DELL R610 6x50GB RAID10 12GB RAM SSD	370,52	185,26	524288	0,00	86,363	213,793	9,973	0,2	0,1

I have to say that's not impressive at all. True, reads are nice, but come on, writes 12x times slower ?!? It's really far far from ok.

Maybe it's Dell firmware, but atm I got latest firmware every part.

Back from holidays can be scary ;-D