Re: Questions about synchronization in compaction pipeline

Hi Mike, Thanks for being interested in the CompactionPipeline implementation. It is pleasure to discuss it with you. Regarding that we are implementing our own copy-on-write (COW) list. May be it is close, but in classic COW, everybody is sharing the same read-only copy and when someone tries

[jira] [Created] (HBASE-20173) [AMv2] DisableTableProcedure concurrent to ServerCrashProcedure can deadlock

stack created HBASE-20173: - Summary: [AMv2] DisableTableProcedure concurrent to ServerCrashProcedure can deadlock Key: HBASE-20173 URL: https://issues.apache.org/jira/browse/HBASE-20173 Project: HBase

Re: Questions about synchronization in compaction pipeline

Replacing with ArrayDeque wouldn't be straight forward since it implements Deque interface where there is no method for accessing given index. ArrayDeque provides remove by Object: public boolean remove(Object o) { return removeFirstOccurrence(o); After the removal, add() or

Re: Questions about synchronization in compaction pipeline

> LL copy is fairly slow and likely loses us any gains. Also, I'm a little > dubious on the use of LL given that we support a replaceAtIndex which will > be much faster in an array. > > Can we improve by using an ArrayDeque? Does ArrayDeque support to change element by arbitrary index? If not, it

Re: [VOTE] First release candidate for HBase 1.3.2 (RC0) is available

Thanks Ted. You are right. TestEndToEndSplitTransaction works well now. On 2018/03/10 15:47:58, Ted Yu wrote: > I checked out latest branch-1.3 where TestEndToEndSplitTransaction passes > nicely. > > Looking at the commits that came in after Francis' tag, I think the >

[jira] [Created] (HBASE-20172) During coprocessor load, switch classloader only if it's a custom CP.

Ankit Singhal created HBASE-20172: - Summary: During coprocessor load, switch classloader only if it's a custom CP. Key: HBASE-20172 URL: https://issues.apache.org/jira/browse/HBASE-20172 Project: