www.infinidb.org

Hi,

I'm trying to install InfiniDB on an Amazon EC2 instance using the provided 1.0.3 RPMs. All goes well until after installing I log into idbmysql and execute a CREATE TABLE statement:

mysql> create table summary (id INT) engine=InfiniDB;
ERROR 122 (HY000): CAL0001: Create table Failed: DDLPackageProcessor::writeSysTableMetaData WE: Error updating calpont.systable: a BRM get hwm error.

Having read several threads with similar issues, I've tried reinstalling with no success.

Taken from suggestions from other threads that hopefully will help diagnose my issues:

# /usr/local/Calpont/bin/dbrmctl status
OK.

# /usr/local/Calpont/bin/editem -d
# See attachment for output

SysLog-NG (as configured using www.infinidb.org/community/forums/6-inst...f-for-infinidb-usage) gives the following:

# crit.log
Mar 10 03:50:04 domU-xxxxxxxxxx ddlpackageproc[16005]: 04.409393 |0|0|0| C 23 CAL0001: Create table Failed: DDLPackageProcessor::writeSysTableMetaData WE: Error updating calpont.systable: a BRM get hwm error.

# debug.log
Mar 10 03:50:04 domU-xxxxxxxxxx ddlpackageproc[16005]: 04.333134 |1|12|0| D 23 CAL0041: Start SQL statement: create table summary (id INT) ENGINE=InfiniDB;
Mar 10 03:50:04 domU-xxxxxxxxxx ddlpackageproc[16005]: 04.335141 |1|12|0| D 23 CAL0042: End SQL statement

# info.log
Mar 10 03:49:39 domU-xxxxxxxxxx DMLProc[16144]: 39.662944 |0|0|0| I 20 CAL0002: DMLProc starts bulk roll back.
Mar 10 03:49:39 domU-xxxxxxxxxx DMLProc[16144]: 39.663946 |0|0|0| I 20 CAL0002: No table need rollback
Mar 10 03:49:39 domU-xxxxxxxxxx messagequeue[16144]: 39.833426 |0|0|0| I 20 CAL0002: DMLProc finished bulk roll back.
Mar 10 03:49:39 domU-xxxxxxxxxx DMLProc[16144]: 39.845769 |0|0|0| I 20 CAL0002: DMLProc starts rollbackAll transactions.
Mar 10 03:49:40 domU-xxxxxxxxxx DMLProc[16144]: 40.135791 |0|0|0| I 20 CAL0002: DMLProc finished rollbackAll transactions.


Any help much appreciated. Thanks in advance!

Thanks for downloading and checking InfiniDB out.

You did a very good job in checking the forum and providing the information we usually request.

From the information you provided, especially with the editem dump, the data looks correct and there is nothing that explains the problem you are having.

The issue could be Amazon EC2 environment related. We have plans to perform an installation and functionality test on an Amazon EC2 system within the next week's timeframe.

So we should be able to post some results from that testing within the next week or so.

David

We successfully performed an install of the InfiniDB 1.0.3 in an Amazon EC2 environment. We did run into an issue with the logging that required a little work it get working, but nothing special was required to get the query engine functionality to work.

We used the following instance for our testing:

Basic 64-bit Fedora Core 8

NDavies, if you are still monitoring the thread, could you let us know the type of instance you were using? We would like to followup with your issue to see if we could reproduce if in a different instance type.

Or if you decide to give the install another shot, please let us know how it works.

Thanks, David

I got the same error, too.



Server version: 5.1.39 MySQL Community
InfiniDB Community Edition 1.0.4-3 Final (GPL)

OS: Ubuntu 9.10 x86_64

Could you help me? please!

This error generally means that there was an issue related to the installattion of the system catalog data.

A couple of utilities that will help diagnose the problem.

Please check the outputs of these commands:
/usr/local/Calpont/bin/dbrmctl status
/usr/local/Calpont/bin/editem -d

The first will give the status from the distributed block resolution manager and the second will display the contents of the extent map.

If the editem call does not return anything, this indicates that the installation did not complete successfully.

Can you out the contents of these log files, if they exist:

cat /tmp/dbbuilder.status
cat /tmp/dbbuilder.log

Thanks for your reply,davidhill.

I've changed to version 1.1.0-1, it works fine!





Thanks.