Home | About | Sematext search-lucene.com search-hadoop.com
 Search Hadoop and all its subprojects:

Switch to Plain View
HBase, mail # user - querying hbase


+
Aji Janis 2013-05-21, 21:58
+
Viral Bajaria 2013-05-21, 22:16
+
Aji Janis 2013-05-21, 22:43
+
lars hofhansl 2013-05-22, 03:35
+
Jean-Marc Spaggiari 2013-05-22, 03:41
+
Ian Varley 2013-05-22, 08:06
+
Shahab Yunus 2013-05-22, 13:12
+
Aji Janis 2013-05-22, 14:42
+
James Taylor 2013-05-22, 16:22
+
James Taylor 2013-05-22, 16:09
+
Jean-Marc Spaggiari 2013-05-23, 23:17
+
James Taylor 2013-05-24, 00:10
+
Andrew Purtell 2013-05-24, 21:50
+
Michel Segel 2013-06-01, 10:17
+
Andrew Purtell 2013-06-01, 10:44
Copy link to this message
-
Re: querying hbase
Michael Segel 2013-06-01, 18:15
Well,

What happens when you restart the RS?

Suppose I'm running a scan on a completely different table and you restart the RS?
What happens to me?

I havent thought through the whole problem, but you need to put each table's CP in to its own sandbox.
(There's more to it and would require some pizza, beer and a very large whiteboard....)
On Jun 1, 2013, at 5:44 AM, Andrew Purtell <[EMAIL PROTECTED]> wrote:

> Isn't the time to restart and the steps necessary more or less the same? Or
> will the objects that hold the in memory state survive across the reload?
> Will they still share a classloader (maintain equality tests)? What if the
> implementation / bundle version changes? We are taking about an upgrade
> scenario. Will we need to dump and restore in memory state to local disk,
> pickle the state of an earlier version and have the latest version
> unpickle, fixing up as needed? What happens if that fails midway?
> The JITted code for the old bundle is unused and GCed now that the bundle
> is upgraded, so we have to wait for runtime profiling and C2 to crunch the
> bytecode again for the new bundle. Will all that need more time than just
> restating a JVM ? Am I missing a simpler way?
>
> On Saturday, June 1, 2013, Michel Segel wrote:
>
>>> Is there a benefit to restarting a regionserver in an OSGi container
>> versus
>>> restarting a Java process?
>>
>> Was that rhetorical?
>>
>> Absolutely.
>> Think of a production environment where you are using HBase to serve data
>> in real time.
>>
>>
>> Sent from a remote device. Please excuse any typos...
>>
>> Mike Segel
>>
>> On May 24, 2013, at 4:50 PM, Andrew Purtell <[EMAIL PROTECTED]<javascript:;>>
>> wrote:
>>
>>> On Thu, May 23, 2013 at 5:10 PM, James Taylor <[EMAIL PROTECTED]<javascript:;>
>>> wrote:
>>>
>>>> Has there been any discussions on running the HBase server in an OSGi
>>>> container?
>>>
>>>
>>> I believe the only discussions have been on avoiding talk about
>> coprocessor
>>> reloading, as it implies either a reimplementation of or taking on an
>> OSGi
>>> runtime.
>>>
>>> Is there a benefit to restarting a regionserver in an OSGi container
>> versus
>>> restarting a Java process?
>>>
>>> Or would that work otherwise like an update the coprocessor and filters
>> in
>>> the container then trigger the embedded regionserver to do a quick close
>>> and reopen of the regions?
>>>
>>> --
>>> Best regards,
>>>
>>>  - Andy
>>>
>>> Problems worthy of attack prove their worth by hitting back. - Piet Hein
>>> (via Tom White)
>>
>
>
> --
> Best regards,
>
>   - Andy
>
> Problems worthy of attack prove their worth by hitting back. - Piet Hein
> (via Tom White)
+
James Taylor 2013-06-01, 20:20
+
Michael Segel 2013-06-02, 02:44
+
Andrew Purtell 2013-06-02, 10:42
+
Andrew Purtell 2013-06-02, 10:45
+
Andrew Purtell 2013-06-02, 10:59
+
James Taylor 2013-05-31, 23:31