[
https://issues.apache.org/jira/browse/HBASE-16438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15927705#comment-15927705
]
Anastasia Braginsky commented on HBASE-16438:
---------------------------------------------
Hi [~ram_krish],
I understand that you have already done some refactoring work for Chunks
creation/allocation. I appreciate it a lot! I just thought may be it can be
quicker and easier for you if I do the creator/allocator. But if you have the
new design/patch already then just go ahead. Do you mind to publish the new
code on RB? BTW if you are using the lock to synchronize the threads asking for
the current chunk in one MSLAB, then why do you need CAS there as well?
[~anoop.hbase], I also looked on that code and thought there is a bug there! :)
But then realized it is OK due to this UNINITIALIZED. This is why I am saying
we do not add any new delay here in chunks allocation. Anyway if two or more
threads need new chunk one is initializing and the rest are waiting...
> Create a cell type so that chunk id is embedded in it
> -----------------------------------------------------
>
> Key: HBASE-16438
> URL: https://issues.apache.org/jira/browse/HBASE-16438
> Project: HBase
> Issue Type: Sub-task
> Affects Versions: 2.0.0
> Reporter: ramkrishna.s.vasudevan
> Assignee: ramkrishna.s.vasudevan
> Attachments: HBASE-16438_1.patch, HBASE-16438.patch,
> MemstoreChunkCell_memstoreChunkCreator_oldversion.patch,
> MemstoreChunkCell_trunk.patch
>
>
> For CellChunkMap we may need a cell such that the chunk out of which it was
> created, the id of the chunk be embedded in it so that when doing flattening
> we can use the chunk id as a meta data. More details will follow once the
> initial tasks are completed.
> Why we need to embed the chunkid in the Cell is described by [~anastas] in
> this remark over in parent issue
> https://issues.apache.org/jira/browse/HBASE-14921?focusedCommentId=15244119&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15244119
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
