is the top floor Lars. Otherwise, HBaseConEastBay -- Tacubaya,
Starline Social Club -- here we come (smile).
St.Ack
> -- Lars
>
> > On Feb 8, 2018, at 4:18 AM, Jean-Marc Spaggiari
> > <jean-m...@spaggiari.org>
> wrote:
> >
> > So who's jumping in for NY or
Huawei can continue to hold HBaseCon Asia 2018 :-)
Best Regards,
Jieshan.
-Original Message-
From: saint@gmail.com [mailto:saint@gmail.com] On Behalf Of Stack
Sent: 2018年2月8日 0:37
To: HBase Dev List
Subject: Re: HBaseCon Plans?
On Fri, Feb 2, 2018 at 9:13
Thanks for uploading all the slides and the good write-up, stackHope more
people will join us next year:)
Jieshan.
-Original Message-
From: saint@gmail.com [mailto:saint@gmail.com] On Behalf Of Stack
Sent: 2017年8月7日 23:12
To: HBase Dev List ; Hbase-User
for attending HBaseCon Asia 2017, please send email to me:
bijies...@huawei.com<mailto:bijies...@huawei.com>
Bijieshan.
Congratulations!
Jieshan.
-Original Message-
From: Anoop John [mailto:anoop.hb...@gmail.com]
Sent: 2017年4月14日 22:22
To: dev@hbase.apache.org; u...@hbase.apache.org
Cc: Yu Li
Subject: ANNOUNCE: Yu Li joins the Apache HBase PMC
On behalf of the Apache HBase PMC I"m
Nice find, zhoushuaifeng:)
Suggest to raise an issue for 94.
Jieshan.
From: 周帅锋 [zhoushuaif...@gmail.com]
Sent: Thursday, December 04, 2014 6:01 PM
To: dev
Subject: Re: split failed caused by FileNotFoundException
I rechecked the code in 0.98, this
But even with replicationSink, replicationSource still need to use RPC to
ship entries.
So, the potential problem you said may still occur.
Replication has its own handler, which is different from normal handlers.
You can check it from code:)
Jieshan.
1.
Why does HBase replication need replicationSink?
I think replicationSource can do replicationSink's work as well.
And if we don't use replicationSink, we just need one time I/O.
ReplicationSink used to apply all HLog edits to peer cluster. If we remove
ReplicationSink from current
Hi,
I think WritableRpcEngine$Invoker should not cache UGI. The intent behind this
design?
We encounter 1 problem due to client called User#login more than 1 times. The
error log:
14/05/08 15:44:40 FATAL ipc.SecureClient: SASL authentication failed. The most
likely cause is missing or
Sent again since I got no reply.
That's 1 problem we encountered due to calling User#login more than 1 times.
For your reference.
Jieshan.
-Original Message-
From: Bijieshan
Sent: Thursday, May 08, 2014 6:54 PM
To: dev@hbase.apache.org
Cc: Fanghao
Subject: WritableRpcEngine$Invoker
Congratulations, Liang Xie!
-Original Message-
From: saint@gmail.com [mailto:saint@gmail.com] On Behalf Of Stack
Sent: Thursday, December 19, 2013 8:47 AM
To: HBase Dev List
Subject: Please welcome our newest committer, Liang Xie!
谢良 has been doing great work for ages now; we're
Yes, it is only used for indicating which KVs to replicate. See
ReplicationSource#removeNonReplicableEdits.
bq.If they indicate which KVs to replicate, wouldn't it be better to store
bitmask or something like that?
Sounds like a good idea.
Regards,
Jieshan
-Original Message-
From:
Use shared ThreadPoolExecutor will not always good, e.g. when we do metaScan or
something else, we don't expect any delay due to no available threads in this
shared pool.
But that would always be a good practice for application-level.
It is individual opinion only:)
Jieshan
-Original
I would like to volunteer for client, Scan, Filter, Region Splitting, Create
Table(Table related operations)...
Thank you:)
Jieshan
-Original Message-
From: saint@gmail.com [mailto:saint@gmail.com] On Behalf Of Stack
Sent: Wednesday, September 19, 2012 6:15 AM
To:
Congratulations Liyin!
-Original Message-
From: saint@gmail.com [mailto:saint@gmail.com] On Behalf Of Stack
Sent: Thursday, May 17, 2012 12:04 PM
To: HBase Dev List
Subject: Please welcome our newest committer and PMC member, Liyin Tang
One of us Liyin!
Keep up the great work.
I think BinaryComparator will not give any help to achieve that goal(Because
it's not a number comparison).
You can try to customize your own comparator(Extend the class of
WritableByteArrayComparable), and write the rules of how to do that comparison.
And then using this comparator to do the
Hi all,
We found so many hlogs in our cluster, after some analysis, we also found one
splitted region occurred in HLog.lastSeqWritten. For this region had been
closed, it can't be flushed again. So blocking all the other logs removing to
.oldlogs directory.
05:06:44,422 INFO
Can you provide more detail on this 0.90.5 +, please ?
Did it include HBASE-5225 ?
Thanks
On Tue, Jan 24, 2012 at 8:55 PM, bijieshan bijies...@huawei.com wrote:
Hi all,
We found so many hlogs in our cluster, after some analysis, we also found
one splitted region occurred
of HBASE-5225.
Because in HBASE-5225 we tried to fix the case where the seq id is missed.
Here it is not missed it is still there in lastSeqWritten without getting
flushed.
Regards
Ram
-Original Message-
From: bijieshan [mailto:bijies...@huawei.com]
Sent: Wednesday, January 25
Hi all,
We use thousand of threads doing the scan operations. One thread got blocked at
the position of java.util.TreeMap.fixAfterDeletion. It can't come out of the
loop of TreeMap.fixAfterDeletion:
So I think it maybe a concurrency issue. Has someone encountered this?
Thank you.
Jieshan.
);
return null;
}
return value.get();
}
In this method, it can remove the element from internalMap which is a heapMap
from the backed TreeMap. A concurrency issue may happen from here.
Correct me if am wrong.
Thank you.
Jieshan.
发件人: bijieshan
发送时间: 2011年12月21日 18:48
收件人: dev
In my understanding, all the coprocessors are loaded in the initialization of
coprocessor environment, dynamic loading is not supported currently.
Maybe we can add this new feature.
Jieshan
--
发件人: Andrei Dragomir [mailto:adrag...@adobe.com]
发送时间: 2011年12月2日 17:07
收件人:
Thank you all.
I think it's the same problem with the link provided by Stack. Because the
heap-size is stabilized, but the non-heap size keep growing. So I think not the
problem of the CMS GC bug.
And we have known the content of the problem memory section, all the records
contains the info
I also hope this patch can be integrated into 0.90.
Thank you for your efforts on this issue:)
Jieshan.
-邮件原件-
发件人: Ted Yu [mailto:yuzhih...@gmail.com]
发送时间: 2011年11月3日 22:34
收件人: dev@hbase.apache.org; ramakrish...@huawei.com
主题: Re: Round Robin Assignment of enabling table HBASE-4669 -
Hi,
Under some scenarios, we use the function of disable/enable HTable. But
currently, enable HTable using the random-assignment. We hope all the regions
show a better distribution, no matter how many regions and how many
regionservers.
So I suggest to add a choice of using round-robin
Congratulations! Ram:)
-邮件原件-
发件人: Ramakrishna S Vasudevan 00902313 [mailto:ramakrish...@huawei.com]
发送时间: 2011年9月29日 2:36
收件人: dev@hbase.apache.org
抄送: dev@hbase.apache.org
主题: Re: Please welcome Ramkrishna S. Vasudevan, our newest hbase committer
Dear All
Thanks a lot.
Hope to do
About this failure, I've seen it several times. I didn't see the detail logs
for this one. But in my env, there's always some similar logs :
2011-09-02 09:33:57,517 INFO [RS_CLOSE_META-linux1.site,53487,1314927226948-0]
regionserver.HRegion(554): Closed .META.,,1.1028785192
2011-09-02
27 matches
Mail list logo