+0

Recent PR test failures are unfortunate, but look unrelated. It's
unfortunate, because there's enough change here that I think we'd all be a
lot more comfortable with better confidence that the changeset has not
introduced instabilities.

I think we're pretty close to cutting a 2.5.0 from this branch. I've not
seen anyone report their success at integrating these changes into a
telemetry system and showing end-to-end tracing of a service call. As I
recall from the last 2.5 discuss thread, we wanted this to be the banner
feature for the minor release. Since we don't have this end-to-end
confirmation, do we have someone who's volunteered to demonstrate that
final proof-of-integration in a timely manner? Perhaps that someone is keen
to be release manager for 2.5.

I didn't see a discuss thread talking about what open items might be left
before merge, so I raise my question here. Pardon me if these comments
should have landed elsewhere.

Thanks,
Nick

On Sun, Aug 29, 2021 at 8:22 PM Tak Lon (Stephen) Wu <[email protected]>
wrote:

> Hi everyone,
>
> I'm writing this request and propose a merge of HBASE-25853
> <https://issues.apache.org/jira/browse/HBASE-25853> "Backport HBASE-22120
> Replace HTrace with OpenTelemetry" to branch-2. The goal is to remove
> HTrace and uses OpenTelemetry also in branch-2.5.0+.
>
> Highlights
> * These changes only support async clients and calls
> * We will have a separate thread for support sync client in branch-2 , see
> HBASE-26141 <https://issues.apache.org/jira/browse/HBASE-26141>
>
> PRs
> * The merge PR with 18 reviewed commits
> https://github.com/apache/hbase/pull/3637
> * see all those reviewed commits at feature branch HBASE-25853
> <https://github.com/apache/hbase/commits/HBASE-25853>
>
> Please vote:
> [+1]      Agree
> [+/-0]    Neutral
> [-1]       Disagree (please include actionable feedback)
>
> Thanks,
> Stephen
>

Reply via email to