It can't be a blocker I don't think. We don't have a clear idea what's in error and how to fix.
> On Dec 5, 2016, at 2:19 PM, Stack <st...@duboce.net> wrote: > >> On Mon, Dec 5, 2016 at 12:10 PM, Sean Busbey <bus...@apache.org> wrote: >> >> I have not, thanks for the heads-up. >> >> HBASE-17069 is currently not marked blocker and has no assignee. If >> it's a blocker for 1.2.5, could the folks involved please correct >> this? >> >> > Its not marked blocker because issue is under investigation still. > HBASE-14465 has been fingered as a problematic backport but it has been in > 1.2 since 1.2.0 committed more than a year ago. Seems important figuring > what is going on here -- I'm having trouble replicating -- but doesn't seem > like something to hold up a 1.2.5 for. > > St.Ack > > > > >>> On Mon, Dec 5, 2016 at 2:08 PM, Ted Yu <yuzhih...@gmail.com> wrote: >>> Sean: >>> Have you looked at HBASE-17069 ? >>> >>> Cheers >>> >>>> On Mon, Dec 5, 2016 at 12:05 PM, Sean Busbey <bus...@apache.org> wrote: >>>> >>>> Hi folks! >>>> >>>> I'm planning to cut an RC for 1.2.5 at the end of this week. I don't >>>> see any blockers in JIRA, so please let me know if there's something >>>> that ought to stop a release. >>>> >>>> - >>>> busbey >>>> >>
