I would potentially be interested in continue to be involved with HTrace as a 
subproject.

The vision behind HTrace was always to have a single trace system that unified 
all of Hadoop.  So you could see what Accumulo was doing and how that affected 
HDFS, or what Phoenix was doing that affected HBase and HDFS, etc. etc.  This 
has sort of been built several times internally by companies running services 
based on Hadoopy projects, but never really made its way into open source in a 
meaningful way.  I thought we had a good shot at that, but maybe we needed to 
start earlier and have more resources.  We especially lacked full-time 
developers and people to evangelize the client.

I think it makes the most sense for HTrace to be a subproject of either Apache 
Hadoop or Apache Skywalking.  Skywalking in particular seems interesting since 
its goals are very similar to HTrace's -- to be a one-stop shop including 
tracing clients, visualization, and storage.  Perhaps HTraced could be useful 
to them for improving that "first 15 minute experience".  It's easy to start up 
and doesn't require managing a separate storage or query system.

I'm not so sure about HTrace being a subproject of Accumulo.  It seems like 
Accumulo is really focused on being a storage system, not so much on being a 
platform.  It would be weird for HBase or HDFS to depend on something that was 
a subproject of Accumulo, for example.

best,
Colin


On Wed, Mar 14, 2018, at 17:35, Michael Wall wrote:
> I am interested.  I am not thinking about it as subproject under Accumulo
> though, just to be clear.  Just looked at Skywalking for the first time,
> seems intriguing.
> 
> On Wed, Mar 14, 2018 at 7:32 PM Mike Drob <md...@mdrob.com> wrote:
> 
> > On Wed, Mar 14, 2018, 2:26 PM Billie Rinaldi <billie.rina...@gmail.com>
> > wrote:
> >
> > > In the active thread "[VOTE] Retire HTrace from Incubation" Christopher
> > > Tubbs brought up the idea to make HTrace a subproject of an existing TLP.
> >
> > This would mitigate the issues of the community being inactive and the core
> > > instrumentation library not requiring ongoing development.
> >
> >
> > Does moving to a subproject out another tlp necessitate changing Java
> > package names prior to release? That would put a damper on user adoption
> > again.
> >
> > It's a choice we could make now (assuming we were able to find a TLP
> > > willing to adopt HTrace
> >
> > as a subproject),
> >
> > The Skywalking podling expressed some interest in the vote thread.
> >
> >
> >
> > or we could allow HTrace to retire and then revisit the
> > > subproject idea at a future time if someone becomes interested in
> > patching
> > > and releasing a new version of HTrace.
> > >
> > > So far, the people who have expressed interest in being involved with
> > > HTrace as a possible subproject are Christopher, Masatake, and myself. Is
> > > anyone else in the community interested in this idea?
> > >
> >

Reply via email to