[jira] [Commented] (HBASE-3845) data loss because lastSeqWritten can miss memstore edits

[ https://issues.apache.org/jira/browse/HBASE-3845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13069405#comment-13069405 ] ramkrishna.s.vasudevan commented on HBASE-3845: --- @Stack, Thanks for the comm

[jira] [Commented] (HBASE-4095) Hlog may not be rolled in a long time if checkLowReplication's request of LogRoll is blocked

[ https://issues.apache.org/jira/browse/HBASE-4095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13069404#comment-13069404 ] Jieshan Bean commented on HBASE-4095: - I don't know why it got blocked for a long time

[jira] [Commented] (HBASE-4095) Hlog may not be rolled in a long time if checkLowReplication's request of LogRoll is blocked

[ https://issues.apache.org/jira/browse/HBASE-4095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13069403#comment-13069403 ] stack commented on HBASE-4095: -- You say "But the rollWriter may be blocked this time" Why is

[jira] [Updated] (HBASE-4095) Hlog may not be rolled in a long time if checkLowReplication's request of LogRoll is blocked

[ https://issues.apache.org/jira/browse/HBASE-4095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jieshan Bean updated HBASE-4095: Attachment: hbase-root-regionserver-193-195-5-111.rar I attached the full logs of the regionserver

[jira] [Commented] (HBASE-4095) Hlog may not be rolled in a long time if checkLowReplication's request of LogRoll is blocked

[ https://issues.apache.org/jira/browse/HBASE-4095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13069397#comment-13069397 ] stack commented on HBASE-4095: -- "But if rollWriter is blocked, all the following roll will be

[jira] [Commented] (HBASE-4095) Hlog may not be rolled in a long time if checkLowReplication's request of LogRoll is blocked

[ https://issues.apache.org/jira/browse/HBASE-4095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13069399#comment-13069399 ] stack commented on HBASE-4095: -- Oh, ok. I was unable to follow what was going on. Mixing up

[jira] [Commented] (HBASE-4095) Hlog may not be rolled in a long time if checkLowReplication's request of LogRoll is blocked

[ https://issues.apache.org/jira/browse/HBASE-4095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13069396#comment-13069396 ] Jieshan Bean commented on HBASE-4095: - Sorry for misunderstood your comments about the

[jira] [Commented] (HBASE-1730) Near-instantaneous online schema and table state updates

[ https://issues.apache.org/jira/browse/HBASE-1730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13069395#comment-13069395 ] stack commented on HBASE-1730: -- Dhruba: You can ignore the attached patches. They and the d

[jira] [Commented] (HBASE-4095) Hlog may not be rolled in a long time if checkLowReplication's request of LogRoll is blocked

[ https://issues.apache.org/jira/browse/HBASE-4095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13069393#comment-13069393 ] Jieshan Bean commented on HBASE-4095: - About the report, I mixed up several tests. For

[jira] [Commented] (HBASE-4095) Hlog may not be rolled in a long time if checkLowReplication's request of LogRoll is blocked

[ https://issues.apache.org/jira/browse/HBASE-4095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13069390#comment-13069390 ] stack commented on HBASE-4095: -- Jieshan. Is there something messed up in the logs you report

[jira] [Commented] (HBASE-3845) data loss because lastSeqWritten can miss memstore edits

[ https://issues.apache.org/jira/browse/HBASE-3845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13069385#comment-13069385 ] dhruba borthakur commented on HBASE-3845: - Hi Prakash, would you like to review th

[jira] [Commented] (HBASE-3845) data loss because lastSeqWritten can miss memstore edits

[ https://issues.apache.org/jira/browse/HBASE-3845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13069383#comment-13069383 ] stack commented on HBASE-3845: -- Ram: After setting wal.setFlushInProgress(true);, should we

[jira] [Updated] (HBASE-3845) data loss because lastSeqWritten can miss memstore edits

[ https://issues.apache.org/jira/browse/HBASE-3845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan updated HBASE-3845: -- Attachment: HBASE-3845_2.patch > data loss because lastSeqWritten can miss mems

[jira] [Commented] (HBASE-3845) data loss because lastSeqWritten can miss memstore edits

[ https://issues.apache.org/jira/browse/HBASE-3845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13069380#comment-13069380 ] ramkrishna.s.vasudevan commented on HBASE-3845: --- @Ted, I think the file got

[jira] [Updated] (HBASE-3845) data loss because lastSeqWritten can miss memstore edits

[ https://issues.apache.org/jira/browse/HBASE-3845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan updated HBASE-3845: -- Status: Open (was: Patch Available) > data loss because lastSeqWritten can mis

[jira] [Commented] (HBASE-3857) Change the HFile Format

[ https://issues.apache.org/jira/browse/HBASE-3857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13069377#comment-13069377 ] stack commented on HBASE-3857: -- Resolve hbase-3417 when this goes in. This subsumes it. > C

[jira] [Commented] (HBASE-4122) improve hbck tool to fix .META. hole issue.

[ https://issues.apache.org/jira/browse/HBASE-4122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13069365#comment-13069365 ] Jieshan Bean commented on HBASE-4122: - Two suggestions about the patch: 1. I think cha

[jira] [Updated] (HBASE-4095) Hlog may not be rolled in a long time if checkLowReplication's request of LogRoll is blocked

[ https://issues.apache.org/jira/browse/HBASE-4095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jieshan Bean updated HBASE-4095: Attachment: surefire-report-branch.html HBASE-4095-trunk-V3.patch HB

[jira] [Commented] (HBASE-3899) enhance HBase RPC to support free-ing up server handler threads even if response is not ready

[ https://issues.apache.org/jira/browse/HBASE-3899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13069311#comment-13069311 ] jirapos...@reviews.apache.org commented on HBASE-3899: --

[jira] [Commented] (HBASE-3899) enhance HBase RPC to support free-ing up server handler threads even if response is not ready

[ https://issues.apache.org/jira/browse/HBASE-3899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13069312#comment-13069312 ] jirapos...@reviews.apache.org commented on HBASE-3899: -- bq. On 201

[jira] [Commented] (HBASE-3899) enhance HBase RPC to support free-ing up server handler threads even if response is not ready

[ https://issues.apache.org/jira/browse/HBASE-3899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13069230#comment-13069230 ] jirapos...@reviews.apache.org commented on HBASE-3899: -- bq. On 201

[jira] [Commented] (HBASE-3899) enhance HBase RPC to support free-ing up server handler threads even if response is not ready

[ https://issues.apache.org/jira/browse/HBASE-3899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13069227#comment-13069227 ] jirapos...@reviews.apache.org commented on HBASE-3899: --

[jira] [Commented] (HBASE-3899) enhance HBase RPC to support free-ing up server handler threads even if response is not ready

[ https://issues.apache.org/jira/browse/HBASE-3899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13069223#comment-13069223 ] jirapos...@reviews.apache.org commented on HBASE-3899: --

[jira] [Commented] (HBASE-3417) CacheOnWrite is using the temporary output path for block names, need to use a more consistent block naming scheme

[ https://issues.apache.org/jira/browse/HBASE-3417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13069216#comment-13069216 ] Mikhail Bautin commented on HBASE-3417: --- @stack: This patch is already part of HFile

[jira] [Commented] (HBASE-3417) CacheOnWrite is using the temporary output path for block names, need to use a more consistent block naming scheme

[ https://issues.apache.org/jira/browse/HBASE-3417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13069204#comment-13069204 ] Jonathan Gray commented on HBASE-3417: -- It does support COW but if it doesn't include

[jira] [Commented] (HBASE-3899) enhance HBase RPC to support free-ing up server handler threads even if response is not ready

[ https://issues.apache.org/jira/browse/HBASE-3899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13069194#comment-13069194 ] jirapos...@reviews.apache.org commented on HBASE-3899: --

[jira] [Commented] (HBASE-3845) data loss because lastSeqWritten can miss memstore edits

[ https://issues.apache.org/jira/browse/HBASE-3845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13069107#comment-13069107 ] Ted Yu commented on HBASE-3845: --- Patch doesn't apply cleanly on 0.90: {noformat} patching fi

[jira] [Commented] (HBASE-4064) Two concurrent unassigning of the same region caused the endless loop of "Region has been PENDING_CLOSE for too long..."

[ https://issues.apache.org/jira/browse/HBASE-4064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13069100#comment-13069100 ] stack commented on HBASE-4064: -- Yah! J-D is back! > Two concurrent unassigning of the same

[jira] [Commented] (HBASE-4064) Two concurrent unassigning of the same region caused the endless loop of "Region has been PENDING_CLOSE for too long..."

[ https://issues.apache.org/jira/browse/HBASE-4064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13069098#comment-13069098 ] Jean-Daniel Cryans commented on HBASE-4064: --- This work should really be done for

[jira] [Commented] (HBASE-4123) Add support for BT locality groups

[ https://issues.apache.org/jira/browse/HBASE-4123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13069063#comment-13069063 ] stack commented on HBASE-4123: -- I think its at a level above hfile; hfile is kinda agnostic a

[jira] [Commented] (HBASE-4123) Add support for BT locality groups

[ https://issues.apache.org/jira/browse/HBASE-4123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13069060#comment-13069060 ] Jason Rutherglen commented on HBASE-4123: - I think we should specify what changes

[jira] [Commented] (HBASE-3465) Hbase should use a HADOOP_HOME environment variable if available.

[ https://issues.apache.org/jira/browse/HBASE-3465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13069055#comment-13069055 ] stack commented on HBASE-3465: -- I'm +1 then. Let me commit in a day or so. Maybe Ted Dunnin

[jira] [Commented] (HBASE-3465) Hbase should use a HADOOP_HOME environment variable if available.

[ https://issues.apache.org/jira/browse/HBASE-3465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13069035#comment-13069035 ] Alejandro Abdelnur commented on HBASE-3465: --- I think so, thxs! > Hbase should u

[jira] [Created] (HBASE-4123) Add support for BT locality groups

Add support for BT locality groups -- Key: HBASE-4123 URL: https://issues.apache.org/jira/browse/HBASE-4123 Project: HBase Issue Type: New Feature Reporter: stack BT has locality groups. HBase d

[jira] [Commented] (HBASE-3465) Hbase should use a HADOOP_HOME environment variable if available.

[ https://issues.apache.org/jira/browse/HBASE-3465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13069025#comment-13069025 ] stack commented on HBASE-3465: -- On 1., we use the mini test tools, minidfs, etc., but if the

[jira] [Commented] (HBASE-3465) Hbase should use a HADOOP_HOME environment variable if available.

[ https://issues.apache.org/jira/browse/HBASE-3465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13068978#comment-13068978 ] Alejandro Abdelnur commented on HBASE-3465: --- Thanks Stack. On 1st comment: Does

[jira] [Commented] (HBASE-3918) When assigning regions to an address, check the regionserver is actually online first

[ https://issues.apache.org/jira/browse/HBASE-3918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13068902#comment-13068902 ] ramkrishna.s.vasudevan commented on HBASE-3918: --- @Stack, I think this one is

[jira] [Updated] (HBASE-4122) improve hbck tool to fix .META. hole issue.

[ https://issues.apache.org/jira/browse/HBASE-4122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] feng xu updated HBASE-4122: --- Attachment: HBASE-4122.patch this patch is about how to fix a hole problem. > improve hbck tool to fix .META

[jira] [Commented] (HBASE-4094) improve hbck tool to fix more hbase problem

[ https://issues.apache.org/jira/browse/HBASE-4094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13068899#comment-13068899 ] feng xu commented on HBASE-4094: >>Regards 18 above, when you say collect the regioninfo f

[jira] [Commented] (HBASE-3845) data loss because lastSeqWritten can miss memstore edits

[ https://issues.apache.org/jira/browse/HBASE-3845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13068881#comment-13068881 ] ramkrishna.s.vasudevan commented on HBASE-3845: --- I have submitted the patch

[jira] [Updated] (HBASE-3845) data loss because lastSeqWritten can miss memstore edits

[ https://issues.apache.org/jira/browse/HBASE-3845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan updated HBASE-3845: -- Attachment: HBASE-3845_1.patch > data loss because lastSeqWritten can miss mems

[jira] [Updated] (HBASE-4083) If Enable table is not completed and is partial, then scanning of the table is not working

[ https://issues.apache.org/jira/browse/HBASE-4083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan updated HBASE-4083: -- Status: Patch Available (was: Open) > If Enable table is not completed and is

[jira] [Updated] (HBASE-4083) If Enable table is not completed and is partial, then scanning of the table is not working

[ https://issues.apache.org/jira/browse/HBASE-4083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan updated HBASE-4083: -- Attachment: HBASE-4083_trunk_1.patch > If Enable table is not completed and is

[jira] [Updated] (HBASE-4083) If Enable table is not completed and is partial, then scanning of the table is not working

[ https://issues.apache.org/jira/browse/HBASE-4083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan updated HBASE-4083: -- Attachment: HBASE-4083_0.90_1.patch > If Enable table is not completed and is p

[jira] [Updated] (HBASE-3845) data loss because lastSeqWritten can miss memstore edits

[ https://issues.apache.org/jira/browse/HBASE-3845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan updated HBASE-3845: -- Fix Version/s: 0.90.4 Status: Patch Available (was: Open) > data lo

[jira] [Updated] (HBASE-4083) If Enable table is not completed and is partial, then scanning of the table is not working

[ https://issues.apache.org/jira/browse/HBASE-4083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan updated HBASE-4083: -- Status: Open (was: Patch Available) > If Enable table is not completed and is

[jira] [Commented] (HBASE-4064) Two concurrent unassigning of the same region caused the endless loop of "Region has been PENDING_CLOSE for too long..."

[ https://issues.apache.org/jira/browse/HBASE-4064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13068876#comment-13068876 ] gaojinchao commented on HBASE-4064: --- Please don't merge the patch, I found other issue a

[jira] [Created] (HBASE-4121) improve hbck tool to fix .META. hole issue.

improve hbck tool to fix .META. hole issue. --- Key: HBASE-4121 URL: https://issues.apache.org/jira/browse/HBASE-4121 Project: HBase Issue Type: Improvement Reporter: feng xu F

[jira] [Created] (HBASE-4122) improve hbck tool to fix .META. hole issue.

improve hbck tool to fix .META. hole issue. --- Key: HBASE-4122 URL: https://issues.apache.org/jira/browse/HBASE-4122 Project: HBase Issue Type: Improvement Reporter: feng xu F

[jira] [Commented] (HBASE-4064) Two concurrent unassigning of the same region caused the endless loop of "Region has been PENDING_CLOSE for too long..."

[ https://issues.apache.org/jira/browse/HBASE-4064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13068843#comment-13068843 ] gaojinchao commented on HBASE-4064: --- I reproduced the issue by the above code. and modif