Mailing-List: contact user-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@hbase.apache.org
Received-SPF: pass (nike.apache.org: domain of tsunanet@gmail.com designates
 209.85.214.173 as permitted sender)
MIME-Version: 1.0
From: tsuna <tsunanet@gmail.com>
Date: Mon, 9 Dec 2013 21:46:16 -0800
Message-ID: 
 <CAFKYj4fgm2G14XzWmjSCVm0RZvU2-fBGqbEhYvL44ho4FgYwQA@mail.gmail.com>
Subject: Giving a chance to buggy coprocessors to clean up
To: HBase users <user@hbase.apache.org>
Content-Type: text/plain; charset=ISO-8859-1

Hi there,
If a coprocessor is buggy and throws an uncaught exception, it gets
removed without having its stop() method called, and it therefore
can't free up resources.

Any resources that are held by global variables (e.g. statics on a
class loaded by the coprocessor) can't be freed because of bug
HBASE-9046 (Coprocessors can't be upgraded in service reliably). And
the coprocessor can't be removed because of HBASE-9046.  Therefore
there is no way that I can see to release those resources, short of
restarting the RegionServer (yikes!).

Is there any rationale behind not calling stop() when forcefully
removing the buggy coprocessor?  Or should we maybe add some sort of a
cleanUp() method to give a chance to the coprocessor to save face and
die gracefully?

-- 
Benoit "tsuna" Sigoure