ld not be visible if you use the old mvcc. If you define this as an
> > > error then I think there will be conflicts.
> > >
> > > But at client side, there is guarantee that the request you send first
> > will
> > > be executed first. So as long as the re
if you about the write operation at
> different stages.
>
> Thanks.
>
> 2017-04-10 6:47 GMT+08:00 杨苏立 Yang Su Li :
>
> > We are trying to implement speculative rpc handling for our workloads. So
> > we want allow RPC Handler to stop executing an RPC call, put it back to
wrote:
> I don't know what your intention and your context are.
>
> You may get a different mvcc number and get different results next time
> around if there are concurrent writes.
>
> Thanks,
>
> Jerry
>
> On Sun, Apr 9, 2017 at 12:48 PM 杨苏立 Yang Su Li wrote:
&g
Hi,
I am wondering, for read requests like Get/MultiGet/Scan, is the RPC
handling idempotent in HBase?
More specifically, if in the middle of RPC handling we stop the handling
threads, puts the RPC call back to the queue, and later another RPC Handler
picks up this call and starts all over again,
Hi HBase Developers,
The previous email I sent seem to spur more conversion on the durability of
HBase rather than its overall architecture; so I think i would send another
email to plead comments on our architectural document (
http://pages.cs.wisc.edu/~suli/hbase.pdf) .
We are doing some researc
can simplify the reasoning
> of how fsync is implemented in hbase.
>
> hdfs was evaluated by the paper where I noticed the following:
>
> bq. both HDFS and ZooKeeper respondents lament that such an fsync() is not
> easily achievable with Java
>
> Cheers
>
> On Sun, Apr 2
t; currently is.
>>
>> Cheers
>>
>> On Sun, Apr 2, 2017 at 9:36 AM, 杨苏立 Yang Su Li
>> wrote:
>>
>> > Don't your second paragraph just prove my point? -- If data is not
>> > persisted to disk, then it is not durable. That is the definition
, including
the durability aspect.
On Sun, Apr 2, 2017 at 12:19 PM, Ted Yu wrote:
> Suli:
> Have you looked at HBASE-5954 ?
>
> It gives some background on why hbase code is formulated the way it
> currently is.
>
> Cheers
>
> On Sun, Apr 2, 2017 at 9:36 AM, 杨苏立 Yang Su
nk
> that data was durable when it actually wasn't (at the HDFS level).
>
> On Thu, Mar 30, 2017 at 4:26 PM, 杨苏立 Yang Su Li
> wrote:
> > Also, please correct me if I am wrong, but I don't think a put is durable
> > when an RPC returns to the client. Just its correspondi
t; total throughput drops.
>
> It is typical to run with 100-300 threads on the regionserver side,
> depending on your settings. You can use the "Debug dump" from the
> regionserver we UI or jstack to inspect what the "handler" threads are
> doing.
>
>
cluster.distsched-pg0.wisc.cloudlab.us
hbase.ipc.server.read.threadpool.size
10
hbase.regionserver.handler.count
30
>
> Cheers
>
> On Fri, Mar 31, 2017 at 7:29 PM, 杨苏立 Yang Su Li
> wrote:
>
> > Hi,
> >
> > We found that when there is a mix of CP
Hi,
We found that when there is a mix of CPU-intensive and I/O intensive
workload, HBase seems to slow everything down to the disk throughput level.
This is shown in the performance graph at
http://pages.cs.wisc.edu/~suli/blocking-orig.pdf : both client-1 and
client-2 are issuing 1KB Gets. From s
future would complete,
> what really happened is that the write/sync which included the caller's
> update was committed (along with others). All of this is happening inside
> the RS's implementation of accepting an update.
>
> https://github.com/apache/hbase/blob/55d6dcaf877
really happened is that the write/sync which included the caller's
> update was committed (along with others). All of this is happening inside
> the RS's implementation of accepting an update.
>
> https://github.com/apache/hbase/blob/55d6dcaf877cc5223e67973
> 6eb613173229c
t; On Mon, Mar 27, 2017 at 6:19 PM, 杨苏立 Yang Su Li
> wrote:
>
> > Hi,
> >
> > I am a graduate student working on scheduling on storage systems, and we
> > are interested in how different threads in HBase interact with each other
> > and how it might affect s
(attached). I am wondering if the developers of
HBase could take a look at it and let me know if anything is incorrect or
inaccurate, or if I have missed anything.
Thanks a lot for your help!
On Wed, Mar 22, 2017 at 3:39 PM, 杨苏立 Yang Su Li wrote:
> Hi,
>
> I am a graduate student working on s
Hi,
I am a graduate student working on scheduling on storage systems, and we
are interested in how different threads in HBase interact with each other
and how it might affect scheduling.
I have written down my understanding on how HBase/HDFS works based on its
current thread architecture (attache
17 matches
Mail list logo
