[jira] [Commented] (HBASE-20248) [ITBLL] UNREFERENCED rows
[ https://issues.apache.org/jira/browse/HBASE-20248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16436484#comment-16436484 ] stack commented on HBASE-20248: --- Just finished a 4th 10B run where Master was NOT killed over the life of the run. It verified. Logs look ok except for (disturbing-looking) spew from HBASE-20404 "Ugly cleanerchore complaint that dir is not empty" and HBASE-20383 "[AMv2] AssignmentManager: Failed transition XYZ is not OPEN". > [ITBLL] UNREFERENCED rows > - > > Key: HBASE-20248 > URL: https://issues.apache.org/jira/browse/HBASE-20248 > Project: HBase > Issue Type: Sub-task > Components: dataloss >Affects Versions: 2.0.0 >Reporter: stack >Assignee: stack >Priority: Blocker > Fix For: 2.0.0 > > > From parent, saw unreferenced rows in a run yesterday against tip of > branch-2. Saw similar in a run from a week or so ago. > Enabling DEBUG and rerunning to see if I can get to root of dataloss. See > https://docs.google.com/document/d/14Tvu5yWYNBDFkh8xCqLkU9tlyNWhJv3GjDGOkqZU1eE/edit# > for old debugging trickery. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HBASE-20248) [ITBLL] UNREFERENCED rows
[ https://issues.apache.org/jira/browse/HBASE-20248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16434332#comment-16434332 ] stack commented on HBASE-20248: --- 3rd 10B run verified. I'll keep running tests but for now resolving as can't reproduce. > [ITBLL] UNREFERENCED rows > - > > Key: HBASE-20248 > URL: https://issues.apache.org/jira/browse/HBASE-20248 > Project: HBase > Issue Type: Sub-task > Components: dataloss >Affects Versions: 2.0.0 >Reporter: stack >Assignee: stack >Priority: Blocker > Fix For: 2.0.0 > > > From parent, saw unreferenced rows in a run yesterday against tip of > branch-2. Saw similar in a run from a week or so ago. > Enabling DEBUG and rerunning to see if I can get to root of dataloss. See > https://docs.google.com/document/d/14Tvu5yWYNBDFkh8xCqLkU9tlyNWhJv3GjDGOkqZU1eE/edit# > for old debugging trickery. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HBASE-20248) [ITBLL] UNREFERENCED rows
[ https://issues.apache.org/jira/browse/HBASE-20248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16432662#comment-16432662 ] stack commented on HBASE-20248: --- A second 10B run just verified as all Cells present/linked. Starting another > [ITBLL] UNREFERENCED rows > - > > Key: HBASE-20248 > URL: https://issues.apache.org/jira/browse/HBASE-20248 > Project: HBase > Issue Type: Sub-task > Components: dataloss >Affects Versions: 2.0.0 >Reporter: stack >Assignee: stack >Priority: Blocker > Fix For: 2.0.0 > > > From parent, saw unreferenced rows in a run yesterday against tip of > branch-2. Saw similar in a run from a week or so ago. > Enabling DEBUG and rerunning to see if I can get to root of dataloss. See > https://docs.google.com/document/d/14Tvu5yWYNBDFkh8xCqLkU9tlyNWhJv3GjDGOkqZU1eE/edit# > for old debugging trickery. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HBASE-20248) [ITBLL] UNREFERENCED rows
[ https://issues.apache.org/jira/browse/HBASE-20248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16431650#comment-16431650 ] stack commented on HBASE-20248: --- Ok. Tried 25B twice. First time failed with HBASE-20366. Second time ran longer but failed because I filled all the disks (I am keeping all WALs, recovered edits, and hfiles, so I can trace dataloss should it arise). Let me go back to 5 or 10B runs. > [ITBLL] UNREFERENCED rows > - > > Key: HBASE-20248 > URL: https://issues.apache.org/jira/browse/HBASE-20248 > Project: HBase > Issue Type: Sub-task > Components: dataloss >Affects Versions: 2.0.0 >Reporter: stack >Assignee: stack >Priority: Blocker > Fix For: 2.0.0 > > > From parent, saw unreferenced rows in a run yesterday against tip of > branch-2. Saw similar in a run from a week or so ago. > Enabling DEBUG and rerunning to see if I can get to root of dataloss. See > https://docs.google.com/document/d/14Tvu5yWYNBDFkh8xCqLkU9tlyNWhJv3GjDGOkqZU1eE/edit# > for old debugging trickery. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HBASE-20248) [ITBLL] UNREFERENCED rows
[ https://issues.apache.org/jira/browse/HBASE-20248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16429510#comment-16429510 ] stack commented on HBASE-20248: --- Started this project up again. Just did a 10B run w/ chaos. All checked out. Will try going bigger. > [ITBLL] UNREFERENCED rows > - > > Key: HBASE-20248 > URL: https://issues.apache.org/jira/browse/HBASE-20248 > Project: HBase > Issue Type: Sub-task > Components: dataloss >Affects Versions: 2.0.0 >Reporter: stack >Assignee: stack >Priority: Blocker > Fix For: 2.0.0 > > > From parent, saw unreferenced rows in a run yesterday against tip of > branch-2. Saw similar in a run from a week or so ago. > Enabling DEBUG and rerunning to see if I can get to root of dataloss. See > https://docs.google.com/document/d/14Tvu5yWYNBDFkh8xCqLkU9tlyNWhJv3GjDGOkqZU1eE/edit# > for old debugging trickery. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
