KiokuDB::Backend::BDB and replication

[email protected] (atomicstack) Mon, 25 May 2009 04:13:26 +1000
Newsgroups perl.kiokudb
Message-ID <[email protected]>
--0016e644cd6032b9e2046aac7347
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

I notice BerkeleyDB::Manager has attributes for replication, but no mention
in the documentation. Has anybody had luck using it in a replicated
environment? I'm tinkering with MemcacheDB but the tests seem to fail when
BDB::Manager calls BerkeleyDB::Hash->new. My XS knowledge isn't great so I'm
not sure where/how to start digging into BerkeleyDB to see if it's honouring
the replication flags properly...

[matt@quark KiokuDB-Backend-BDB-0.14-IP_2km] prove -Ilib
t/bdb_backend.t
t/bdb_backend.t .. 1/?
start $flags: 256 at /home/matt/perl-5.10/lib/BerkeleyDB/Manager.pm line
138.
has: log lock replication transactions recover create
end $flags: 18385 at /home/matt/perl-5.10/lib/BerkeleyDB/Manager.pm line
172.
BerkeleyDB::Hash->new at /home/matt/perl-5.10/lib/BerkeleyDB/Manager.pm line
377.
Non-replication DB_ENV handle attempting to modify a replicated environment
at /home/matt/perl-5.10/lib/BerkeleyDB/Manager.pm line 379.
# Looks like your test exited with 17 just after 4.
t/bdb_backend.t .. Dubious, test returned 17 (wstat 4352, 0x1100)
All 4 subtests passed

Test Summary Report
-------------------
t/bdb_backend.t (Wstat: 4352 Tests: 4 Failed: 0)
  Non-zero exit status: 17
Files=1, Tests=4,  1 wallclock secs ( 0.02 usr  0.00 sys +  0.50 cusr  0.01
csys =  0.53 CPU)
Result: FAIL

--0016e644cd6032b9e2046aac7347--