[RESULT] WAS Re: [VOTE] Retire the HTrace Podling

[lewis john mcgibbney]

I am closing this VOTE off now. Thank you to everyone that VOTE'd. RESULT
is as follows

[6] +1 retire the HTrace podling
Lewis John McGibbney*
Sheng Wu
Ralph Goers*
P. Taylor Goetz*
Dave Fisher*
Pierre Smits*

[0] -1 NOT NOT retire the HTrace podling (please provide justification)

* IPMC Binding

I'll go ahead and reboot the retirement process.
Lewis

On Wed, Apr 11, 2018 at 4:40 PM, lewis john mcgibbney <lewi...@apache.org>
wrote:

> Hi Folks,
> Please excuse the error on my part, which essentially missed this
> important stage of VOTE'ing on general@ for official retirement of the
> HTrace Podling.
> However, we are here now. The VOTE will be open for a minimum of 72 hours.
> The previous community VOTE [0] took place on the HTrace dev@ list with a
> lot of participation. I closed this off today with the RESULT [1].
> I would like to explicitly note that a subsequent parallel thread was
> initiated [2] which essentially suggested HTrace staying alive as a
> Subproject. Unfortunately this thread petered out... my inclination is that
> this outcome is that for HTrace to become a Subproject, essentially work
> would need to be done by some people... which brings us back to the initial
> reason for drafting the retirement email thread in the first place e.g.
> no-one has the time to work on HTrace any more.
> Please DISCUSS or VOTE as below
>
> [ ] +1 retire the HTrace podling
> [ ] -1 NOT NOT retire the HTrace podling (please provide justification)
>
> Thanks,
> Lewis
> P.S. Here is my +1
>
>
> [0] VOTE: https://s.apache.org/2sGB
> [1] RESULT: https://s.apache.org/e22i
> [2] https://s.apache.org/MlLn
>
> --
> http://home.apache.org/~lewismc/
> http://people.apache.org/keys/committer/lewismc
>



-- 
http://home.apache.org/~lewismc/
http://people.apache.org/keys/committer/lewismc

[VOTE] Retire the HTrace Podling

[lewis john mcgibbney]

Hi Folks,
Please excuse the error on my part, which essentially missed this important
stage of VOTE'ing on general@ for official retirement of the HTrace Podling.
However, we are here now. The VOTE will be open for a minimum of 72 hours.
The previous community VOTE [0] took place on the HTrace dev@ list with a
lot of participation. I closed this off today with the RESULT [1].
I would like to explicitly note that a subsequent parallel thread was
initiated [2] which essentially suggested HTrace staying alive as a
Subproject. Unfortunately this thread petered out... my inclination is that
this outcome is that for HTrace to become a Subproject, essentially work
would need to be done by some people... which brings us back to the initial
reason for drafting the retirement email thread in the first place e.g.
no-one has the time to work on HTrace any more.
Please DISCUSS or VOTE as below

[ ] +1 retire the HTrace podling
[ ] -1 NOT NOT retire the HTrace podling (please provide justification)

Thanks,
Lewis
P.S. Here is my +1


[0] VOTE: https://s.apache.org/2sGB
[1] RESULT: https://s.apache.org/e22i
[2] https://s.apache.org/MlLn

-- 
http://home.apache.org/~lewismc/
http://people.apache.org/keys/committer/lewismc

Retirement Process

[lewis john mcgibbney]

Hi Folks,
OK, so the process is well underway.
https://issues.apache.org/jira/browse/INFRA-16335
Once this is done, I will pick things back up from the bottom bullet point
"...After Infra modifies the website SVN permissions, disable the podling
website by installing an .htaccess like this..."
Lewis
Lewis

-- 
http://home.apache.org/~lewismc/
http://people.apache.org/keys/committer/lewismc

[RESULT] WAS Re: [VOTE] Retire HTrace from Incubation

[Lewis John McGibbney]

Hi Folks,
OK, 72 hours has well and truly come and gone... many times over. I am 
therefore going to close with a RESULT.

[ ] +1 retire the HTrace podling
Lewis John McGibbney
Sean Busby
Jake Farrell
Mike Drob
Michael Stack
Masatake Iwasaki

[0] -1 NOT NOT retire the HTrace podling (please provide justification)

I will therefore progress with drafting the retirement documentation and follow 
the progress.
Thanks all for the effort during the Incubation. Not all podling efforts work 
out.
Lewis

On 2018/03/08 14:49:23, lewis john mcgibbney <lewi...@apache.org> wrote: 
> Hi Folks,
> Below I've populated our report for the month of March 2018.
> https://wiki.apache.org/incubator/March2018 (also below)
> I've basically initiated the Retirement sentiment which has been prevalent
> within the HTrace community for some time. I would therefore like to
> formally open a VOTE to retire HTrace from the Incubator.
> The VOTE will be open for at least 72 hours.
> [ ] +1 retire the HTrace podling
> [ ] -1 NOT NOT retire the HTrace podling (please provide justification)
> Lewis
> 
> ===
> 
> HTrace
> 
> HTrace is a tracing framework intended for use with distributed systems
> written in java.
> 
> HTrace has been incubating since 2014-11-11.
> 
> Three most important issues to address in the move towards graduation:
> 
>   1. -
>   2. -
>   3. -
> 
> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> aware of?
> 
> The HTrace podling has seen no code activity in months. Discussion of
> sending it to the Attic have been circulating for some time as well.
> After literally no activity again over the last few months, it looks like
> it is time to progress with sending HTrace to the Attic.
> 
> How has the community developed since the last report?
> 
> It has not.
> 
> How has the project developed since the last report?
> 
> It has not.
> 
> How would you assess the podling's maturity?
> Please feel free to add your own commentary.
> 
>   [X] Initial setup
>   [X] Working towards first release
>   [X] Community building
>   [ ] Nearing graduation
>   [X] Other: No actiity.
> 
> Date of last release:
> 
>   2016-03-04
> 
> When were the last committers or PPMC members elected?
> 
>   2016-10-03
> 
> Signed-off-by:
> 
>   [ ](htrace) Jake Farrell
>  Comments:
>   [ ](htrace) Todd Lipcon
>  Comments:
>   [X](htrace) Lewis John Mcgibbney
>  Comments: In our January 2018 report we mentioned that
>  "HTrace is very quiet. There is opportunity to continue
>  work if we engage with projects already using HTrace. If that does not
>  happen, we should retire the podling." We should therefore retire the
> podling.
>   [ ](htrace) Andrew Purtell
>  Comments:
>   [ ](htrace) Billie Rinaldi
>  Comments:
>   [ ](htrace) Michael Stack
> 
> -- 
> http://home.apache.org/~lewismc/
> http://people.apache.org/keys/committer/lewismc
> 

Re: [DISCUSS] Subproject proposal

[lewis john mcgibbney]

Hi Billie,
Thanks
I'm not sure that letting this sit for too much longer is doing any favours
for anyone to be honest.
Additionally, I think it has probably sat for way too long already.
I'll give it to end of weekend then close VOTE and begin retirement to
Attic.
Thanks
Lewis

On Fri, Apr 6, 2018 at 6:49 AM,  wrote:

>
> From: Billie Rinaldi 
> To: dev@htrace.incubator.apache.org
> Cc:
> Bcc:
> Date: Wed, 4 Apr 2018 06:49:55 -0700
> Subject: Re: [DISCUSS] Subproject proposal
> That sounds like an accurate assessment. I have not contacted any potential
> target communities.
>
> Billie
>
>

Re: [VOTE] Retire HTrace from Incubation

[lewis john mcgibbney]

general@incubator thread link inline

On Mon, Mar 12, 2018 at 9:27 PM, lewis john mcgibbney <lewi...@apache.org>
wrote:

> Hi Folks,
> The decision to initiate retirement is not usually an enjoyable one. It
> would appear that those whose of us who have VOTE'd have made it quite
> clear that retirement is the right thing to do.
> According to whimsy however [0], we do not currently have enough PPMC
> VOTE's to move forward with closing this VOTE with any RESULT. Actually,
> not one member of the PPMC has VOTE'd yet which is pretty discouraging. At
> this stage I think that we should most likely consult the general@incubator
> list to seek consensus on how to proceed.
>

https://s.apache.org/94eL


> It should be noted that it is really the Mentors who have contributed to
> this VOTE thread with VOTE's. I think that this speaks volumes for HTrace's
> ability to sustain itself as a viable podling.
>
> The VOTE has been open for at least 72 hours with the following outcome.
>
> [4] +1 retire the HTrace podling
> Sean Busbey
> Jake Farrell
> Mike Drob
> Michael Stack
>
> [0] -1 NOT NOT retire the HTrace podling (please provide justification)
>
> I have not yet VOTE'd. I am completely aware of the fact however that this
> is crunch time for HTrace. I think we either need to graduate as a
> subproject OR draft a retirement resolution and propose that HTrace be
> sucked into the Attic. I personally would like to see one/more of the
> following taking place
>
>- HTrace PPMC to engage with the VOTE if possible
>- Sean Busbey/Sheng Wu/Christopher (ctubbsii)/Billie Rinaldi step up
>and propose a path for HTrace to graduate as a subproject of project X.
>
> I'll hang on with the VOTE for another ~72 hours and if nothing come of
> the above then I will most likely VOTE to retire HTrace.
>
> Lewis
>
> [0] https://whimsy.apache.org/roster/ppmc/htrace
>
> On Thu, Mar 8, 2018 at 6:49 AM, lewis john mcgibbney <lewi...@apache.org>
> wrote:
>
>> Hi Folks,
>> Below I've populated our report for the month of March 2018.
>> https://wiki.apache.org/incubator/March2018 (also below)
>> I've basically initiated the Retirement sentiment which has been
>> prevalent within the HTrace community for some time. I would therefore like
>> to formally open a VOTE to retire HTrace from the Incubator.
>> The VOTE will be open for at least 72 hours.
>> [ ] +1 retire the HTrace podling
>> [ ] -1 NOT NOT retire the HTrace podling (please provide justification)
>> Lewis
>>
>> ===
>>
>> HTrace
>>
>> HTrace is a tracing framework intended for use with distributed systems
>> written in java.
>>
>> HTrace has been incubating since 2014-11-11.
>>
>> Three most important issues to address in the move towards graduation:
>>
>>   1. -
>>   2. -
>>   3. -
>>
>> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
>> aware of?
>>
>> The HTrace podling has seen no code activity in months. Discussion of
>> sending it to the Attic have been circulating for some time as well.
>> After literally no activity again over the last few months, it looks like
>> it is time to progress with sending HTrace to the Attic.
>>
>> How has the community developed since the last report?
>>
>> It has not.
>>
>> How has the project developed since the last report?
>>
>> It has not.
>>
>> How would you assess the podling's maturity?
>> Please feel free to add your own commentary.
>>
>>   [X] Initial setup
>>   [X] Working towards first release
>>   [X] Community building
>>   [ ] Nearing graduation
>>   [X] Other: No actiity.
>>
>> Date of last release:
>>
>>   2016-03-04
>>
>> When were the last committers or PPMC members elected?
>>
>>   2016-10-03
>>
>> Signed-off-by:
>>
>>   [ ](htrace) Jake Farrell
>>  Comments:
>>   [ ](htrace) Todd Lipcon
>>  Comments:
>>   [X](htrace) Lewis John Mcgibbney
>>  Comments: In our January 2018 report we mentioned that
>>  "HTrace is very quiet. There is opportunity to continue
>>  work if we engage with projects already using HTrace. If that does
>> not
>>  happen, we should retire the podling." We should therefore retire
>> the podling.
>>   [ ](htrace) Andrew Purtell
>>  Comments:
>>   [ ](htrace) Billie Rinaldi
>>  Comments:
>>   [ ](htrace) Michael Stack
>>
>> --
>> http://home.apache.org/~lewismc/
>> http://people.apache.org/keys/committer/lewismc
>>
>
>
>
> --
> http://home.apache.org/~lewismc/
> http://people.apache.org/keys/committer/lewismc
>



-- 
http://home.apache.org/~lewismc/
http://people.apache.org/keys/committer/lewismc

Fwd: [VOTE] Retire HTrace from Incubation

[lewis john mcgibbney]

Hi HTrace PPMC,
I thought I would directly pass on the below VOTE for consideration.
Thanks
Lewis

-- Forwarded message --
From: lewis john mcgibbney <lewi...@apache.org>
Date: Thu, Mar 8, 2018 at 6:49 AM
Subject: [VOTE] Retire HTrace from Incubation
To: dev@htrace.incubator.apache.org


Hi Folks,
Below I've populated our report for the month of March 2018.
https://wiki.apache.org/incubator/March2018 (also below)
I've basically initiated the Retirement sentiment which has been prevalent
within the HTrace community for some time. I would therefore like to
formally open a VOTE to retire HTrace from the Incubator.
The VOTE will be open for at least 72 hours.
[ ] +1 retire the HTrace podling
[ ] -1 NOT NOT retire the HTrace podling (please provide justification)
Lewis

===

HTrace

HTrace is a tracing framework intended for use with distributed systems
written in java.

HTrace has been incubating since 2014-11-11.

Three most important issues to address in the move towards graduation:

  1. -
  2. -
  3. -

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?

The HTrace podling has seen no code activity in months. Discussion of
sending it to the Attic have been circulating for some time as well.
After literally no activity again over the last few months, it looks like
it is time to progress with sending HTrace to the Attic.

How has the community developed since the last report?

It has not.

How has the project developed since the last report?

It has not.

How would you assess the podling's maturity?
Please feel free to add your own commentary.

  [X] Initial setup
  [X] Working towards first release
  [X] Community building
  [ ] Nearing graduation
  [X] Other: No actiity.

Date of last release:

  2016-03-04

When were the last committers or PPMC members elected?

  2016-10-03

Signed-off-by:

  [ ](htrace) Jake Farrell
 Comments:
  [ ](htrace) Todd Lipcon
 Comments:
  [X](htrace) Lewis John Mcgibbney
 Comments: In our January 2018 report we mentioned that
 "HTrace is very quiet. There is opportunity to continue
 work if we engage with projects already using HTrace. If that does not
 happen, we should retire the podling." We should therefore retire the
podling.
  [ ](htrace) Andrew Purtell
 Comments:
  [ ](htrace) Billie Rinaldi
 Comments:
  [ ](htrace) Michael Stack

-- 
http://home.apache.org/~lewismc/
http://people.apache.org/keys/committer/lewismc



-- 
http://home.apache.org/~lewismc/
http://people.apache.org/keys/committer/lewismc

Re: [VOTE] Retire HTrace from Incubation

[lewis john mcgibbney]

Hi Sheng,

On Mon, Mar 12, 2018 at 2:55 PM, <
dev-digest-h...@htrace.incubator.apache.org> wrote:

>
> From: Sheng Wu 
> To: Adrian Cole , dev@htrace.incubator.apache.org,
> d...@skywalking.incubator.apache.org
> Cc:
> Bcc:
> Date: Sun, 11 Mar 2018 18:36:17 +0800
> Subject: Re: Re: [VOTE] Retire HTrace from Incubation
> Hi, Adrian and HTrace community.
>
> Glad to be invited. I am the creator and PPMC of SkyWaking, which is a new
> incubator project: https://incubator.apache.org/projects/skywalking.html
>
> Right now, SkyWalking provide Agent based SDK, such OpenTracing APIs and
> our own APIs. But I am not familiar with HTrace's APIs. But there is two
> very easy ways
> 1. Add a new module to provide a library
> 2. Provide another API library with the agent.
>
> Or HTrace community guys have any suggestion.
>
> Anyway, I and skywalking team want to help.


There is absolutely nothing preventing the above work to go ahead right
now. The most recent HTrace artifacts (htrace-4.2.0-incubating) can be
found at [0] with the Maven artifacts present at [1]. Maybe this would be a
useful GSoC effort I am not sure. It doesn't however look like the folks on
dev@htrace have time to be engaged in that effort however I am may be
completely wrong.

Lewis

[0] http://www.apache.org/dyn/closer.cgi/incubator/htrace/
[1] http://search.maven.org/#search%7Cga%7C1%7Cg%3A%22org.apache.htrace%22

Re: [VOTE] Retire HTrace from Incubation

[lewis john mcgibbney]

Hi Mike,

On Mon, Mar 12, 2018 at 2:55 PM, <
dev-digest-h...@htrace.incubator.apache.org> wrote:

>
> From: Mike Drob 
> To: dev@htrace.incubator.apache.org
> Cc:
> Bcc:
> Date: Sat, 10 Mar 2018 22:16:46 -0600
> Subject: Re: [VOTE] Retire HTrace from Incubation
> There's a distinction between the code and the community. The code can be
> there, but it certainly feels like there is no community left. If any of
> the TLPs want to try to pick it back up, I don't think anybody would stop
> them?
>
>
This is true. The Apache Attic [0] enables the current PPPMC to retire
HTrace but also enables almost ANYONE to initiate the pprocess of leaving
the Attic again. The options are

   - Forking the project - we'll link to any forks which have been created
   so please let us know
   - Restarting the community in the Apache Incubator
   - Recreating a PMC for the project

Right now however, if the mentoring members of HTrace were to entirely
disperse e.g. Jake Farrell, Todd Lipcon, Andrew Purtell, Billie Rinaldi,
Michael Stack and me, then I think that HTrace would most likely fall into
the state where it would join the group of projects whose PMC are unable to
muster 3 votes for a release, who have no active committers or are unable
to fulfill their reporting duties to the board.

The simple fact is that until this very point in time, HTrace has been
unable to demonstrably grow community. In hindsight, we should have
possibly drafted a graduation proposal after the preious release however
that is now in the past and cannot be undone.

Lewis

[0] https://attic.apache.org/

[VOTE] Retire HTrace from Incubation

[lewis john mcgibbney]

Hi Folks,
Below I've populated our report for the month of March 2018.
https://wiki.apache.org/incubator/March2018 (also below)
I've basically initiated the Retirement sentiment which has been prevalent
within the HTrace community for some time. I would therefore like to
formally open a VOTE to retire HTrace from the Incubator.
The VOTE will be open for at least 72 hours.
[ ] +1 retire the HTrace podling
[ ] -1 NOT NOT retire the HTrace podling (please provide justification)
Lewis

===

HTrace

HTrace is a tracing framework intended for use with distributed systems
written in java.

HTrace has been incubating since 2014-11-11.

Three most important issues to address in the move towards graduation:

  1. -
  2. -
  3. -

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?

The HTrace podling has seen no code activity in months. Discussion of
sending it to the Attic have been circulating for some time as well.
After literally no activity again over the last few months, it looks like
it is time to progress with sending HTrace to the Attic.

How has the community developed since the last report?

It has not.

How has the project developed since the last report?

It has not.

How would you assess the podling's maturity?
Please feel free to add your own commentary.

  [X] Initial setup
  [X] Working towards first release
  [X] Community building
  [ ] Nearing graduation
  [X] Other: No actiity.

Date of last release:

  2016-03-04

When were the last committers or PPMC members elected?

  2016-10-03

Signed-off-by:

  [ ](htrace) Jake Farrell
 Comments:
  [ ](htrace) Todd Lipcon
 Comments:
  [X](htrace) Lewis John Mcgibbney
 Comments: In our January 2018 report we mentioned that
 "HTrace is very quiet. There is opportunity to continue
 work if we engage with projects already using HTrace. If that does not
 happen, we should retire the podling." We should therefore retire the
podling.
  [ ](htrace) Andrew Purtell
 Comments:
  [ ](htrace) Billie Rinaldi
 Comments:
  [ ](htrace) Michael Stack

-- 
http://home.apache.org/~lewismc/
http://people.apache.org/keys/committer/lewismc

[REPORT] HTrace 2018

[lewis john mcgibbney]

HTraceHTrace is a tracing framework intended for use with distributed
systemswritten in java.HTrace has been incubating since
2014-11-11.Three most important issues to address in the move towards
graduation: 1. Continue to grow the Apache HTrace community 2. Further
engagement with projects integrating Apache HTrace 3. Continue to
develop and release stable Apache HTrace incubating artifactsAny
issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
awareof?Several months of stagnation have raised repeated
conversations aboutretiring HTrace. If nothing materializes before the
end of Q1 2018 HTracewill be retired.How has the community developed
since the last report? Mailing lists continue quiet (bar the above
noted conversations).How has the project developed since the last
report? No development.How would you assess the podling's maturity?
Please feel free to add your owncommentary. [X] Initial setup [X]
Working towards first release [x] Community building [ ] Nearing
graduation [ ] Other:Date of last release: 2016-09-15When were the
last committers or PPMC members elected? 2016-10-03Signed-off-by:  [
](htrace) Jake Farrell Comments:  [ ](htrace) Todd Lipcon
Comments:  [x](htrace) Lewis John Mcgibbney Comments: HTrace is
very quiet. There is opportunity to continue work is we engage
with projects already using HTrace. If that does not happen, we
should retire the podling.  [ ](htrace) Andrew Purtell Comments:
[x](htrace) Billie Rinaldi Comments:  [X](htrace) Michael Stack
 Comments:



-- 
http://home.apache.org/~lewismc/
@hectorMcSpector
http://www.linkedin.com/in/lmcgibbney

Re: Current status?

[lewis john mcgibbney]

Hi John,
This surfaced again about a month or so ago and although opinions were
voiced that HTrace should not retire, I have not seen any activity.
I think the writing is on the wall is it would appear committers do not
quite have the time to move things forward.
Lewis

On Sun, Dec 10, 2017 at 6:32 AM, <
dev-digest-h...@htrace.incubator.apache.org> wrote:

>
> From: "John D. Ament" 
> To: 
> Cc:
> Bcc:
> Date: Sun, 10 Dec 2017 14:32:24 -
> Subject: Current status?
> Dear HTrace Podling,
>
> I was wondering what your current status is.  There is no report filed,
> and very low on list activity.  Is it time to begin retirement discussions?
>
> John
>
>
>


-- 
http://home.apache.org/~lewismc/
@hectorMcSpector
http://www.linkedin.com/in/lmcgibbney

Re: [DISCUSS] Attic podling Apache HTrace?

[lewis john mcgibbney]

Hi Mike,
I think this is a fair question. We've probably all been associated with
projects which just don't really make it. It would appear that HTrace is
one of them. This is not to say that there is nothing going on with the
tracing effort generally (as there is) but it looks like HTrace as a
project may be headed to the Attic.
I suppose the response to this thread will determine what happens...
Lewis

On Wed, Aug 16, 2017 at 10:01 AM, <
dev-digest-h...@htrace.incubator.apache.org> wrote:

>
> From: Mike Drob 
> To: dev@htrace.incubator.apache.org
> Cc:
> Bcc:
> Date: Wed, 16 Aug 2017 12:00:49 -0500
> Subject: [DISCUSS] Attic podling Apache HTrace?
> Hi folks,
>
> Want to bring up a potentially uncofortable topic for some. Is it time to
> retire/attic the project?
>
> We've seen a minimal amount of activity in the past year. The last release
> had two bug fixes, and had been pending for several months before somebody
> reminded me to push the artifacts to subversion from the staging directory.
>
> I'd love to see a renewed set of activity here, but I don't think there is
> a ton of interest going on.
>
> HBase is still on version 3. So is Accumulo, I think. Hadoop is on 4.1,
> which is a good sign, but I haven't heard much from them recently. I
> definitely do no think we are at the point where a lack of releases and
> activity is a sign of super advanced maturity and stability.
>
> Your thoughts?
>
> Mike
>
>


-- 
http://home.apache.org/~lewismc/
@hectorMcSpector
http://www.linkedin.com/in/lmcgibbney

Community Growth through Connections with Distributed Tracing Workgroup + OpenTracing

[Lewis John Mcgibbney]

Hi Folks,
Are there any ongoing or planned engagements/collaborations ongoing with
any of the above? I spoke with a couple of folks @ApacheCon last week and
they were keen to connect with dev@ on a face-to-face basis to see what was
going on.
Is/are anyone from HTrace involved in these activities? If not then is this
something that we want to engage in?
I'm just throwing this out here to see what is going on.
Thanks
Lewis

-- 
*Lewis*

Obtaining HTrace Logging in Client Applications

[Lewis John Mcgibbney]

Hi Folks,
So I consume htrace-core4 in the Nuch Java application. I am however not
able to see the HTrace DEBUG log statements.
I am aware that HTrace uses commons-logging and I have tried adding
commons-logging.properties on my classpath with the following contents

org.apache.commons.logging.Log=org.apache.commons.logging.impl.Log4JLogger
log4j.configuration=log4j.properties
LocalFileSpanReceiver.level=DEBUG

The log4j.properties file is in the same directory.
I am unable to see any log statements from HTrace...
Has anyone else had any luck?
Thanks
Lewis

-- 
*Lewis*

Seeing Spans in HTraced

[Lewis John Mcgibbney]

Hi Folks,
For test and development and also for new comers coming to HTrace I am not
sure if it is realistic for such a high default buffer to be set for
Htraced. Right now is appears that the default value is 16,777,216 bytes
which is pretty large if one wishes to get a feel for the HTrace framework
generally and HTraced specifically.
Although I am easily able to work programmatically and hence change this
default buffer value to anything I want. Everyone else may not be that way
inclined and may instead just wish to, fr example, run the Docker image and
see what HTrace actually does.
Does anyone else have an opinion on this? My perspective from being
@ApacheCon last week and from doing my HTrac'ing in Nutch presentation is
that people just want to see what HTrac'ing looks like. They may not have
an application which writes 16MB of spans to a buffer out of the box.
Thanks
Lewis

-- 
*Lewis*

Issues Building HTrace Master

[Lewis John Mcgibbney]

Hi Folks,
when I attempt to build master branch I get the following error

lmcgibbn@LMC-032857 /usr/local/incubator-htrace(master) $ mvn -version
Apache Maven 3.3.3 (7994120775791599e205a5524ec3e0dfe41d4a06;
2015-04-22T04:57:37-07:00)
Maven home: /usr/local/apache-maven-3.3.3
Java version: 1.8.0_66, vendor: Oracle Corporation
Java home:
/Library/Java/JavaVirtualMachines/jdk1.8.0_66.jdk/Contents/Home/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "mac os x", version: "10.9.5", arch: "x86_64", family: "mac"

mvn clean install -DskipTests -DcreateDependencyReducedPom=false

[INFO]

[INFO] Building htrace-htraced 4.2.0-incubating-SNAPSHOT
[INFO]

[INFO]
[INFO] --- maven-clean-plugin:2.6.1:clean (default-clean) @ htrace-htraced
---
[INFO] Deleting /usr/local/incubator-htrace/htrace-htraced/target
[INFO] Deleting /usr/local/incubator-htrace/htrace-htraced/go/build
(includes = [], excludes = [])
[INFO] Deleting /usr/local/incubator-htrace/htrace-htraced/go/pkg (includes
= [], excludes = [])
[INFO]
[INFO] --- maven-remote-resources-plugin:1.5:process (default) @
htrace-htraced ---
[INFO]
[INFO] --- maven-resources-plugin:2.7:resources (default-resources) @
htrace-htraced ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory
/usr/local/incubator-htrace/htrace-htraced/src/main/resources
[INFO] Copying 3 resources
[INFO]
[INFO] --- maven-compiler-plugin:2.5.1:compile (default-compile) @
htrace-htraced ---
[INFO] Compiling 8 source files to
/usr/local/incubator-htrace/htrace-htraced/target/classes
[INFO]
[INFO] --- maven-antrun-plugin:1.7:run (go_compile) @ htrace-htraced ---
[WARNING] Parameter tasks is deprecated, use target instead
[INFO] Executing tasks

main:
 [exec] Installing godep...
 [exec] godep: [WARNING]: godep should only be used inside a valid go
package directory and
 [exec] godep: [WARNING]: may not function correctly. You are probably
outside of your $GOPATH.
 [exec] godep: [WARNING]:Current Directory:
/usr/local/incubator-htrace/htrace-htraced/go
 [exec] godep: [WARNING]:$GOPATH:
/usr/local/incubator-htrace/htrace-htraced/go/build:/usr/local/incubator-htrace/htrace-htraced/go
 [exec] /usr/local/incubator-htrace/htrace-htraced/go/build/godep
restore...
 [exec] Building 4.2.0-incubating-SNAPSHOT
[4a101e0d1c435937feba9fc876882ffbf71259b1]
 [exec] github.com/ugorji/go/codec
 [exec] htrace/conf
 [exec] github.com/alecthomas/units
 [exec] github.com/gorilla/context
 [exec] github.com/jmhodges/levigo
 [exec] github.com/alecthomas/kingpin
 [exec] github.com/gorilla/mux
 [exec] htrace/common
 [exec] htrace/test
 [exec] htrace/client
 [exec] htrace/htraced
 [exec] htrace/htracedTool
 [exec] # htrace/htracedTool
 [exec] usage: 6l [options] main.6
 [exec]   -1use alternate profiling code
 [exec]   -8assume 64-bit addresses
 [exec]   -B info
 [exec] define ELF NT_GNU_BUILD_ID note
 [exec]   -Ccheck Go calls to C code
 [exec]   -D addr
 [exec] data address
 [exec]   -E sym
 [exec] entry symbol
 [exec]   -I interp
 [exec] set ELF interp
 [exec]   -L dir
 [exec] add dir to library path
 [exec]   -H head
 [exec] header type
 [exec]   -Kadd stack underflow checks
 [exec]   -Oprint pc-line tables
 [exec]   -Qdebug byte-register code gen
 [exec]   -R rnd
 [exec] address rounding
 [exec]   -Scheck type signatures
 [exec]   -T addr
 [exec] text address
 [exec]   -Vprint version and exit
 [exec]   -Wdisassemble input
 [exec]   -X name value
 [exec] define string data
 [exec]   -Zclear stack frame on entry
 [exec]   -adisassemble output
 [exec]   -cdump call graph
 [exec]   -ddisable dynamic executable
 [exec]   -extld ld
 [exec] linker to run in external mode
 [exec]   -extldflags ldflags
 [exec] flags for external linker
 [exec]   -fignore version mismatch
 [exec]   -gdisable go package data checks
 [exec]   -installsuffix suffix
 [exec] pkg directory suffix
 [exec]   -k sym
 [exec] set field tracking symbol
 [exec]   -linkmode mode
 [exec] set link mode (internal, external, auto)
 [exec]   -ndump symbol table
 [exec]   -o outfile
 [exec] set output file
 [exec]   -r dir1:dir2:...
 [exec] set ELF dynamic linker search path
 [exec]   -race
 [exec] enable race detector
 [exec]   -sdisable symbol table
 [exec]   -shared
 [exec] generate shared object (implies -linkmode external)
 [exec]   -tmpdir dir
 

Staging Repos for HTrace

[Lewis John Mcgibbney]

Hi Folks,
There is a closed stging repos for HTrace
https://repository.apache.org/content/repositories/orgapachehtrace-1021/
Can someone close this off? It would be hellish if someone were to release
it accidentally.
Thanks
Lewis

-- 
*Lewis*

Re: HTrace Site

[Lewis John Mcgibbney]

Hi Mike,
No it's just not been updated.
We should push up an update with both of the items below.
Can you lgo a Jira ticket please?
Thanks

On Mon, Apr 18, 2016 at 7:50 PM, <
dev-digest-h...@htrace.incubator.apache.org> wrote:

>
> From: Mike Drob 
> To: dev@htrace.incubator.apache.org
> Cc:
> Date: Mon, 18 Apr 2016 21:50:15 -0500
> Subject: HTrace Site
> HTrace Devs,
>
> I was browsing the project site[1] and noticed that it is very very old,
> having been last published over six months ago. However, there has been
> good activity on the HTRACE-350 Developer Guide and HTRACE-352 Dependency
> Info. Am I looking at the wrong page? Does my browser somehow have terrible
> caching going on?
>
> Thanks,
> Mike
>
> [1]: http://htrace.incubator.apache.org/
>
>


-- 
*Lewis*

Experiences Using Apache HTrace (Incubating) in Distributed Web Search

[Lewis John Mcgibbney]

Hi Folks,
A heads up that I sent in a proposal to Apache Big Data on the above topic.
Very pleased that it was accepted and I hope to be in Vancouver to share
experiences.
The is based on my ongoing work on
https://issues.apache.org/jira/browse/NUTCH-2005
I would like to share slides and get feedback closer to the event prior to
me submitting the slides so I will update this thread nearer the time.
Thanks for now.
Lewis

-- 
*Lewis*

Re: PRs submitted over public Github repo

[Lewis John Mcgibbney]

I am of the opinion that we should definitely have the PR's being shadowed
to this list.
It provides us with context about new contributions and more importantly
new community members.
Thanks Andrey for hitting the lists and letting us know about that.
I filed https://issues.apache.org/jira/browse/INFRA-11298 to address this.
Thanks

On Fri, Feb 19, 2016 at 3:22 PM, <
dev-digest-h...@htrace.incubator.apache.org> wrote:

>
> -- Forwarded message --
> From: Andrey Redko 
> To: dev@htrace.incubator.apache.org
> Cc:
> Date: Thu, 18 Feb 2016 07:47:50 -0500
> Subject: PRs submitted over public Github repo
> Hey Devs,
>
> I am wondering if anyone is watching the PRs submitted over public Github
> repo  (http://github.com/apache/incubator-htrace/)?
> Would be great to have some feedback on those.
> Thank you.
>
> Best Regards,
> Andriy Redko
>
>
>

Re: HTrace 4.1 release candidate 2

[Lewis John Mcgibbney]

Hi Colin,

+1 from me. All my usual tests have passed and I am happy with this RC.
Apologies for late review. This one dropped off the TODO list of TODO's :)
Good job Colin and team. :)

On Tue, Feb 9, 2016 at 7:00 PM,  wrote:

>
> Subject: HTrace 4.1 release candidate 2
> Hi all,
>
> I've posted the second release candidate for HTrace 4.1 here:
>
> http://people.apache.org/~cmccabe/htrace/releases/4.1.0/rc2/
>
> The jars have been staged here:
>
> https://repository.apache.org/content/repositories/orgapachehtrace-1022
>
> Compared to rc1, this rc includes HTRACE-334 and HTRACE-342.
>
> HTrace 4.1 brings a lot of robustness improvements.  There were major
> improvements to htraced and the web UI, as well as new metrics added.
> There were numerous build fixups, and we added Docker support, to
> ensure a repeatable build.
>
> Check it out.  The vote will run for 5 days.
>
> cheers,
> Colin

Re: state of the htrace

[Lewis John Mcgibbney]

Hi Colin,
Really cool. I was in Pasadena and sadly missed you and your presentation.
Maybe next time, please post here if you are presenting on HTrace again.
I wonder if anyone is planning on taking HTrace talks to ApacheCon?
Thanks

On Tue, Feb 2, 2016 at 4:51 PM,  wrote:

>
>
> Subject: state of the htrace
> Hi all,
>
> Happy (belated) New Year.  I've been a bit quiet since I went on
> vacation for a few weeks recently, and since I have some other
> projects going on.  But today I wanted to highlight some really cool
> stuff that's been happening in the HTrace and broader tracing
> community recently.
>
> Last weekend, I gave an "intro to htrace" talk this weekend at the
> Scale 14x Linux conference.  See
>
> https://www.socallinuxexpo.org/scale/14x/presentations/introducing-apache-htrace
> .  Also there is a video here:
> https://www.youtube.com/watch?v=t-TwCLwYIGE  It starts at 6:50, since
> the first few minutes of the recording are just me setting up the VGA
> connection and microphone :P  I thought this one went really well
> (especially the demo), and hopefully will get the word out to even
> more people.
>
> In HDFS, we've been exploring adding annotations to certain trace
> spans to collect even more useful information.  For example, Zhe Zhang
> posted a patch to HDFS-9576 to add "position" and "length" annotations
> to DFSInputStream#byteArrayRead, etc. spans.  This should give us data
> on things like the average and median read length in a set of HDFS
> requests.  Similarly, I posted HDFS-9674 which adds the "maximum write
> latency" to OpWriteBlock spans generated by the DataNode.  This is
> very handy when analyzing HDFS write pipelines.  I think we will see
> more of these really helpful annotations, and they will expand our
> ideas about what HTrace can do.
>
> A few weeks back, I wrote a blog post for my employer, Cloudera.  It
> talks about setting up HTrace and htraced on a CDH5.5 cluster.  See
>
> http://blog.cloudera.com/blog/2015/12/new-in-cloudera-labs-apache-htrace-incubating/
>  Hopefully HTrace can "bridge the chasm" between being a developer
> tool, and being a trusted ops tool.  We have some ways to go, but
> having these precompiled packages for CDH5.5 is a big step forward.
> (OK, I'll shut up about vendor stuff now...)
>
> Another really cool thing is that Sean Busbey and others in the YCSB
> community are working on integrating HTrace.  YCSB is a very popular
> benchmark for big data / Hadoopy workloads.  The github issue is here:
> https://github.com/brianfrankcooper/YCSB/issues/415
>
> cheers,
> Colin
>
>

Removing Old Artifacts from https://dist.apache.org/repos/dist/release/incubator/htrace/

[Lewis John Mcgibbney]

Hi Folks,
It is good practice to remove old artifacts from the URL below once a new
release is pushed.
Release are achived at archive.apache.org
https://dist.apache.org/repos/dist/release/incubator/htrace/
It might be confusing to a new user coming to HTrace if they see 4
artifacts for download.
We should only have the most recent.
Clearing out this directory should also be added to the release management
procedure.
Do you want me to log a Jira ticket?
Ta
Lewis


-- 
*Lewis*

HTrace for User Behavior Metrics

[Lewis John Mcgibbney]

Hi Folks,
I wonder if anyone has deployed tracing software for monitoring
browser-based user behaviour?
I know this is not HTrace but it is topically relevant I hope.
Thanks for any heads up.
Lewis


-- 
*Lewis*

[DISCUSS] Release for HTrace/Drive Towards Graduation

[Lewis John Mcgibbney]

Hi Team,
Quick thread from me here.
What is required to get another release of HTrace?
I see two issues are unresolved for 4.1 release
https://issues.apache.org/jira/browse/HTRACE/?selectedTab=com.atlassian.jira.jira-projects-plugin:issues-panel
I also see the rest of the issues assigned against no fix version.

One we sort this out then we could maybe think about touching the topic of
HTrace and graduation.
Thanks
Lewis

-- 
*Lewis*

Making Website Update Part of Release Process

[Lewis John Mcgibbney]

Hi Folks,
Excellent work on getting recent 4.0.0-incubating release out the door.
I wonder if there is documentation available for a release manager? If so
does it currently contain advice on how to update the HTrace website with
the info for the release?
Right now I don't even see the HTrace artifacts available
http://www.apache.org/dyn/closer.cgi/incubator/htrace/
I am assuming they are not available for public consumption yet.
Is this the case?
Thanks
Lewis

-- 
*Lewis*

Re: HTrace on Jira

[Lewis John Mcgibbney]

Hi Colin,

On Wed, Sep 9, 2015 at 12:44 AM, <
dev-digest-h...@htrace.incubator.apache.org> wrote:

>
> I'm not sure what you mean when you say that "most issues are not
> assigned to any release at all."  Pretty much every issue has a "fix
> version" which is the release it was fixed in, and an "affects
> version", which is the first release it appeared in.  Do you see any
> issues without those fields set?  If so, let's fill them in.
>

I mean the following. Take a look at the "Unresolved: By Version" area

https://issues.apache.org/jira/browse/HTRACE/?selectedTab=com.atlassian.jira.jira-projects-plugin:issues-panel

VersionIssues
4.1   3
Unscheduled   35

All but 3 issues are not even scheduled to be fixed for any particular
version. These should be assigned to the next project development drive
version should they not?



>
> One thing that frustrates me is that there is no "Target version:"
> field in our JIRA, like there is on Hadoop's JIRA.  I'm not sure what
> we have to configure to get a field like that.
>
>
I get your point. The above can be considered as synonymous to the Target
version your referring to. It serves the same purpose in this context.
Lewis

Re: [VOTE] HTrace 4.0 Release Candidate 0

[Lewis John Mcgibbney]

Hi Masatake,

On Wed, Sep 9, 2015 at 12:44 AM, <
dev-digest-h...@htrace.incubator.apache.org> wrote:

>
> HTRACE-234 was filed for this. Which version of Maven are you using?
>
>
lmcgibbn@LMC-032857 /usr/local(master) $ mvn -version
Apache Maven 3.3.3 (7994120775791599e205a5524ec3e0dfe41d4a06;
2015-04-22T04:57:37-07:00)
Maven home: /usr/local/apache-maven-3.3.3
Java version: 1.7.0_79, vendor: Oracle Corporation
Java home:
/Library/Java/JavaVirtualMachines/jdk1.7.0_79.jdk/Contents/Home/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "mac os x", version: "10.9.5", arch: "x86_64", family: "mac"

HTrace on Jira

[Lewis John Mcgibbney]

Hi Folks,
What is happening with versioning on Jira?
Master branch runs off of 4.0.0-incubating-SNAPSHOT, the only version which
exists within Jira is 4.1.
Most issues are not assigned to any release at all.
Can someone sort it out and we could potentially set a roadmap for
releasing HTrace 4.0/4.0.0-incubating?
Thanks folks
lewis

-- 
*Lewis*

Re: [VOTE] Release Apache htrace-3.2.0-incubating

[Lewis John Mcgibbney]

Yes definitely lets get one out. Good job folks.

On Tuesday, June 2, 2015, Abraham Elmahrek a...@cloudera.com wrote:

 Hey man,

 Good point. Should we send out an announce email even though it's a few
 weeks after the fact?

 -Abe

 On Wed, Jun 3, 2015 at 1:10 AM, Nick Dimiduk ndimi...@gmail.com
 javascript:; wrote:

  Hi folks. Looks like this vote passed, but I haven't seen a release
  announcement. Am I missing something?
 
  Thanks,
  Nick
 
  On Wed, May 13, 2015 at 7:16 PM, Abraham Elmahrek a...@cloudera.com
 javascript:;
  wrote:
 
   Closing the vote.
  
   [7] +1 - 6 Were binding I believe. Please correct me if I am mistaken.
   [0]   0
   [0]  -1
  
   Thanks for participating folks.
  
   On Mon, May 11, 2015 at 11:04 PM, Colin McCabe cmcc...@alumni.cmu.edu
 javascript:;
   wrote:
  
Downloaded.  Verified hashes.
Ran unit tests
Installed and built Hadoop trunk against it
Verified that HDFS integration and htraced worked
   
+1.
   
cheers,
Colin
   
On Mon, May 11, 2015 at 7:01 PM, Jake Farrell jfarr...@apache.org
 javascript:;
   wrote:
 Carrying my +1 (binding) over from the dev list

 -Jake

 On Sat, May 9, 2015 at 9:54 PM, Abraham Elmahrek a...@apache.org
 javascript:;
   wrote:

 Apache HTrace (incubating), after 2 release candidates, has voted
 to
 release the below referenced Apache HTrace 3.2.0-incubating
 release
 candidate.

 Dear IPMC, please vote on our second release candidate as an
 Apache
 Incubator project.

 Here is the vote thread we ran on our dev list (Six binding +1
 votes
and no
 -1 votes) with
 a subject: [VOTE] HTrace 3.2.0 - Release Candidate 2, second
  release
 candidate

 *


   
  
 
 http://mail-archives.apache.org/mod_mbox/incubator-htrace-dev/201505.mbox/%3CCAOvM-ciKd82bt3ze7oZD9FnNUcss8T%2BufwwgEndrhpnnOdgMNA%40mail.gmail.com%3E
 


   
  
 
 http://mail-archives.apache.org/mod_mbox/incubator-htrace-dev/201505.mbox/%3CCAOvM-ciKd82bt3ze7oZD9FnNUcss8T%2BufwwgEndrhpnnOdgMNA%40mail.gmail.com%3E
 *

 The source tarball, hashes, and signing are here:

   http://people.apache.org/~abe/htrace/releases/3.2.0/rc1/

 (Over in htrace our RC number was zero based so RC1 == second RC)

 Related maven artifacts are posted here:


   
  https://repository.apache.org/content/repositories/orgapachehtrace-1016

 The tag for the RC is here:


   
  
 
 https://git-wip-us.apache.org/repos/asf?p=incubator-htrace.git;a=tag;h=44fa6e0cd7456b5725b8557161f68b851fdf75d8

 The KEYS file with the key used signing is available here:

 *https://dist.apache.org/repos/dist/release/incubator/htrace/KEYS
 https://dist.apache.org/repos/dist/release/incubator/htrace/KEYS
 *


 75 issues were closed/resolved for this release:



   
  
 
 https://issues.apache.org/jira/issues/?jql=project%20%3D%20HTRACE%20AND%20status%20%3D%20resolved%20AND%20fixVersion%20%3D%203.2.0%20ORDER%20BY%20issuetype%20DESC


 The vote will be open for 96 hours.

 [ ] +1 Release this package as Apache HTrace 3.2.0-incubating
 [ ] +0 no opinion
 [ ] -1 Do not release this package because ...


 Thanks,
 Abe

   
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
 javascript:;
For additional commands, e-mail: general-h...@incubator.apache.org
 javascript:;
   
   
  
 



-- 
*Lewis*

Re: HTrace 3.2+ zipkin namespace issues

[Lewis John Mcgibbney]

Ho Daniel,
Thanks for taking the time to write here.
The preferred method is to log an issue in Jira at
https://issues.apache.org/jira/browse/htrace
You can then work on a patch(ES) and attach it there or alternatively
create a pull request In a new branch against the Github mirror at

https://github.com/apache/incubator-htrace

Thanks
Lewis
On Sunday, May 31, 2015, Daniel Lee dan...@slice.com wrote:

 Hi,

 I recently became aware of htrace and have begun testing it but ran
 into an issue pretty quickly when moving from 3.1 to 3.2. In commit
 f425e63 (HTRACE-90) the maven shade plugin is introduced to the build
 process. As a result, the jar artifacts available have a bunch of
 dependencies pulled into the global namespace which is causing clashes
 and compile/runtime errors.

 Downloading the jar from maven central we can see that there are many
 things in there including org/apache/http/ and org/slf4j/.

 wget
 http://central.maven.org/maven2/org/apache/htrace/htrace-zipkin/3.2.0-incubating/htrace-zipkin-3.2.0-incubating.jar
 jar tf htrace-zipkin-3.2.0-incubating.jar | sed s:/[^/]*\.[^.]*:/: |
 sort | uniq

 Currently I'm just modifying the pom to shade all the extra
 dependencies but I was wonder what were the long term plans for this.

 I've also been updating the Trace class with missing Span setX
 functionality and was wondering if the preferred way to submit patches
 was through bug reports of through posts to the mailing list.

 Daniel



-- 
*Lewis*

NUTCH-2005

[Lewis John Mcgibbney]

Hi Folks,
Looks like I may finally get around to HTracin' Nutch :)
https://issues.apache.org/jira/browse/NUTCH-2005
Will keep the list updated.
Thanks
Lewis

-- 
*Lewis*

Re: [VOTE] HTrace 3.2.0 - Release Candidate 2

[Lewis John Mcgibbney]

Hi Folks,
I ran DRAT over the codebase

  Notes Binaries Archives Standards Apache Generated Unknown  0 0 0 120 83 0
28

28 unknown licenses flagged up

Upon further investigation these were

Unapproved licenses:

  /usr/local/drat/deploy/data/jobs/rat/1430960456935/input/backbone-1.1.2.js
  
/usr/local/drat/deploy/data/jobs/rat/1430960456935/input/backbone.marionette-2.4.1.min.js
  
/usr/local/drat/deploy/data/jobs/rat/1430960456935/input/backbone.paginator-2.0.2.js
  /usr/local/drat/deploy/data/jobs/rat/1430960456935/input/backgrid-0.3.5.js
  
/usr/local/drat/deploy/data/jobs/rat/1430960456935/input/backgrid-paginator-0.3.5.js
  /usr/local/drat/deploy/data/jobs/rat/1430960456935/input/bootstrap.js
  /usr/local/drat/deploy/data/jobs/rat/1430960456935/input/bootstrap.min.js
  /usr/local/drat/deploy/data/jobs/rat/1430960456935/input/d3-3.5.5.js
  /usr/local/drat/deploy/data/jobs/rat/1430960456935/input/d3.min.js
  /usr/local/drat/deploy/data/jobs/rat/1430960456935/input/jquery-2.1.3.min.js
  /usr/local/drat/deploy/data/jobs/rat/1430960456935/input/moment-2.9.0.min.js
  /usr/local/drat/deploy/data/jobs/rat/1430960456935/input/npm.js
  /usr/local/drat/deploy/data/jobs/rat/1430960456935/input/rome.js
  /usr/local/drat/deploy/data/jobs/rat/1430960456935/input/rome.min.js
  /usr/local/drat/deploy/data/jobs/rat/1430960456935/input/rome.standalone.js
  
/usr/local/drat/deploy/data/jobs/rat/1430960456935/input/rome.standalone.min.js
  /usr/local/drat/deploy/data/jobs/rat/1430960456935/input/underscore-1.7.0.js

  
/usr/local/drat/deploy/data/jobs/rat/1430960457357/input/backgrid-0.3.5.min.css
  
/usr/local/drat/deploy/data/jobs/rat/1430960457357/input/backgrid-paginator-0.3.5.min.css
  /usr/local/drat/deploy/data/jobs/rat/1430960457357/input/bootstrap-theme.css
  
/usr/local/drat/deploy/data/jobs/rat/1430960457357/input/bootstrap-theme.min.css
  /usr/local/drat/deploy/data/jobs/rat/1430960457357/input/bootstrap.css
  /usr/local/drat/deploy/data/jobs/rat/1430960457357/input/bootstrap.min.css
  /usr/local/drat/deploy/data/jobs/rat/1430960457357/input/rome.css
  /usr/local/drat/deploy/data/jobs/rat/1430960457357/input/rome.min.css

  /usr/local/drat/deploy/data/jobs/rat/1430960456828/input/SpanProtos.java

  
/usr/local/drat/deploy/data/jobs/rat/1430960457162/input/dependency-reduced-pom.xml
  
/usr/local/drat/deploy/data/jobs/rat/1430960457162/input/dependency-reduced-pom.xml_05062015_1800

If we can clarify the above then I am +1 to the release.

There's nothing more I can add over and above what has been stated by
others.
SIGS check
Builds and Tests in native check
Nice release candidate.
Thanks
Lewis


On Thu, Apr 30, 2015 at 9:16 PM, Abraham Elmahrek a...@apache.org wrote:

 I've the second release candidate here:

   *http://people.apache.org/~abe/htrace/releases/3.2.0/rc1/
 http://people.apache.org/~abe/htrace/releases/3.2.0/rc1/*

 The jars have been staged here:

   *https://repository.apache.org/content/repositories/orgapachehtrace-1016
 https://repository.apache.org/content/repositories/orgapachehtrace-1016*

 This release improves the Java client with better error checking and
 setting parents in a span after the span is created. Also, some issues in
 the local file span receiver are fixed and work has started on a new C/C++
 native client.

 Please vote +1/0/-1 by Friday, May 7th, 2015.

 Thanks,
 Abe

 1.

 https://issues.apache.org/jira/issues/?jql=fixVersion%20%3D%203.2.0%20AND%20project%20%3D%20HTRACE%20AND%20status%20%3D%20Resolved%20ORDER%20BY%20priority%20DESC


 Release Notes - HTrace - Version 3.2.0

 ** Sub-task
 * [HTRACE-44] - Add htraced web UI search page skeleton
 * [HTRACE-45] - Add Span details page skeleton
 * [HTRACE-75] - UI should query htraced
 * [HTRACE-76] - Search page: Add +/- filters to search control
 * [HTRACE-77] - htraced gui: add pagination to the search page.
 * [HTRACE-78] - Search page: Enhance begin time and end time selection
 widget
 * [HTRACE-79] - Search page: Make list more tabular with sorting on
 front end
 * [HTRACE-108] - Search Page: Use server side pagination
 * [HTRACE-121] - Details page: Graph parents and children
 * [HTRACE-131] - Port spans.js in htrace-hbase to htraced
 * [HTRACE-134] - Port front end to marionette JS
 * [HTRACE-142] - Details page: Update graph
 * [HTRACE-146] - Search page: Remove client-side sorting and improve
 pagination

 ** Bug
 * [HTRACE-32] - Change span timeline annotations map to be a
 mapstring, string
 * [HTRACE-37] - htraced: serve index.html if the root URL was given
 * [HTRACE-47] - Add Content-Type header in REST server
 * [HTRACE-48] - use -L 1 in format.sh to make it work on macosx
 * [HTRACE-52] - FIgure out content-type handling in JSON API
 * [HTRACE-55] - Add Clean command to htrace go
 * [HTRACE-57] - Fix LocalFileSpanReceiver to avoid adding irrelevant
 wrapper object
 * [HTRACE-68] - Clean up LocalFileSpanReceiver and 

Re: [VOTE] HTrace 3.2.0 - Release Candidate 2

[Lewis John Mcgibbney]

I would say no, don't roll a new RC.
If there is a way to ensure that generated files have ALv2.0 headers moving
forward and committed to trunk then that would be my advice.
Good job with RC.
+1 from me

On Wednesday, May 6, 2015, Abraham Elmahrek a...@cloudera.com wrote:

 Lewis,

 These are third party packages and a generated file. The JS dependencies
 are listed in LICENSE.txt. I don't see licenses for
 dependency-reduced-pom.xml in general... but I think it might be generated
 by the maven shading plugin. It looks like some of these generated files
 made it into the source tarball. Do you guys think it's worth spinning a
 new RC for this?

 -Abe

 On Wed, May 6, 2015 at 6:05 PM, Lewis John Mcgibbney 
 lewis.mcgibb...@gmail.com javascript:; wrote:

  Hi Folks,
  I ran DRAT over the codebase
 
Notes Binaries Archives Standards Apache Generated Unknown  0 0 0 120
 83
  0
  28
 
  28 unknown licenses flagged up
 
  Upon further investigation these were
 
  Unapproved licenses:
 
 
 
 /usr/local/drat/deploy/data/jobs/rat/1430960456935/input/backbone-1.1.2.js
 
 
 /usr/local/drat/deploy/data/jobs/rat/1430960456935/input/backbone.marionette-2.4.1.min.js
 
 
 /usr/local/drat/deploy/data/jobs/rat/1430960456935/input/backbone.paginator-2.0.2.js
 
 
 /usr/local/drat/deploy/data/jobs/rat/1430960456935/input/backgrid-0.3.5.js
 
 
 /usr/local/drat/deploy/data/jobs/rat/1430960456935/input/backgrid-paginator-0.3.5.js
/usr/local/drat/deploy/data/jobs/rat/1430960456935/input/bootstrap.js
 
  /usr/local/drat/deploy/data/jobs/rat/1430960456935/input/bootstrap.min.js
/usr/local/drat/deploy/data/jobs/rat/1430960456935/input/d3-3.5.5.js
/usr/local/drat/deploy/data/jobs/rat/1430960456935/input/d3.min.js
 
 
 /usr/local/drat/deploy/data/jobs/rat/1430960456935/input/jquery-2.1.3.min.js
 
 
 /usr/local/drat/deploy/data/jobs/rat/1430960456935/input/moment-2.9.0.min.js
/usr/local/drat/deploy/data/jobs/rat/1430960456935/input/npm.js
/usr/local/drat/deploy/data/jobs/rat/1430960456935/input/rome.js
/usr/local/drat/deploy/data/jobs/rat/1430960456935/input/rome.min.js
 
 
 /usr/local/drat/deploy/data/jobs/rat/1430960456935/input/rome.standalone.js
 
 
 /usr/local/drat/deploy/data/jobs/rat/1430960456935/input/rome.standalone.min.js
 
 
 /usr/local/drat/deploy/data/jobs/rat/1430960456935/input/underscore-1.7.0.js
 
 
 
 /usr/local/drat/deploy/data/jobs/rat/1430960457357/input/backgrid-0.3.5.min.css
 
 
 /usr/local/drat/deploy/data/jobs/rat/1430960457357/input/backgrid-paginator-0.3.5.min.css
 
 
 /usr/local/drat/deploy/data/jobs/rat/1430960457357/input/bootstrap-theme.css
 
 
 /usr/local/drat/deploy/data/jobs/rat/1430960457357/input/bootstrap-theme.min.css
/usr/local/drat/deploy/data/jobs/rat/1430960457357/input/bootstrap.css
 
 
 /usr/local/drat/deploy/data/jobs/rat/1430960457357/input/bootstrap.min.css
/usr/local/drat/deploy/data/jobs/rat/1430960457357/input/rome.css
/usr/local/drat/deploy/data/jobs/rat/1430960457357/input/rome.min.css
 
 
  /usr/local/drat/deploy/data/jobs/rat/1430960456828/input/SpanProtos.java
 
 
 
 /usr/local/drat/deploy/data/jobs/rat/1430960457162/input/dependency-reduced-pom.xml
 
 
 /usr/local/drat/deploy/data/jobs/rat/1430960457162/input/dependency-reduced-pom.xml_05062015_1800
 
  If we can clarify the above then I am +1 to the release.
 
  There's nothing more I can add over and above what has been stated by
  others.
  SIGS check
  Builds and Tests in native check
  Nice release candidate.
  Thanks
  Lewis
 
 
  On Thu, Apr 30, 2015 at 9:16 PM, Abraham Elmahrek a...@apache.org
 javascript:; wrote:
 
   I've the second release candidate here:
  
 *http://people.apache.org/~abe/htrace/releases/3.2.0/rc1/
   http://people.apache.org/~abe/htrace/releases/3.2.0/rc1/*
  
   The jars have been staged here:
  
 *
  https://repository.apache.org/content/repositories/orgapachehtrace-1016
   
 https://repository.apache.org/content/repositories/orgapachehtrace-1016
  *
  
   This release improves the Java client with better error checking and
   setting parents in a span after the span is created. Also, some issues
 in
   the local file span receiver are fixed and work has started on a new
  C/C++
   native client.
  
   Please vote +1/0/-1 by Friday, May 7th, 2015.
  
   Thanks,
   Abe
  
   1.
  
  
 
 https://issues.apache.org/jira/issues/?jql=fixVersion%20%3D%203.2.0%20AND%20project%20%3D%20HTRACE%20AND%20status%20%3D%20Resolved%20ORDER%20BY%20priority%20DESC
  
  
   Release Notes - HTrace - Version 3.2.0
  
   ** Sub-task
   * [HTRACE-44] - Add htraced web UI search page skeleton
   * [HTRACE-45] - Add Span details page skeleton
   * [HTRACE-75] - UI should query htraced
   * [HTRACE-76] - Search page: Add +/- filters to search control
   * [HTRACE-77] - htraced gui: add pagination to the search page.
   * [HTRACE-78] - Search page: Enhance begin time and end time
  selection
   widget
   * [HTRACE-79] - Search page: Make list more

Re: [VOTE] HTrace 3.2.0 - Release Candidate 0

[Lewis John Mcgibbney]

Good catch Billie

http://incubator.apache.org/guides/releasemanagement.html#check-list

This is going to be a problem

On Thursday, April 30, 2015, Billie Rinaldi bil...@apache.org wrote:

 There are some compiled class files in the src tarball in the
 htrace-htraced/bin directory.  That's the only issue I can see, though.
 The LICENSE and NOTICE look good to me -- kudos!


 htrace-3.2.0-incubating/htrace-htraced/bin/org/apache/htrace/impl/HTracedRESTReceiver$PostSpans.class

 htrace-3.2.0-incubating/htrace-htraced/bin/org/apache/htrace/impl/HTracedRESTReceiver.class

 htrace-3.2.0-incubating/htrace-htraced/bin/org/apache/htrace/impl/TestHTracedRESTReceiver$TestHTraceConfiguration.class

 htrace-3.2.0-incubating/htrace-htraced/bin/org/apache/htrace/impl/TestHTracedRESTReceiver.class

 htrace-3.2.0-incubating/htrace-htraced/bin/org/apache/htrace/util/DataDir.class

 htrace-3.2.0-incubating/htrace-htraced/bin/org/apache/htrace/util/HTracedProcess.class

 htrace-3.2.0-incubating/htrace-htraced/bin/org/apache/htrace/util/TestHTracedProcess.class


 On Tue, Apr 28, 2015 at 2:46 PM, Abraham Elmahrek a...@cloudera.com
 javascript:; wrote:

  I've posted our first release candidate here:
 
http://people.apache.org/~abe/htrace/releases/3.2.0/
 
  The jars have been staged here:
 
 
 https://repository.apache.org/content/repositories/orgapachehtrace-1015
 
  This release improves the Java client with better error checking and
  setting parents in a span after the span is created. Also, some issues in
  the local file span receiver are fixed and work has started on a new
 C/C++
  native client.
 
  Please vote +1/0/-1 by Friday, May 1st, 2015.
 
  Thanks,
  Abe
 
  1.
 
 
 https://issues.apache.org/jira/issues/?jql=fixVersion%20%3D%203.2.0%20AND%20project%20%3D%20HTRACE%20AND%20status%20%3D%20Resolved%20ORDER%20BY%20priority%20DESC
 
 
  Release Notes - HTrace - Version 3.2.0
 
  ** Sub-task
  * [HTRACE-44] - Add htraced web UI search page skeleton
  * [HTRACE-45] - Add Span details page skeleton
  * [HTRACE-75] - UI should query htraced
  * [HTRACE-76] - Search page: Add +/- filters to search control
  * [HTRACE-77] - htraced gui: add pagination to the search page.
  * [HTRACE-78] - Search page: Enhance begin time and end time
 selection
  widget
  * [HTRACE-79] - Search page: Make list more tabular with sorting on
  front end
  * [HTRACE-108] - Search Page: Use server side pagination
  * [HTRACE-121] - Details page: Graph parents and children
  * [HTRACE-131] - Port spans.js in htrace-hbase to htraced
  * [HTRACE-134] - Port front end to marionette JS
  * [HTRACE-142] - Details page: Update graph
  * [HTRACE-146] - Search page: Remove client-side sorting and improve
  pagination
 
  ** Bug
  * [HTRACE-32] - Change span timeline annotations map to be a
  mapstring, string
  * [HTRACE-37] - htraced: serve index.html if the root URL was given
  * [HTRACE-47] - Add Content-Type header in REST server
  * [HTRACE-48] - use -L 1 in format.sh to make it work on macosx
  * [HTRACE-52] - FIgure out content-type handling in JSON API
  * [HTRACE-55] - Add Clean command to htrace go
  * [HTRACE-57] - Fix LocalFileSpanReceiver to avoid adding irrelevant
  wrapper object
  * [HTRACE-68] - Clean up LocalFileSpanReceiver and
 SpanReceiverBuilder
  a bit
  * [HTRACE-71] - format.sh: only format src/ directory
  * [HTRACE-90] - Remove Guava and shade other depdendencies in HTrace
  subprojects
  * [HTRACE-93] - Add null check to SamplerBuilder
  * [HTRACE-97] - Support both -D and --D when specifying conf vars on
  the command-line
  * [HTRACE-98] - Web Server should use PrefixHandler
  * [HTRACE-99] - log.go fails to create new log files
  * [HTRACE-100] - htraced: put query parameters in the URL, not in the
  GET request body
  * [HTRACE-101] - Add better error-checking to Java HTrace client
  * [HTRACE-103] - Reset unclosed spans after TestBadClient
  * [HTRACE-107] - Support for Greater Than operator in htraced
  * [HTRACE-109] - fix TestHTracedRESTReceiver unit test failures
  * [HTRACE-110] - Fix rat check failure due to
  dependency-reduced-pom.xml in htrace-hbase
  * [HTRACE-111] - HTrace Java client API fixes for 3.2
  * [HTRACE-112] - Fix LocalFileSpanReceiver to avoid BG thread and
  problems around close()
  * [HTRACE-115] - The htraced datastore should use uint64 for span ids
  rather than int64
  * [HTRACE-116] - htraced's data.store.clear option does not work
  * [HTRACE-117] - graph.go: sort children array to get deterministic
  output
  * [HTRACE-118] - Java API: support setting the parents of a span
 after
  the span is created
  * [HTRACE-119] - detach of NullScope singleton should not fail
  * [HTRACE-123] - fix graphviz functionality in the htrace command
  * [HTRACE-126] - BUILDING.txt should not say that godep is required,
  because we 

Re: releasing native build artifacts

[Lewis John Mcgibbney]

Hi Colin,
My understanding is that none of this is yet established on builds.a.o is
this correct?
https://builds.apache.org/view/H-L/view/HBase/
Maybe it would be a nice opportunity to get that sorted out as well.
Lewis

On Thu, Apr 23, 2015 at 11:46 AM, Colin P. McCabe cmcc...@apache.org
wrote:

 Hi all,

 Based on the responses in the earlier thread, it sounds like it's
 getting to be about that time again... time for a new HTrace release
 :)

 I've been thinking about what we should do with our native build
 artifacts.  With Java, we only ever have to build one version of
 everything, since the jar files can run on any architecture and
 supported OS.  But we now have a C client (which is only at an alpha
 level of stability, but still...) and the htraced server, which is
 also not Java.

 Do we want to do builds of this stuff for the common OS/arch
 configurations?  If we did a RHEL6 / x86_64 build and an Ubuntu 12.04
 / x86_64 build, that would cover most of our users, I think.  We could
 also do 32-bit builds, but I don't think anyone is actually using
 32-bit any more in big data land (and if they are, they need to stop
 :)

 This also means we would have 3 downloads available in the next release:
 * Just jar files + source
 * Jar files + source + RHEL6/x86_64 libhtrace.so + htraced
 * Jar files + source + Ubuntu 12.04/x86_64 libhtrace.so + htraced

 thoughts?

 Colin




-- 
*Lewis*

Re: Apache Phoenix Tracing Dashboard-jira issue PHOENIX 1118

[Lewis John Mcgibbney]

Ayola,
Did you apply to GSoC with this?
The submissions window is now closed!
Lewis

On Wednesday, April 22, 2015, Ayola Jayamaha raphaelan...@gmail.com wrote:

 Hi All,

 I'm a University Student applying for the GSOC Project [1] Dashboard for
 tracing information in Phoenix. In Apache Phoenix, HTrace is used to
 provide request level trace information.
 Below are the trace information found in Phoenix Table.

-   trace_id
-   parent_id
-   span_id
-   description
-   start_time
-   end_time
-   hostname
-   tags.count
-   annotations.count

 HTrace library is integrated with HBase tracing utilities. And HTrace
 latest release 3.2.0 will include many visualization improvements[2].

 You can find the Mock Up UI [3] which gives advance search capabilities for
 trace attributes and slider functionality[4] to view the trace for the
 selected time period with zooming capabilities and parent trace info on
 display.

 A web UI is the solution proposed and a dashboard will show the required
 information.

 Can the Phoenix SYSTEM.TRACING_STATS table be made available in the htrace
 web gui? Which will further cater for the needs of visualizing the trace
 info as the Mock Up UIs suggest.

 Pagination will be tackled in the visualization of the tracing.

 [1] https://issues.apache.org/jira/browse/PHOENIX-1118
 [2]

 http://mail-archives.apache.org/mod_mbox/htrace-dev/201504.mbox/%3cca+qbeuny9f9zloutoiefb9lekzvbkmkwzrjw52_5-u8jka+...@mail.gmail.com%3E
 [3]

 https://issues.apache.org/jira/secure/attachment/12726864/MockUp2-AdvanceSearch.png
 [4]

 https://issues.apache.org/jira/secure/attachment/12726863/MockUp1-TimeSlider.png

 --
 Best Regards,
 Ayola Jayamaha
 http://ayolajayamaha.blogspot.com/



-- 
*Lewis*

Re: htrace gui meeting minutes

[Lewis John Mcgibbney]

Sorry I didn't make it folks.
Thank you for notes.
Anyone apart from Colin going to ApachCon? I would really like to hook up
and get drunk and talk grace, etc.
I'll be in Austin Sunday, Monday, Tuesday leaving Tuesday night.
Chris Mattmann and myself are hosting the science and healthcare track. So
I'll be around that crowd.
Lewis

On Friday, April 3, 2015, Abraham Elmahrek a...@cloudera.com wrote:

 Thanks for putting this together Colin. It was really useful!

 On Fri, Apr 3, 2015 at 6:57 PM, Colin P. McCabe cmcc...@apache.org
 javascript:; wrote:

  We had: Abe, Colin, May, Masatake in attendance.
 
  We talked about more closely integrating the search page with the
  swimlanes view.  In particular, would it be possible to have them be
  one view?  Maybe.  We need zoom buttons, time delineation bars, and
  some other minor features in the swimlanes view.   We talked about
  having parent/child relationships shown on this view.
 
  Pagination has been a trouble spot for the search page.  We need to
  use entire spans as continuation tokens, and correctly handle cases
  where we are sorting by a key other than span id.  It would be nice if
  the web UI could fetch 4 pages worth of results, in order to give the
  user an idea of whether there were many results, or only a few.  This
  may be difficult to do with backgrid.js.
 
  It would also be nice to be able to click on a span in the view to see
  its children (May's suggestion).  This may also be difficult with
  backgrid, but it would be really cool.
 
  We talked about having tabs to move between different activities.  The
  ones discussed were server info, configuration, search, and
  aggregrates.
 
  server info: The server info tab must contain an owl.  We already have
  a serverinfo JSON RPC, so this could be used.  We might also want
  server stats on this page eventually.
 
  configuration: It would be nice to have the configuration page
  accessible via /conf, for familiarity to hadoop admins.  This would
  show the htraced configuration.
 
  aggregates: this view would provide all the same predicates as the
  search view, but would allow users to choose an aggregate from a
  drop-down list.  Examples include: average, median, std deviation,
  max, min, count.  We also would want a bucket size.  One really great
  example is taking the sum of the number of spans within each 10 minute
  interval in the last 24 hours, to see activity spikes.  We may need to
  think about whether this puts too much load on the server.  if so,
  we'd have to precompute a few aggregates, or do this outside htraced.
  The histogram view is a later target than the other views.
 
  best,
  Colin
 



-- 
*Lewis*

Re: HTrace GUI meetup

[Lewis John Mcgibbney]

I'll try my best to be there as well folks. I've got it in my calendar and
will make best efforts to be online. Thanks

On Friday, March 27, 2015, Colin McCabe cmcc...@alumni.cmu.edu wrote:

 Great.  4/3 at 5PM PDT sounds like the time, then.  Lewis, does that
 work for you?

 On Fri, Mar 27, 2015 at 4:49 PM, Masatake Iwasaki
 iwasak...@oss.nttdata.co.jp javascript:; wrote:
  Hmm.  Sounds like May is unavailable on Tuesday.  Does Friday (4/3) at
  5PM PDT work for everyone?  Masatake, I'd especially like to talk to
  you about some ideas for the spans GUI...
 
  4/3 is ok for me.
  I'm in JST now and will join by Hangouts.
  I appreciate if you forward voice to Hangouts.

 It might be a bit tough to have audio on both hangouts and webex.  We
 tend to get the echo chamber effect when we try to do that.  I can
 understand the desire not to make an international call, though.
 Maybe let's just forget about the phone connection and just do
 hangouts.  If we run into problems we can try something else at that
 point.

 I will try to get a hardline (i.e. non-wifi) so maybe the VoIP will work
 out.

 cheers.
 Colin


 
  Masatake
 
 
 
  On 3/28/15 03:19, Colin P. McCabe wrote:
  Hmm.  Sounds like May is unavailable on Tuesday.  Does Friday (4/3) at
  5PM PDT work for everyone?  Masatake, I'd especially like to talk to
  you about some ideas for the spans GUI...
 
  Abe, to respond to your points: We will post the minutes to the
  mailing list.  Also, obviously the actual implementation of any of
  these ideas will happen on JIRA through the usual process.  I view
  this as kind of similar to the meetings we do occasionally on Hadoop
  to coordinate a new feature that the community is working on.
 
  Also, on a semi-related note, I'm going to try to check some
  real-world span data into the repo to use when looking at the GUI.
 
  cheers,
  Colin
 
 
  On Thu, Mar 26, 2015 at 3:46 PM, Abraham Elmahrek a...@cloudera.com
 javascript:;
  wrote:
  Hey Colin,
 
  I'm hugely +1 on this! I'd prefer Tuesday @ 5PM PST.
 
  There has been some discussion about doing this in the Sqoop community
 as
  well, so I thought I'd relay some of the ideas that popped up there (
 
 
 http://mail-archives.apache.org/mod_mbox/sqoop-dev/201502.mbox/%3CCAHUddLM98%3DM4N4qNGfpAThQ%2BEpRf0war0FN4WM%3D3T6t7Owt4nQ%40mail.gmail.com%3E
  ):
 
 1. Meeting minutes are persisted (wiki) and communicated (mailing
  list)
 2. No concrete decisions are made (we should run votes first so
 every
 one can participate and make sure full context is provided some how)
 3. Proper notice is given to the community and the meeting is
 globally
 available (which it seems we have).
 
  I think HTrace is a different community and can run it however we see
  fit.
  But I hope the above helps at least for reference.
 
  -Abe
 
  On Thu, Mar 26, 2015 at 3:29 PM, Colin P. McCabe cmcc...@apache.org
 javascript:;
  wrote:
 
  Hi all,
 
  There's been a lot of really great work on the HTrace GUI recently.
  Masatake's span visualization screen, Abe's work on the details page,
  and May's work come to mind.
 
  I was thinking, we should have a phone call to talk about the GUI.  I
  have some ideas that might be really cool.  Abe also came up with some
  mockups.
 
  Some time next week would work well for me.  Maybe next Tuesday (3/31)
  at 5pm, or next Friday (4/3) at 5pm PST?  (I realize 5pm PST is late
  in California but I'm trying to come up with something that works for
  all the time zones.)  Does that work for you guys?
 
  I'm thinking we can provide a plain ol' telephone dial-in number and
  use Google Hangouts for screen sharing.  (We could use Google Hangouts
  for voice as well, but in my experience, it's best to use regular
  phone for voice to avoid glitches.)
 
  best,
  Colin
 
 



-- 
*Lewis*

Re: HTrace GUI meetup

[Lewis John Mcgibbney]

I would be super interested in joining.
I'll look out for something more concrete.


On Thursday, March 26, 2015, may...@outlook.com wrote:

 Next Friday ought to be fine





 Sent by Outlook for Android




 On Thu, Mar 26, 2015 at 3:50 PM -0700, may...@outlook.com javascript:;
 wrote:
 Unavailable Tuesday. Have another event.

 Sent by Outlook for Android




 On Thu, Mar 26, 2015 at 3:29 PM -0700, Colin P. McCabe 
 cmcc...@apache.org javascript:; wrote:
 Hi all,

 There's been a lot of really great work on the HTrace GUI recently.
 Masatake's span visualization screen, Abe's work on the details page,
 and May's work come to mind.

 I was thinking, we should have a phone call to talk about the GUI.  I
 have some ideas that might be really cool.  Abe also came up with some
 mockups.

 Some time next week would work well for me.  Maybe next Tuesday (3/31)
 at 5pm, or next Friday (4/3) at 5pm PST?  (I realize 5pm PST is late
 in California but I'm trying to come up with something that works for
 all the time zones.)  Does that work for you guys?

 I'm thinking we can provide a plain ol' telephone dial-in number and
 use Google Hangouts for screen sharing.  (We could use Google Hangouts
 for voice as well, but in my experience, it's best to use regular
 phone for voice to avoid glitches.)

 best,
 Colin



-- 
*Lewis*

Re: Getting started with Apache HTrace development

[Lewis John Mcgibbney]

This is dynamite and I think it would be very helpful to have it linked to
from the website.
Although the install and config doesn't appear too bulky, there are a
number of steps and this would be non trivial for someone who is not
familiarized with Hadoop xml based runtime configuration.
I'm finishing off a patch for Chukwa right now then I will be building
HTtace into my Nutxh 2.x search stack. My aim is to write something similar
for that deployment as R would also be very helpful to see tracing for Gora
data stores as well.

On Monday, March 2, 2015, Colin P. McCabe cmcc...@apache.org wrote:

 A few people have asked how to get started with HTrace development.  It's a
 good question and we don't have a great README up about it so I thought I
 would
 write something.

 HTrace is all about tracing distributed systems.  So the best way to get
 started is to plug htrace into your favorite distributed system and see
 what
 cool things happen or what bugs pop up.  Since I'm an HDFS developer,
 that's
 the distributed system that I'm most familiar with.  So I will do a quick
 writeup about how to use HTrace + HDFS.  (HBase + HTrace is another very
 important use-case that I would like to write about later, but one step at
 a
 time.)

 Just a quick note: a lot of this software is relatively new.  So there may
 be
 bugs or integration pain points that you encounter.

 There has not yet been a stable release of Hadoop that contained Apache
 HTrace.
 There have been releases that contained the pre-Apache version of HTrace,
 but
 that's no fun.  If we want to do development, we want to be able to run the
 latest version of the code.  So we will have to build it ourselves.

 Building HTrace is not too bad.  First we install the dependencies:

 cmccabe@keter:~/ apt-get install java javac google-go leveldb-devel

 If you have a different Linux distro this command will vary slightly, of
 course.  On Macs, brew is a good option.
 Next we use Maven to build the source:

   cmccabe@keter:~/ git clone
 https://git-wip-us.apache.org/repos/asf/incubator-htrace.git
   cmccabe@keter:~/ cd incubator-htrace
   cmccabe@keter:~/ git checkout master
   cmccabe@keter:~/ mvn install -DskipTests -Dmaven.javadoc.skip=true
 -Drat.skip

 OK.  So htrace is built and installed to the local ~/.m2 directory.

 We should see it under the .m2:
 cmccabe@keter:~/ find ~/.m2 | grep htrace-core
 ...
  
 /home/cmccabe/.m2/repository/org/apache/htrace/htrace-core/3.2.0-SNAPSHOT
  

 /home/cmccabe/.m2/repository/org/apache/htrace/htrace-core/3.2.0-SNAPSHOT/htrace-core-3.2.0-SNAPSHOT.jar.lastUpdated
  

 /home/cmccabe/.m2/repository/org/apache/htrace/htrace-core/3.2.0-SNAPSHOT/htrace-core-3.2.0-SNAPSHOT.pom.lastUpdated
 ...

 The version you built should be 3.2.0-SNAPSHOT.

 Next, we check out Hadoop:

   cmccabe@keter:~/ git clone
 https://git-wip-us.apache.org/repos/asf/hadoop.git
   cmccabe@keter:~/ cd hadoop
   cmccabe@keter:~/ git checkout branch-2

 So we are basically building a pre-release version of Hadoop 2.7, currently
 known as branch-2.  We will need to modify Hadoop to use 3.2.0-SNAPSHOT
 rather
 than the stable 3.1.0 release which it would ordinarily use in branch-2.  I
 applied this diff to hadoop-project/pom.xml

   diff --git a/hadoop-project/pom.xml b/hadoop-project/pom.xml
   index 569b292..5b7e466 100644
   --- a/hadoop-project/pom.xml
   +++ b/hadoop-project/pom.xml
   @@ -785,7 +785,7 @@
  dependency
groupIdorg.apache.htrace/groupId
artifactIdhtrace-core/artifactId
   -version3.1.0-incubating/version
   +version3.2.0-incubating-SNAPSHOT/version
  /dependency
  dependency
groupIdorg.jdom/groupId

 Next, I built Hadoop:

 cmccabe@keter:~/ mvn package -Pdist -DskipTests -Dmaven.javadoc.skip=true

 You should get a package with Hadoop jars named like so:

 ...

 ./hadoop-hdfs-project/hadoop-hdfs/target/hadoop-hdfs-2.7.0-SNAPSHOT/share/hadoop/hdfs/lib/commons-codec-1.4.jar

 ./hadoop-hdfs-project/hadoop-hdfs/target/hadoop-hdfs-2.7.0-SNAPSHOT/share/hadoop/hdfs/lib/commons-daemon-1.0.13.jar
 ...

 This package should also contain an htrace-3.2.0-SNAPSHOT jar.

 OK, so how can we start seeing some trace spans?  The easiest way is to
 configure LocalFileSpanReceiver.

 Add this to your hdfs-site.xml:

   property
 namehadoop.htrace.spanreceiver.classes/name
 valueorg.apache.htrace.impl.LocalFileSpanReceiver/value
   /property
   property
 namehadoop.htrace.sampler/name
 valueAlwaysSampler/value
   /property

 When you run the Hadoop daemons, you should see them writing to files named
 /tmp/${PROCESS_ID} (for each different process).  If this doesn't happen,
 try
 cranking up your log4j level to TRACE to see why the SpanReceiver could not
 be
 created.

 You should see something like this in the log4j logs:

   13:28:33,885 TRACE SpanReceiverBuilder:94 - Created new span receiver of
 type org.apache.htrace.impl.LocalFileSpanReceiver
  at
 

[REPORT] HTrace March 2015

[Lewis John Mcgibbney]

Hi Folks,
Please see below, this has been added to the wiki

HTraceHTrace is a tracing framework intended for use with distributed
systemswritten in java.HTrace has been incubating since 2014-11.Three
most important issues to address in the move towards graduation:  1.
Continue to grow the HTrace community  2. Continue to develop and
release stable HTrace incubating artifacts  3. Continue to explore the
integration of the HTrace framework into other Apache productsAny
issues that the Incubator PMC (IPMC) or ASF Board wish/need to beaware
of?NoHow has the community developed since the last report?There has
been a bunch of mailing list activity relating directlyto issue 3
above e.g. better integration of HTrace into HBase/HDFS.HTrace is
being represented at ApacheCon 2015 NA in April with a
presentationIntroducing Apache HTrace: An End-to-End Tracing
Framework for Distributed Systems - Colin McCabe, Cloudera -
http://sched.co/2P8QHow has the project developed since the last
report?The codebase has seen about 30 odd commits since last
reporting.Jira continues to see activity which is encouraging as
HTrace communityprogresses towards next incubating release.Date of
last release:   2015-20-01 htrace-3.1.0-incubatingWhen were the last
committers or PMC members elected?Abraham Elmahrek was elected to
become an HTrace committer onWed, 11 Feb, 2-15.Signed-off-by:   [
](htrace) Jake Farrell  [ ](htrace) Todd Lipcon  [X](htrace) Lewis
John Mcgibbney  [ ](htrace) Andrew Purtell  [ ](htrace) Billie Rinaldi
 [ ](htrace) Michael StackShepherd/Mentor notes:


Ta
Lewis


-- 
*Lewis*

Re: February 2015 Report

[Lewis John Mcgibbney]

Hi Colin,


On Fri, Jan 30, 2015 at 11:48 AM, Colin McCabe cmcc...@alumni.cmu.edu
wrote:

 Thanks for putting this together, Lewis!  It looks good.

 The only thing I would change is that while the current text says the
 community appears not to have developed much with regards to
 attracting new community members, we do have a new community member,
 Abraham Elmarek, who has been doing a lot of good work on the web UI.
 So I think that should count, although Abe is not yet a committer.

 Wiki page shows up as immutable for me so please add that in there if
 it makes sense to you.


Sorry about that. I had not picked this up so apologies Abraham :|
It is now edited to accommodate the contributions.
Thanks folks.
lewis

-- 
*Lewis*

Re: February 2015 Report

[Lewis John Mcgibbney]

Hi Folks,
Please see our entry in the Incubator reporting page.
I flushed out some of my observations and options. Please change at will if
you do not agree.
Thanks
Lewis


On Thu, Jan 29, 2015 at 5:01 PM, Marvin Humphrey mar...@apache.org wrote:

 Greetings, {podling} developers,

 The marvin automated report reminder script didn't fire for whatever
 reason this week, so I'm sending out a bulk reminder manually for the 19
 podlings who are expected to submit a February 2015 report.  Boilerplate
 repinder text below.

 Best,

 Marvin Humphrey

 ---

 Dear podling,

 This email was sent by an automated system on behalf of the Apache
 Incubator PMC. It is an initial reminder to give you plenty of time to
 prepare your quarterly board report.

 The board meeting is scheduled for Wed, 18 February 2015, 10:30 am PST.
 The report for your podling will form a part of the Incubator PMC
 report. The Incubator PMC requires your report to be submitted 2 weeks
 before the board meeting, to allow sufficient time for review and
 submission (Wed, February 4th).

 Please submit your report with sufficient time to allow the incubator
 PMC, and subsequently board members to review and digest. Again, the
 very latest you should submit your report is 2 weeks prior to the board
 meeting.

 Thanks,

 The Apache Incubator PMC

 Submitting your Report

 --

 Your report should contain the following:

 *   Your project name
 *   A brief description of your project, which assumes no knowledge of
 the project or necessarily of its field
 *   A list of the three most important issues to address in the move
 towards graduation.
 *   Any issues that the Incubator PMC or ASF Board might wish/need to be
 aware of
 *   How has the community developed since the last report
 *   How has the project developed since the last report.

 This should be appended to the Incubator Wiki page at:

 http://wiki.apache.org/incubator/February2015

 Note: This is manually populated. You may need to wait a little before
 this page is created from a template.

 Mentors
 ---

 Mentors should review reports for their project(s) and sign them off on
 the Incubator wiki page. Signing off reports shows that you are
 following the project - projects that are not signed may raise alarms
 for the Incubator PMC.

 Incubator PMC




-- 
*Lewis*

Re: Board Report?

[Lewis John Mcgibbney]

I agree with your last sentence entirely and thank you for the context.
Ta
Lewis

On Tue, Jan 6, 2015 at 1:01 PM, John D. Ament john.d.am...@gmail.com
wrote:

 Lewis,

 I'll explain, for yours and  Andrew's sake.

 There was an issue last month I think where a mentor couldn't update the
 wiki for some reason (technical in nature).  He requested the PPMC to sign
 his name on the report.  The commit looked like it was just someone signing
 off for someone else (no context). This set off some alarms.

 It was requested that if you do sign off, include a link to the mail
 archive with the request.

 From my point of view, no such technical issue was in this case.
 Considering the major mentor issues being raised on the general list, I'd
 prefer to not see this.  Mentors signing off on the report are very
 important.

 John

 On Tue Jan 06 2015 at 3:37:05 PM Lewis John Mcgibbney 
 lewis.mcgibb...@gmail.com wrote:

  John,
  The report looks good to me and reflects what I am seeing taking place
  within the community.
  I think it is well understood that this is a case of people trying to
 help
  out where they can based on the time they have. It was appreciated from
 my
  point of view.
  As always, I've checked the full report as it now appears on the wiki.
  What the issue here is I am not sure. Michael is a mentor of the project
  anyways is he not?
  Thanks
  Lewis
 
  On Tue, Jan 6, 2015 at 7:33 AM, John D. Ament johndam...@apache.org
  wrote:
 
   Mentors,
  
   I'm very concerned over what I see here.
  
   - You should be signing off on the report on the wiki, not asking the
  PPMC
   to add your sign off.
   - If you have issues accessing the wiki, please request access on the
   general@ mailing list.
  
   PPMC members,
  
   I'm concerned over the statement With oks from three mentors and Nick
   The incubator expects that all mentors sign off on the report, but you
   shouldn't wait for the mentors OK to post it to the wiki.
   Please also hold your mentors accountable to sign off on the report.
  
   I plan to remove the mentor checks from the incubator report shortly.
  
   John
  
   On Tue, Jan 6, 2015 at 1:52 AM, Lewis John Mcgibbney 
   lewis.mcgibb...@gmail.com wrote:
  
Good job
   
On Monday, January 5, 2015, Stack st...@duboce.net wrote:
   
 Thank you Lewis.

 With oks from three mentors and Nick, let me post this to the wiki.
  If
any
 more comments, no problem, I'll edit them in.

 Thanks,
 St.Ack

 On Mon, Jan 5, 2015 at 10:22 PM, Lewis John Mcgibbney 
 lewis.mcgibb...@gmail.com javascript:; wrote:

  Hi St.Ack,
  Report looks good to me. Please duly assign my X
  I've been silently monitoring HTrace and very pleased to see RC's
   going
 up.
  I'll be VOTE'ing on next ones in an attempt to drive first
  Incubating
  release.
  Great job folks.
  Thanks
  Lewis
 
  On Mon, Jan 5, 2015 at 9:03 PM, Stack st...@duboce.net
javascript:;
 wrote:
 
   Thank you for the ping, Mr Project Shepherd.
  
   What would folks add to the below? (Below is the template taken
   from
   http://wiki.apache.org/incubator/January2015 filled in). If
 you
   are
a
   mentor and below is good by you, ack and I'll add in an 'x' for
  you
in
  the
   mentors box below.
  
   St.Ack
  
  
   
   HTrace
  
   HTrace is a tracing framework intended for use with distributed
systems
   written in java.
  
   HTrace has been incubating since 2014-11.
  
   Three most important issues to address in the move towards
graduation:
  
 1. Make our first release from incubator
 2. Move dependent projects over to the incubator version
 3. Continue to grow user and contributor base; i.e. grow the
 community.
  
   Any issues that the Incubator PMC (IPMC) or ASF Board wish/need
  to
   be
   aware of?
  
   None
  
   How has the community developed since the last report?
  
   * 141 messages on dev@htrace
   * 42 issues resolved and 11 open
  
   How has the project developed since the last report?
  
   * This is our first report.
   * We are fully moved over to Apache Infrastructure now (thanks
 in
   particular to Jake Farrell for help here).
   * We have our first htrace website published.
   * Development of an easy to deploy htraced trace sink and
visualization
  is
   moving along nicely.
   * An htrace receiver for Apache Flume was contributed.
   * We have put up 5 release candidates for our 1st podling
 release
with
 a
   6th on its way.
  
   Date of last release:
  
 None as yet.
  
   When were the last committers or PMC members elected?
  
None since initial setup.
  
   Signed-off

Re: Board Report?

[Lewis John Mcgibbney]

Good job

On Monday, January 5, 2015, Stack st...@duboce.net wrote:

 Thank you Lewis.

 With oks from three mentors and Nick, let me post this to the wiki. If any
 more comments, no problem, I'll edit them in.

 Thanks,
 St.Ack

 On Mon, Jan 5, 2015 at 10:22 PM, Lewis John Mcgibbney 
 lewis.mcgibb...@gmail.com javascript:; wrote:

  Hi St.Ack,
  Report looks good to me. Please duly assign my X
  I've been silently monitoring HTrace and very pleased to see RC's going
 up.
  I'll be VOTE'ing on next ones in an attempt to drive first Incubating
  release.
  Great job folks.
  Thanks
  Lewis
 
  On Mon, Jan 5, 2015 at 9:03 PM, Stack st...@duboce.net javascript:;
 wrote:
 
   Thank you for the ping, Mr Project Shepherd.
  
   What would folks add to the below? (Below is the template taken from
   http://wiki.apache.org/incubator/January2015 filled in). If you are a
   mentor and below is good by you, ack and I'll add in an 'x' for you in
  the
   mentors box below.
  
   St.Ack
  
  
   
   HTrace
  
   HTrace is a tracing framework intended for use with distributed systems
   written in java.
  
   HTrace has been incubating since 2014-11.
  
   Three most important issues to address in the move towards graduation:
  
 1. Make our first release from incubator
 2. Move dependent projects over to the incubator version
 3. Continue to grow user and contributor base; i.e. grow the
 community.
  
   Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
   aware of?
  
   None
  
   How has the community developed since the last report?
  
   * 141 messages on dev@htrace
   * 42 issues resolved and 11 open
  
   How has the project developed since the last report?
  
   * This is our first report.
   * We are fully moved over to Apache Infrastructure now (thanks in
   particular to Jake Farrell for help here).
   * We have our first htrace website published.
   * Development of an easy to deploy htraced trace sink and visualization
  is
   moving along nicely.
   * An htrace receiver for Apache Flume was contributed.
   * We have put up 5 release candidates for our 1st podling release with
 a
   6th on its way.
  
   Date of last release:
  
 None as yet.
  
   When were the last committers or PMC members elected?
  
None since initial setup.
  
   Signed-off-by:
  
 [ ](htrace) Jake Farrell
 [ ](htrace) Todd Lipcon
 [ ](htrace) Lewis John Mcgibbney
 [ ](htrace) Andrew Purtell
 [ ](htrace) Billie Rinaldi
 [ ](htrace) Michael Stack
  
   Shepherd/Mentor notes:
  
  
   On Mon, Jan 5, 2015 at 6:13 PM, John D. Ament johndam...@apache.org
 javascript:;
   wrote:
  
Hi Podling?
   
How are you today?
   
Just wondering, how are you doing with a board report for this month?
   
Look forward to seeing it.  You look like you're off to a good start.
   
John
   
  
 
 
 
  --
  *Lewis*
 



-- 
*Lewis*

Re: What version should be the first apache htrace be? 4.0.0 or 1.0.0?

[Lewis John Mcgibbney]

Hi Folks,
+0 on keeping versioning going 3.1.X or 3.2
I'll get more involved as the weeks go on.
Have a great weekend folks
Lewis

On Fri, Dec 5, 2014 at 9:36 PM, Nick Dimiduk ndimi...@gmail.com wrote:

 I think going backwards to 1.0 would be confusing for any existing users.
 Maybe make the -incubating releases pickup 3.1.x with the intention of the
 first graduated release being 4.0.0. Could be seen as artificially
 inflating the version numbers, but I don't think that matters too much. I
 assume (prefer) we'll follow the guidelines of semantic versioning.

 -n

 On Friday, December 5, 2014, Colin McCabe cmcc...@alumni.cmu.edu wrote:

  I looked at
 
 http://incubator.apache.org/guides/releasemanagement.html#best-practice-versioning
  and it doesn't say whether we need to start at 1.  Hmm.
 
  I think either way could work.  There is stuff from org.htrace up on
  Maven central, but since we're moving to org.apache.htrace, we won't
  conflict if we choose to go back to 1.0.0.  I don't really have any
  preference between 1.0.0 or 4.0.0.
 
  best,
  Colin
 
  On Fri, Dec 5, 2014 at 7:47 PM, Stack st...@duboce.net javascript:;
  wrote:
   org.htrace was at 3.0.4
  
   The next release could be 4.0.0.
  
   Or we could roll back and make it 1.0.0?
  
   Any opinions out there?
  
   Thanks,
   St.Ack
 




-- 
*Lewis*