Mailing-List: contact user-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@hbase.apache.org
Received-SPF: pass (athena.apache.org: domain of gcjhhu-hbase-user@m.gmane.org
 designates 80.91.229.12 as permitted sender)
To: user@hbase.apache.org
From: Andrey Timerbaev <atimerbaev@gmx.net>
Subject: Re: RegionServer can't recover after a failure
Date: Mon, 30 Aug 2010 07:16:11 +0000 (UTC)
Lines: 23
Message-ID: <loom.20100830T090522-4@post.gmane.org>
References: <loom.20100826T161659-347@post.gmane.org>
 <B85005F4-A4B6-48DD-A72E-0A8D42E211AE@troove.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
User-Agent: Loom/3.14 (http://gmane.org/)

> The issue is that the global transaction log table is not created yet. You can
do so simply by calling
> HBaseBackedTransactionLogger.createTable() at the time when you are seeding
the rest of your tables.

> James Kennedy
> Project Manager
> Troove Inc.

Hello James,

Thank you for the comment. Do I understand right, that the createTable() method
should be called before the very first transaction performed? In other words, in
our situation, when region servers report "Region
log has 9 unfinished transactions" and the just created table __GLOBAL_TRX_LOG__
exists, but it's empty, this won't help?

Maybe, just for the moment we can clean the log, where the number of unfinished
transactions is logged? And then maybe RegionServers won't try to recover the
unfinished transactions? Could you kindly suggest, where it is logged?

Thank you,
Andrey