[ 
https://issues.apache.org/jira/browse/HBASE-5782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13255329#comment-13255329
 ] 

ramkrishna.s.vasudevan commented on HBASE-5782:
-----------------------------------------------

@Lars
Correct me if am wrong.  
Currently the edits are ordered atleast in the memory so that the store file 
that is persisted is having the proper sequence number.
But it is when applying it to the WAL there is a change and the same needs to 
be taken care while replaying.  
Is there any special consideration needed that my edits have to ordered even in 
the WAL file? What is the design consideration behind this?
May be am missing something here.
@Stack
This patch is one similar to the one i had in mind.  Synchronize 
getPendingWrites and the 'writer.append(e);'.
                
> Edits can be appended out of seqid order since HBASE-4487
> ---------------------------------------------------------
>
>                 Key: HBASE-5782
>                 URL: https://issues.apache.org/jira/browse/HBASE-5782
>             Project: HBase
>          Issue Type: Bug
>          Components: wal
>    Affects Versions: 0.94.0
>            Reporter: Gopinathan A
>            Assignee: ramkrishna.s.vasudevan
>            Priority: Blocker
>             Fix For: 0.94.0
>
>         Attachments: 5782-sketch.txt, 5782.txt, 5782.unfinished-stack.txt, 
> HBASE-5782.patch
>
>
> Create a table with 1000 splits, after the region assignemnt, kill the 
> regionserver wich contains META table.
> Here few regions are missing after the log splitting and region assigment. 
> HBCK report shows multiple region holes are got created.
> Same scenario was verified mulitple times in 0.92.1, no issues.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to