,
Hayden
From: iain wright iainw...@gmail.com
Sent: Wednesday, October 29, 2014 1:51 AM
To: user@hbase.apache.org
Subject: Re: Upgrading a coprocessor
Hi Hayden,
We ran into the same thing ended up going with a rudimentary cp deploy
script
strategies?)
Thanks,
Hayden
From: iain wright iainw...@gmail.com
Sent: Wednesday, October 29, 2014 1:51 AM
To: user@hbase.apache.org
Subject: Re: Upgrading a coprocessor
Hi Hayden,
We ran into the same thing ended up going with a rudimentary cp deploy
Sent: Wednesday, October 29, 2014 1:51 AM
To: user@hbase.apache.org
Subject: Re: Upgrading a coprocessor
Hi Hayden,
We ran into the same thing ended up going with a rudimentary cp deploy
script for appending epoch to the cp name, placing on hdfs, and
disabling/modifying hbase table
,
Hayden
From: iain wright iainw...@gmail.com
Sent: Wednesday, October 29, 2014 1:51 AM
To: user@hbase.apache.org
Subject: Re: Upgrading a coprocessor
Hi Hayden,
We ran into the same thing ended up going with a rudimentary cp deploy
script
@hbase.apache.org
Subject: Re: Upgrading a coprocessor
Hi Hayden,
We ran into the same thing ended up going with a rudimentary cp deploy
script for appending epoch to the cp name, placing on hdfs, and
disabling/modifying hbase table/enabling
Heres the issue for this: https
and I see that it is forever
holding a classloaderCache with no mechanism for clearing it out.
I assume that if I restart the region server it will take the new version of my
coprocessor.
Is there any workaround for upgrading a coprocessor without either changing the
path, or restarting
holding a classloaderCache with no mechanism for clearing it out.
I assume that if I restart the region server it will take the new version
of my coprocessor.
Is there any workaround for upgrading a coprocessor without either
changing the path, or restarting the HBase region server?
Thanks
with no mechanism for clearing it out.
I assume that if I restart the region server it will take the new version
of my coprocessor.
Is there any workaround for upgrading a coprocessor without either
changing the path, or restarting the HBase region server?
Thanks,
Hayden
--
Bharath
with no mechanism for clearing it out.
I assume that if I restart the region server it will take the new version
of my coprocessor.
Is there any workaround for upgrading a coprocessor without either
changing the path, or restarting the HBase region server?
Thanks,
Hayden
A rolling restart across all region server would reload all the latest classes.
That is currently the best option, IMHO.
-- Lars
From: Mike Axiak m...@axiak.net
To: user@hbase.apache.org
Sent: Tuesday, October 28, 2014 7:03 PM
Subject: Re: Upgrading a coprocessor
Because
10 matches
Mail list logo