Re: [VOTE] Accept HTrace into the Apache Incubator
On Wed, Nov 5, 2014 at 11:36 AM, Roman Shaposhnik r...@apache.org wrote: On Wed, Nov 5, 2014 at 11:16 AM, Roman Shaposhnik r...@apache.org wrote: Following the discussion earlier in the thread: http://s.apache.org/Dk7 I would like to call a VOTE for accepting HTrace as a new incubator project. The proposal is available at: https://wiki.apache.org/incubator/HTraceProposal (a full version of the proposal is attached) Vote is open until at least Sunday, 9th November 2014, 23:59:00 UTC [ ] +1 accept Lens in the Incubator [ ] ±0 [ ] -1 because... +1 (binding) Thanks, Roman. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[RESULT] [VOTE] Accept HTrace into the Apache Incubator
The vote has passed with 14 binding +1 votes, 13 non-binding +1, and no +/-0 or -1 votes. Binding (+1) Stack Jake Farrell Chris Mattmann Ted Dunning Suresh Srinivas Billie Rinaldi Tim Williams Jan i Arvind Prabhakar Andrew Purtell Arun Murthy Steve Loughran John D. Ament Roman Shaposhnik Non-binding (+1) Todd Lipcon Seetharam Venkatesh Balaji Ganesan Lieven Govaerts Naresh Agarwal Shwetha GS Colin McCabe Jonathan Leavitt Masatake Iwasaki Elliott Clark Dilli Arumugam Aditya Kishore Nick Dimiduk Thanks to everyone who voted and commented on the proposal! Mentors, start your engines -- lets make HTrace transition into ASF Incubator as smooth as possible! Thanks, Roman. On Wed, Nov 5, 2014 at 11:36 AM, Roman Shaposhnik r...@apache.org wrote: On Wed, Nov 5, 2014 at 11:16 AM, Roman Shaposhnik r...@apache.org wrote: Following the discussion earlier in the thread: http://s.apache.org/Dk7 I would like to call a VOTE for accepting HTrace as a new incubator project. The proposal is available at: https://wiki.apache.org/incubator/HTraceProposal (a full version of the proposal is attached) Vote is open until at least Sunday, 9th November 2014, 23:59:00 UTC [ ] +1 accept Lens in the Incubator [ ] ±0 [ ] -1 because... Thanks, Roman. == Abstract == HTrace is a tracing framework intended for use with distributed systems written in java. == Proposal == HTrace is an aid for understanding system behavior and for reasoning about performance issues in distributed systems. HTrace is primarily a low impedance library that a java distributed system can incorporate to generate ‘breadcrumbs’ or ‘traces’ along the path of execution, even as it crosses processes and machines. HTrace also includes various tools and glue for collecting, processing and ‘visualizing’ captured execution traces for analysis ex post facto of where time was spent and what resources were consumed. == Background == Distributed systems are made up of multiple software components running on multiple computers connected by networks. Debugging or profiling operations run over non-trivial distributed systems -- figuring execution paths and what services, machines, and libraries participated in the processing of a request -- can be involved. == Rationale == Rather than have each distributed system build its own custom ‘tracing’ libraries, ideally all would use a single project that provides necessary primitives and saves each project building its own visualizations and processing tools anew. Google described “...[a] large-scale distributed systems tracing infrastructure” in Dapper, a Large-Scale Distributed Systems Tracing Infrastructure. The paper tells a compelling story of what is possible when disparate systems standardize on a single tracing library and cooperate, ‘passing the baton’, filling out trace context as executions cross systems. HTrace aims to provide a rough equivalent in open source of the described core Dapper tools and library. As it is adopted by more projects, there will be a ‘network effect’ as HTrace will provide a more comprehensive view of activity on the cluster. For example, as HDFS gets HTrace support, we can connect this with the HTrace support in HBase to follow HBase requests as they enter HDFS. Given the success of HTrace depends on its being integrated by many projects, HTrace should be perceived as unhampered, free of any commercial, political, or legal ‘taint’. Being an Apache project would help in this regard. == Initial Goals == HTrace is a small project of narrow scope but with a grand vision: * Move the HTrace source and repository to Apache, a vendor-neutral location. Currently HTrace resides at a Cloudera-hosted repository. * Add past contributors as committers and institute Apache governance. * Evangelize and encourage HTrace diffusion. Initially we will continue a focus on the Hadoop space since that is where most of the initial contributors work and it is where HTrace has been initially deployed. * Building out the standalone visualization tool that ships with HTrace. * Build more community and add more committers == Current Status == Currently HTrace has a viable Java trace library that can be interpolated to create ‘traces’. The work that needs to be done on this library is mostly bug fixes, ease-of-use improvements, and performance tweaks. In the future, we may add libraries for other languages besides Java. HTrace has means of dumping traces to the filesystem, Twitters’ Zipkin (a tracing sink and visualization system developed by Twitter https://github.com/twitter/zipkin), or Apache HBase. Executions can be viewed either in Zipkin or in pygraph (https://code.google.com/p/python-graph/). Since the initial sprint in the summer of 2012 which saw HTrace patches proposed for Apache HDFS and committed to Apache HBase, development has
Re: [VOTE] Accept HTrace into the Apache Incubator
+1 (binding) Arun On Nov 6, 2014, at 1:00 PM, Andrew Purtell apurt...@apache.org wrote: +1 (binding) On Wed, Nov 5, 2014 at 11:16 AM, Roman Shaposhnik r...@apache.org wrote: Following the discussion earlier in the thread: http://s.apache.org/Dk7 I would like to call a VOTE for accepting HTrace as a new incubator project. The proposal is available at: https://wiki.apache.org/incubator/HTraceProposal Vote is open until at least Sunday, 9th November 2014, 23:59:00 UTC [ ] +1 accept Lens in the Incubator [ ] ±0 [ ] -1 because... - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Best regards, - Andy Problems worthy of attack prove their worth by hitting back. - Piet Hein (via Tom White) -- CONFIDENTIALITY NOTICE NOTICE: This message is intended for the use of the individual or entity to which it is addressed and may contain information that is confidential, privileged and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any printing, copying, dissemination, distribution, disclosure or forwarding of this communication is strictly prohibited. If you have received this communication in error, please contact the sender immediately and delete it from your system. Thank You. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept HTrace into the Apache Incubator
[ ] +1 accept Lens in the Incubator [ ] ±0 [ ] -1 because... think you meant HTrace and not lens. Accordingly +1, binding -- CONFIDENTIALITY NOTICE NOTICE: This message is intended for the use of the individual or entity to which it is addressed and may contain information that is confidential, privileged and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any printing, copying, dissemination, distribution, disclosure or forwarding of this communication is strictly prohibited. If you have received this communication in error, please contact the sender immediately and delete it from your system. Thank You.
Re: [VOTE] Accept HTrace into the Apache Incubator
+1 (binding) On Wed, Nov 5, 2014 at 2:16 PM, Roman Shaposhnik r...@apache.org wrote: Following the discussion earlier in the thread: http://s.apache.org/Dk7 I would like to call a VOTE for accepting HTrace as a new incubator project. The proposal is available at: https://wiki.apache.org/incubator/HTraceProposal Vote is open until at least Sunday, 9th November 2014, 23:59:00 UTC [ ] +1 accept Lens in the Incubator [ ] ±0 [ ] -1 because... - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept HTrace into the Apache Incubator
+1 On Wed, Nov 5, 2014 at 11:16 AM, Roman Shaposhnik r...@apache.org wrote: Following the discussion earlier in the thread: http://s.apache.org/Dk7 I would like to call a VOTE for accepting HTrace as a new incubator project. The proposal is available at: https://wiki.apache.org/incubator/HTraceProposal Vote is open until at least Sunday, 9th November 2014, 23:59:00 UTC [ ] +1 accept Lens in the Incubator [ ] ±0 [ ] -1 because... - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept HTrace into the Apache Incubator
+1 (non-binding) Thanks Naresh On Thu, Nov 6, 2014 at 12:26 PM, Seetharam Venkatesh venkat...@innerzeal.com wrote: +1 (non-binding) On Wed, Nov 5, 2014 at 1:34 PM, Billie Rinaldi bil...@apache.org wrote: +1 On Wed, Nov 5, 2014 at 11:37 AM, Roman Shaposhnik r...@apache.org wrote: Following the discussion earlier in the thread: http://s.apache.org/Dk7 I would like to call a VOTE for accepting HTrace as a new incubator project. The proposal is available at: https://wiki.apache.org/incubator/HTraceProposal Vote is open until at least Sunday, 9th November 2014, 23:59:00 UTC [ ] +1 accept Lens in the Incubator [ ] ±0 [ ] -1 because... -- Regards, Venkatesh “Perfection (in design) is achieved not when there is nothing more to add, but rather when there is nothing more to take away.” - Antoine de Saint-Exupéry -- _ The information contained in this communication is intended solely for the use of the individual or entity to whom it is addressed and others authorized to receive it. It may contain confidential or legally privileged information. If you are not the intended recipient you are hereby notified that any disclosure, copying, distribution or taking any action in reliance on the contents of this information is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by responding to this email and then delete it from your system. The firm is neither liable for the proper and complete transmission of the information contained in this communication nor for any delay in its receipt.
Re: [VOTE] Accept HTrace into the Apache Incubator
+1 (non-binding) On Thu, Nov 6, 2014 at 1:36 PM, Naresh Agarwal naresh.agar...@inmobi.com wrote: +1 (non-binding) Thanks Naresh On Thu, Nov 6, 2014 at 12:26 PM, Seetharam Venkatesh venkat...@innerzeal.com wrote: +1 (non-binding) On Wed, Nov 5, 2014 at 1:34 PM, Billie Rinaldi bil...@apache.org wrote: +1 On Wed, Nov 5, 2014 at 11:37 AM, Roman Shaposhnik r...@apache.org wrote: Following the discussion earlier in the thread: http://s.apache.org/Dk7 I would like to call a VOTE for accepting HTrace as a new incubator project. The proposal is available at: https://wiki.apache.org/incubator/HTraceProposal Vote is open until at least Sunday, 9th November 2014, 23:59:00 UTC [ ] +1 accept Lens in the Incubator [ ] ±0 [ ] -1 because... -- Regards, Venkatesh “Perfection (in design) is achieved not when there is nothing more to add, but rather when there is nothing more to take away.” - Antoine de Saint-Exupéry -- _ The information contained in this communication is intended solely for the use of the individual or entity to whom it is addressed and others authorized to receive it. It may contain confidential or legally privileged information. If you are not the intended recipient you are hereby notified that any disclosure, copying, distribution or taking any action in reliance on the contents of this information is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by responding to this email and then delete it from your system. The firm is neither liable for the proper and complete transmission of the information contained in this communication nor for any delay in its receipt. -- _ The information contained in this communication is intended solely for the use of the individual or entity to whom it is addressed and others authorized to receive it. It may contain confidential or legally privileged information. If you are not the intended recipient you are hereby notified that any disclosure, copying, distribution or taking any action in reliance on the contents of this information is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by responding to this email and then delete it from your system. The firm is neither liable for the proper and complete transmission of the information contained in this communication nor for any delay in its receipt.
Re: [VOTE] Accept HTrace into the Apache Incubator
+1 --tim On Wed, Nov 5, 2014 at 2:36 PM, Roman Shaposhnik r...@apache.org wrote: On Wed, Nov 5, 2014 at 11:16 AM, Roman Shaposhnik r...@apache.org wrote: Following the discussion earlier in the thread: http://s.apache.org/Dk7 I would like to call a VOTE for accepting HTrace as a new incubator project. The proposal is available at: https://wiki.apache.org/incubator/HTraceProposal (a full version of the proposal is attached) Vote is open until at least Sunday, 9th November 2014, 23:59:00 UTC [ ] +1 accept Lens in the Incubator [ ] ±0 [ ] -1 because... Thanks, Roman. == Abstract == HTrace is a tracing framework intended for use with distributed systems written in java. == Proposal == HTrace is an aid for understanding system behavior and for reasoning about performance issues in distributed systems. HTrace is primarily a low impedance library that a java distributed system can incorporate to generate ‘breadcrumbs’ or ‘traces’ along the path of execution, even as it crosses processes and machines. HTrace also includes various tools and glue for collecting, processing and ‘visualizing’ captured execution traces for analysis ex post facto of where time was spent and what resources were consumed. == Background == Distributed systems are made up of multiple software components running on multiple computers connected by networks. Debugging or profiling operations run over non-trivial distributed systems -- figuring execution paths and what services, machines, and libraries participated in the processing of a request -- can be involved. == Rationale == Rather than have each distributed system build its own custom ‘tracing’ libraries, ideally all would use a single project that provides necessary primitives and saves each project building its own visualizations and processing tools anew. Google described “...[a] large-scale distributed systems tracing infrastructure” in Dapper, a Large-Scale Distributed Systems Tracing Infrastructure. The paper tells a compelling story of what is possible when disparate systems standardize on a single tracing library and cooperate, ‘passing the baton’, filling out trace context as executions cross systems. HTrace aims to provide a rough equivalent in open source of the described core Dapper tools and library. As it is adopted by more projects, there will be a ‘network effect’ as HTrace will provide a more comprehensive view of activity on the cluster. For example, as HDFS gets HTrace support, we can connect this with the HTrace support in HBase to follow HBase requests as they enter HDFS. Given the success of HTrace depends on its being integrated by many projects, HTrace should be perceived as unhampered, free of any commercial, political, or legal ‘taint’. Being an Apache project would help in this regard. == Initial Goals == HTrace is a small project of narrow scope but with a grand vision: * Move the HTrace source and repository to Apache, a vendor-neutral location. Currently HTrace resides at a Cloudera-hosted repository. * Add past contributors as committers and institute Apache governance. * Evangelize and encourage HTrace diffusion. Initially we will continue a focus on the Hadoop space since that is where most of the initial contributors work and it is where HTrace has been initially deployed. * Building out the standalone visualization tool that ships with HTrace. * Build more community and add more committers == Current Status == Currently HTrace has a viable Java trace library that can be interpolated to create ‘traces’. The work that needs to be done on this library is mostly bug fixes, ease-of-use improvements, and performance tweaks. In the future, we may add libraries for other languages besides Java. HTrace has means of dumping traces to the filesystem, Twitters’ Zipkin (a tracing sink and visualization system developed by Twitter https://github.com/twitter/zipkin), or Apache HBase. Executions can be viewed either in Zipkin or in pygraph (https://code.google.com/p/python-graph/). Since the initial sprint in the summer of 2012 which saw HTrace patches proposed for Apache HDFS and committed to Apache HBase, development has been sporadic; mostly a single developer or two adding a feature or bug fixing. HTrace is currently undergoing a new “spurt” of development with the effort to get HTrace added to Apache HDFS revived and a new standalone viewing facility being added in to HTrace itself. HTrace has been integrated by Apache Phoenix. === Meritocracy === HTrace, up to this, has been run by Apache committers and PMC members. We want to build out a diverse developer and user community and run the HTrace project in the Apache way. Users and new contributors will be treated with respect and welcomed; they will earn merit in the project by tendering quality patches and support that move the project forward. Those with a proven
Re: [VOTE] Accept HTrace into the Apache Incubator
+1 (non-binding) Colin On Wed, Nov 5, 2014 at 11:36 AM, Roman Shaposhnik r...@apache.org wrote: On Wed, Nov 5, 2014 at 11:16 AM, Roman Shaposhnik r...@apache.org wrote: Following the discussion earlier in the thread: http://s.apache.org/Dk7 I would like to call a VOTE for accepting HTrace as a new incubator project. The proposal is available at: https://wiki.apache.org/incubator/HTraceProposal (a full version of the proposal is attached) Vote is open until at least Sunday, 9th November 2014, 23:59:00 UTC [ ] +1 accept Lens in the Incubator [ ] ±0 [ ] -1 because... Thanks, Roman. == Abstract == HTrace is a tracing framework intended for use with distributed systems written in java. == Proposal == HTrace is an aid for understanding system behavior and for reasoning about performance issues in distributed systems. HTrace is primarily a low impedance library that a java distributed system can incorporate to generate ‘breadcrumbs’ or ‘traces’ along the path of execution, even as it crosses processes and machines. HTrace also includes various tools and glue for collecting, processing and ‘visualizing’ captured execution traces for analysis ex post facto of where time was spent and what resources were consumed. == Background == Distributed systems are made up of multiple software components running on multiple computers connected by networks. Debugging or profiling operations run over non-trivial distributed systems -- figuring execution paths and what services, machines, and libraries participated in the processing of a request -- can be involved. == Rationale == Rather than have each distributed system build its own custom ‘tracing’ libraries, ideally all would use a single project that provides necessary primitives and saves each project building its own visualizations and processing tools anew. Google described “...[a] large-scale distributed systems tracing infrastructure” in Dapper, a Large-Scale Distributed Systems Tracing Infrastructure. The paper tells a compelling story of what is possible when disparate systems standardize on a single tracing library and cooperate, ‘passing the baton’, filling out trace context as executions cross systems. HTrace aims to provide a rough equivalent in open source of the described core Dapper tools and library. As it is adopted by more projects, there will be a ‘network effect’ as HTrace will provide a more comprehensive view of activity on the cluster. For example, as HDFS gets HTrace support, we can connect this with the HTrace support in HBase to follow HBase requests as they enter HDFS. Given the success of HTrace depends on its being integrated by many projects, HTrace should be perceived as unhampered, free of any commercial, political, or legal ‘taint’. Being an Apache project would help in this regard. == Initial Goals == HTrace is a small project of narrow scope but with a grand vision: * Move the HTrace source and repository to Apache, a vendor-neutral location. Currently HTrace resides at a Cloudera-hosted repository. * Add past contributors as committers and institute Apache governance. * Evangelize and encourage HTrace diffusion. Initially we will continue a focus on the Hadoop space since that is where most of the initial contributors work and it is where HTrace has been initially deployed. * Building out the standalone visualization tool that ships with HTrace. * Build more community and add more committers == Current Status == Currently HTrace has a viable Java trace library that can be interpolated to create ‘traces’. The work that needs to be done on this library is mostly bug fixes, ease-of-use improvements, and performance tweaks. In the future, we may add libraries for other languages besides Java. HTrace has means of dumping traces to the filesystem, Twitters’ Zipkin (a tracing sink and visualization system developed by Twitter https://github.com/twitter/zipkin), or Apache HBase. Executions can be viewed either in Zipkin or in pygraph (https://code.google.com/p/python-graph/). Since the initial sprint in the summer of 2012 which saw HTrace patches proposed for Apache HDFS and committed to Apache HBase, development has been sporadic; mostly a single developer or two adding a feature or bug fixing. HTrace is currently undergoing a new “spurt” of development with the effort to get HTrace added to Apache HDFS revived and a new standalone viewing facility being added in to HTrace itself. HTrace has been integrated by Apache Phoenix. === Meritocracy === HTrace, up to this, has been run by Apache committers and PMC members. We want to build out a diverse developer and user community and run the HTrace project in the Apache way. Users and new contributors will be treated with respect and welcomed; they will earn merit in the project by tendering quality patches and support that move the project forward.
Re: [VOTE] Accept HTrace into the Apache Incubator
+1 binding. rgds jan i On 6 November 2014 18:49, Colin McCabe cmcc...@alumni.cmu.edu wrote: +1 (non-binding) Colin On Wed, Nov 5, 2014 at 11:36 AM, Roman Shaposhnik r...@apache.org wrote: On Wed, Nov 5, 2014 at 11:16 AM, Roman Shaposhnik r...@apache.org wrote: Following the discussion earlier in the thread: http://s.apache.org/Dk7 I would like to call a VOTE for accepting HTrace as a new incubator project. The proposal is available at: https://wiki.apache.org/incubator/HTraceProposal (a full version of the proposal is attached) Vote is open until at least Sunday, 9th November 2014, 23:59:00 UTC [ ] +1 accept Lens in the Incubator [ ] ±0 [ ] -1 because... Thanks, Roman. == Abstract == HTrace is a tracing framework intended for use with distributed systems written in java. == Proposal == HTrace is an aid for understanding system behavior and for reasoning about performance issues in distributed systems. HTrace is primarily a low impedance library that a java distributed system can incorporate to generate ‘breadcrumbs’ or ‘traces’ along the path of execution, even as it crosses processes and machines. HTrace also includes various tools and glue for collecting, processing and ‘visualizing’ captured execution traces for analysis ex post facto of where time was spent and what resources were consumed. == Background == Distributed systems are made up of multiple software components running on multiple computers connected by networks. Debugging or profiling operations run over non-trivial distributed systems -- figuring execution paths and what services, machines, and libraries participated in the processing of a request -- can be involved. == Rationale == Rather than have each distributed system build its own custom ‘tracing’ libraries, ideally all would use a single project that provides necessary primitives and saves each project building its own visualizations and processing tools anew. Google described “...[a] large-scale distributed systems tracing infrastructure” in Dapper, a Large-Scale Distributed Systems Tracing Infrastructure. The paper tells a compelling story of what is possible when disparate systems standardize on a single tracing library and cooperate, ‘passing the baton’, filling out trace context as executions cross systems. HTrace aims to provide a rough equivalent in open source of the described core Dapper tools and library. As it is adopted by more projects, there will be a ‘network effect’ as HTrace will provide a more comprehensive view of activity on the cluster. For example, as HDFS gets HTrace support, we can connect this with the HTrace support in HBase to follow HBase requests as they enter HDFS. Given the success of HTrace depends on its being integrated by many projects, HTrace should be perceived as unhampered, free of any commercial, political, or legal ‘taint’. Being an Apache project would help in this regard. == Initial Goals == HTrace is a small project of narrow scope but with a grand vision: * Move the HTrace source and repository to Apache, a vendor-neutral location. Currently HTrace resides at a Cloudera-hosted repository. * Add past contributors as committers and institute Apache governance. * Evangelize and encourage HTrace diffusion. Initially we will continue a focus on the Hadoop space since that is where most of the initial contributors work and it is where HTrace has been initially deployed. * Building out the standalone visualization tool that ships with HTrace. * Build more community and add more committers == Current Status == Currently HTrace has a viable Java trace library that can be interpolated to create ‘traces’. The work that needs to be done on this library is mostly bug fixes, ease-of-use improvements, and performance tweaks. In the future, we may add libraries for other languages besides Java. HTrace has means of dumping traces to the filesystem, Twitters’ Zipkin (a tracing sink and visualization system developed by Twitter https://github.com/twitter/zipkin), or Apache HBase. Executions can be viewed either in Zipkin or in pygraph (https://code.google.com/p/python-graph/). Since the initial sprint in the summer of 2012 which saw HTrace patches proposed for Apache HDFS and committed to Apache HBase, development has been sporadic; mostly a single developer or two adding a feature or bug fixing. HTrace is currently undergoing a new “spurt” of development with the effort to get HTrace added to Apache HDFS revived and a new standalone viewing facility being added in to HTrace itself. HTrace has been integrated by Apache Phoenix. === Meritocracy === HTrace, up to this, has been run by Apache committers and PMC members. We want to build out a diverse developer and user community and run the
Re: [VOTE] Accept HTrace into the Apache Incubator
+1 (non-binding) On Thu, Nov 6, 2014 at 9:56 AM, jan i j...@apache.org wrote: +1 binding. rgds jan i On 6 November 2014 18:49, Colin McCabe cmcc...@alumni.cmu.edu wrote: +1 (non-binding) Colin On Wed, Nov 5, 2014 at 11:36 AM, Roman Shaposhnik r...@apache.org wrote: On Wed, Nov 5, 2014 at 11:16 AM, Roman Shaposhnik r...@apache.org wrote: Following the discussion earlier in the thread: http://s.apache.org/Dk7 I would like to call a VOTE for accepting HTrace as a new incubator project. The proposal is available at: https://wiki.apache.org/incubator/HTraceProposal (a full version of the proposal is attached) Vote is open until at least Sunday, 9th November 2014, 23:59:00 UTC [ ] +1 accept Lens in the Incubator [ ] ±0 [ ] -1 because... Thanks, Roman. == Abstract == HTrace is a tracing framework intended for use with distributed systems written in java. == Proposal == HTrace is an aid for understanding system behavior and for reasoning about performance issues in distributed systems. HTrace is primarily a low impedance library that a java distributed system can incorporate to generate ‘breadcrumbs’ or ‘traces’ along the path of execution, even as it crosses processes and machines. HTrace also includes various tools and glue for collecting, processing and ‘visualizing’ captured execution traces for analysis ex post facto of where time was spent and what resources were consumed. == Background == Distributed systems are made up of multiple software components running on multiple computers connected by networks. Debugging or profiling operations run over non-trivial distributed systems -- figuring execution paths and what services, machines, and libraries participated in the processing of a request -- can be involved. == Rationale == Rather than have each distributed system build its own custom ‘tracing’ libraries, ideally all would use a single project that provides necessary primitives and saves each project building its own visualizations and processing tools anew. Google described “...[a] large-scale distributed systems tracing infrastructure” in Dapper, a Large-Scale Distributed Systems Tracing Infrastructure. The paper tells a compelling story of what is possible when disparate systems standardize on a single tracing library and cooperate, ‘passing the baton’, filling out trace context as executions cross systems. HTrace aims to provide a rough equivalent in open source of the described core Dapper tools and library. As it is adopted by more projects, there will be a ‘network effect’ as HTrace will provide a more comprehensive view of activity on the cluster. For example, as HDFS gets HTrace support, we can connect this with the HTrace support in HBase to follow HBase requests as they enter HDFS. Given the success of HTrace depends on its being integrated by many projects, HTrace should be perceived as unhampered, free of any commercial, political, or legal ‘taint’. Being an Apache project would help in this regard. == Initial Goals == HTrace is a small project of narrow scope but with a grand vision: * Move the HTrace source and repository to Apache, a vendor-neutral location. Currently HTrace resides at a Cloudera-hosted repository. * Add past contributors as committers and institute Apache governance. * Evangelize and encourage HTrace diffusion. Initially we will continue a focus on the Hadoop space since that is where most of the initial contributors work and it is where HTrace has been initially deployed. * Building out the standalone visualization tool that ships with HTrace. * Build more community and add more committers == Current Status == Currently HTrace has a viable Java trace library that can be interpolated to create ‘traces’. The work that needs to be done on this library is mostly bug fixes, ease-of-use improvements, and performance tweaks. In the future, we may add libraries for other languages besides Java. HTrace has means of dumping traces to the filesystem, Twitters’ Zipkin (a tracing sink and visualization system developed by Twitter https://github.com/twitter/zipkin), or Apache HBase. Executions can be viewed either in Zipkin or in pygraph (https://code.google.com/p/python-graph/). Since the initial sprint in the summer of 2012 which saw HTrace patches proposed for Apache HDFS and committed to Apache HBase, development has been sporadic; mostly a single developer or two adding a feature or bug fixing. HTrace is currently undergoing a new “spurt” of development with the effort to get HTrace added to Apache HDFS revived and a new standalone viewing facility being added in to HTrace itself.
Re: [VOTE] Accept HTrace into the Apache Incubator
+1 (non-binding) Masatake Iwasaki (11/5/14, 11:36), Roman Shaposhnik wrote: On Wed, Nov 5, 2014 at 11:16 AM, Roman Shaposhnik r...@apache.org wrote: Following the discussion earlier in the thread: http://s.apache.org/Dk7 I would like to call a VOTE for accepting HTrace as a new incubator project. The proposal is available at: https://wiki.apache.org/incubator/HTraceProposal (a full version of the proposal is attached) Vote is open until at least Sunday, 9th November 2014, 23:59:00 UTC [ ] +1 accept Lens in the Incubator [ ] ±0 [ ] -1 because... Thanks, Roman. == Abstract == HTrace is a tracing framework intended for use with distributed systems written in java. == Proposal == HTrace is an aid for understanding system behavior and for reasoning about performance issues in distributed systems. HTrace is primarily a low impedance library that a java distributed system can incorporate to generate ‘breadcrumbs’ or ‘traces’ along the path of execution, even as it crosses processes and machines. HTrace also includes various tools and glue for collecting, processing and ‘visualizing’ captured execution traces for analysis ex post facto of where time was spent and what resources were consumed. == Background == Distributed systems are made up of multiple software components running on multiple computers connected by networks. Debugging or profiling operations run over non-trivial distributed systems -- figuring execution paths and what services, machines, and libraries participated in the processing of a request -- can be involved. == Rationale == Rather than have each distributed system build its own custom ‘tracing’ libraries, ideally all would use a single project that provides necessary primitives and saves each project building its own visualizations and processing tools anew. Google described “...[a] large-scale distributed systems tracing infrastructure” in Dapper, a Large-Scale Distributed Systems Tracing Infrastructure. The paper tells a compelling story of what is possible when disparate systems standardize on a single tracing library and cooperate, ‘passing the baton’, filling out trace context as executions cross systems. HTrace aims to provide a rough equivalent in open source of the described core Dapper tools and library. As it is adopted by more projects, there will be a ‘network effect’ as HTrace will provide a more comprehensive view of activity on the cluster. For example, as HDFS gets HTrace support, we can connect this with the HTrace support in HBase to follow HBase requests as they enter HDFS. Given the success of HTrace depends on its being integrated by many projects, HTrace should be perceived as unhampered, free of any commercial, political, or legal ‘taint’. Being an Apache project would help in this regard. == Initial Goals == HTrace is a small project of narrow scope but with a grand vision: * Move the HTrace source and repository to Apache, a vendor-neutral location. Currently HTrace resides at a Cloudera-hosted repository. * Add past contributors as committers and institute Apache governance. * Evangelize and encourage HTrace diffusion. Initially we will continue a focus on the Hadoop space since that is where most of the initial contributors work and it is where HTrace has been initially deployed. * Building out the standalone visualization tool that ships with HTrace. * Build more community and add more committers == Current Status == Currently HTrace has a viable Java trace library that can be interpolated to create ‘traces’. The work that needs to be done on this library is mostly bug fixes, ease-of-use improvements, and performance tweaks. In the future, we may add libraries for other languages besides Java. HTrace has means of dumping traces to the filesystem, Twitters’ Zipkin (a tracing sink and visualization system developed by Twitter https://github.com/twitter/zipkin), or Apache HBase. Executions can be viewed either in Zipkin or in pygraph (https://code.google.com/p/python-graph/). Since the initial sprint in the summer of 2012 which saw HTrace patches proposed for Apache HDFS and committed to Apache HBase, development has been sporadic; mostly a single developer or two adding a feature or bug fixing. HTrace is currently undergoing a new “spurt” of development with the effort to get HTrace added to Apache HDFS revived and a new standalone viewing facility being added in to HTrace itself. HTrace has been integrated by Apache Phoenix. === Meritocracy === HTrace, up to this, has been run by Apache committers and PMC members. We want to build out a diverse developer and user community and run the HTrace project in the Apache way. Users and new contributors will be treated with respect and welcomed; they will earn merit in the project by tendering quality patches and support that move the project forward. Those with a proven support and quality patch track record will be encouraged to become committers. ===
Re: [VOTE] Accept HTrace into the Apache Incubator
+ 1 ( Non-Binding) On Thu, Nov 6, 2014 at 10:15 AM, Masatake Iwasaki iwasak...@oss.nttdata.co.jp wrote: +1 (non-binding) Masatake Iwasaki (11/5/14, 11:36), Roman Shaposhnik wrote: On Wed, Nov 5, 2014 at 11:16 AM, Roman Shaposhnik r...@apache.org wrote: Following the discussion earlier in the thread: http://s.apache.org/Dk7 I would like to call a VOTE for accepting HTrace as a new incubator project. The proposal is available at: https://wiki.apache.org/incubator/HTraceProposal (a full version of the proposal is attached) Vote is open until at least Sunday, 9th November 2014, 23:59:00 UTC [ ] +1 accept Lens in the Incubator [ ] ±0 [ ] -1 because... Thanks, Roman. == Abstract == HTrace is a tracing framework intended for use with distributed systems written in java. == Proposal == HTrace is an aid for understanding system behavior and for reasoning about performance issues in distributed systems. HTrace is primarily a low impedance library that a java distributed system can incorporate to generate ‘breadcrumbs’ or ‘traces’ along the path of execution, even as it crosses processes and machines. HTrace also includes various tools and glue for collecting, processing and ‘visualizing’ captured execution traces for analysis ex post facto of where time was spent and what resources were consumed. == Background == Distributed systems are made up of multiple software components running on multiple computers connected by networks. Debugging or profiling operations run over non-trivial distributed systems -- figuring execution paths and what services, machines, and libraries participated in the processing of a request -- can be involved. == Rationale == Rather than have each distributed system build its own custom ‘tracing’ libraries, ideally all would use a single project that provides necessary primitives and saves each project building its own visualizations and processing tools anew. Google described “...[a] large-scale distributed systems tracing infrastructure” in Dapper, a Large-Scale Distributed Systems Tracing Infrastructure. The paper tells a compelling story of what is possible when disparate systems standardize on a single tracing library and cooperate, ‘passing the baton’, filling out trace context as executions cross systems. HTrace aims to provide a rough equivalent in open source of the described core Dapper tools and library. As it is adopted by more projects, there will be a ‘network effect’ as HTrace will provide a more comprehensive view of activity on the cluster. For example, as HDFS gets HTrace support, we can connect this with the HTrace support in HBase to follow HBase requests as they enter HDFS. Given the success of HTrace depends on its being integrated by many projects, HTrace should be perceived as unhampered, free of any commercial, political, or legal ‘taint’. Being an Apache project would help in this regard. == Initial Goals == HTrace is a small project of narrow scope but with a grand vision: * Move the HTrace source and repository to Apache, a vendor-neutral location. Currently HTrace resides at a Cloudera-hosted repository. * Add past contributors as committers and institute Apache governance. * Evangelize and encourage HTrace diffusion. Initially we will continue a focus on the Hadoop space since that is where most of the initial contributors work and it is where HTrace has been initially deployed. * Building out the standalone visualization tool that ships with HTrace. * Build more community and add more committers == Current Status == Currently HTrace has a viable Java trace library that can be interpolated to create ‘traces’. The work that needs to be done on this library is mostly bug fixes, ease-of-use improvements, and performance tweaks. In the future, we may add libraries for other languages besides Java. HTrace has means of dumping traces to the filesystem, Twitters’ Zipkin (a tracing sink and visualization system developed by Twitter https://github.com/twitter/zipkin), or Apache HBase. Executions can be viewed either in Zipkin or in pygraph (https://code.google.com/p/python-graph/). Since the initial sprint in the summer of 2012 which saw HTrace patches proposed for Apache HDFS and committed to Apache HBase, development has been sporadic; mostly a single developer or two adding a feature or bug fixing. HTrace is currently undergoing a new “spurt” of development with the effort to get HTrace added to Apache HDFS revived and a new standalone viewing facility being added in to HTrace itself. HTrace has been integrated by Apache Phoenix. === Meritocracy === HTrace, up to this, has been run by Apache committers and PMC members. We want to build out a diverse developer and user community and run the HTrace project in the Apache way. Users and new contributors will be treated with respect and welcomed;
Re: [VOTE] Accept HTrace into the Apache Incubator
+1 (non-binding) On Thu, Nov 6, 2014 at 10:23 AM, Elliott Clark ecl...@apache.org wrote: + 1 ( Non-Binding) On Thu, Nov 6, 2014 at 10:15 AM, Masatake Iwasaki iwasak...@oss.nttdata.co.jp wrote: +1 (non-binding) Masatake Iwasaki (11/5/14, 11:36), Roman Shaposhnik wrote: On Wed, Nov 5, 2014 at 11:16 AM, Roman Shaposhnik r...@apache.org wrote: Following the discussion earlier in the thread: http://s.apache.org/Dk7 I would like to call a VOTE for accepting HTrace as a new incubator project. The proposal is available at: https://wiki.apache.org/incubator/HTraceProposal (a full version of the proposal is attached) Vote is open until at least Sunday, 9th November 2014, 23:59:00 UTC [ ] +1 accept Lens in the Incubator [ ] ±0 [ ] -1 because... Thanks, Roman. == Abstract == HTrace is a tracing framework intended for use with distributed systems written in java. == Proposal == HTrace is an aid for understanding system behavior and for reasoning about performance issues in distributed systems. HTrace is primarily a low impedance library that a java distributed system can incorporate to generate ‘breadcrumbs’ or ‘traces’ along the path of execution, even as it crosses processes and machines. HTrace also includes various tools and glue for collecting, processing and ‘visualizing’ captured execution traces for analysis ex post facto of where time was spent and what resources were consumed. == Background == Distributed systems are made up of multiple software components running on multiple computers connected by networks. Debugging or profiling operations run over non-trivial distributed systems -- figuring execution paths and what services, machines, and libraries participated in the processing of a request -- can be involved. == Rationale == Rather than have each distributed system build its own custom ‘tracing’ libraries, ideally all would use a single project that provides necessary primitives and saves each project building its own visualizations and processing tools anew. Google described “...[a] large-scale distributed systems tracing infrastructure” in Dapper, a Large-Scale Distributed Systems Tracing Infrastructure. The paper tells a compelling story of what is possible when disparate systems standardize on a single tracing library and cooperate, ‘passing the baton’, filling out trace context as executions cross systems. HTrace aims to provide a rough equivalent in open source of the described core Dapper tools and library. As it is adopted by more projects, there will be a ‘network effect’ as HTrace will provide a more comprehensive view of activity on the cluster. For example, as HDFS gets HTrace support, we can connect this with the HTrace support in HBase to follow HBase requests as they enter HDFS. Given the success of HTrace depends on its being integrated by many projects, HTrace should be perceived as unhampered, free of any commercial, political, or legal ‘taint’. Being an Apache project would help in this regard. == Initial Goals == HTrace is a small project of narrow scope but with a grand vision: * Move the HTrace source and repository to Apache, a vendor-neutral location. Currently HTrace resides at a Cloudera-hosted repository. * Add past contributors as committers and institute Apache governance. * Evangelize and encourage HTrace diffusion. Initially we will continue a focus on the Hadoop space since that is where most of the initial contributors work and it is where HTrace has been initially deployed. * Building out the standalone visualization tool that ships with HTrace. * Build more community and add more committers == Current Status == Currently HTrace has a viable Java trace library that can be interpolated to create ‘traces’. The work that needs to be done on this library is mostly bug fixes, ease-of-use improvements, and performance tweaks. In the future, we may add libraries for other languages besides Java. HTrace has means of dumping traces to the filesystem, Twitters’ Zipkin (a tracing sink and visualization system developed by Twitter https://github.com/twitter/zipkin), or Apache HBase. Executions can be viewed either in Zipkin or in pygraph (https://code.google.com/p/python-graph/). Since the initial sprint in the summer of 2012 which saw HTrace patches proposed for Apache HDFS and committed to Apache HBase, development has been sporadic; mostly a single developer or two adding a feature or bug fixing. HTrace is currently undergoing a new “spurt” of development with the effort to get HTrace added to Apache HDFS revived and a new standalone viewing facility being added in to HTrace itself. HTrace has been integrated by Apache Phoenix. === Meritocracy === HTrace, up to
Re: [VOTE] Accept HTrace into the Apache Incubator
+1 (non-binding). On Thu, Nov 6, 2014 at 11:10 AM, Dilli Arumugam darumu...@hortonworks.com wrote: +1 (non-binding) On Thu, Nov 6, 2014 at 10:23 AM, Elliott Clark ecl...@apache.org wrote: + 1 ( Non-Binding) On Thu, Nov 6, 2014 at 10:15 AM, Masatake Iwasaki iwasak...@oss.nttdata.co.jp wrote: +1 (non-binding) Masatake Iwasaki (11/5/14, 11:36), Roman Shaposhnik wrote: On Wed, Nov 5, 2014 at 11:16 AM, Roman Shaposhnik r...@apache.org wrote: Following the discussion earlier in the thread: http://s.apache.org/Dk7 I would like to call a VOTE for accepting HTrace as a new incubator project. The proposal is available at: https://wiki.apache.org/incubator/HTraceProposal (a full version of the proposal is attached) Vote is open until at least Sunday, 9th November 2014, 23:59:00 UTC [ ] +1 accept Lens in the Incubator [ ] ±0 [ ] -1 because... Thanks, Roman. == Abstract == HTrace is a tracing framework intended for use with distributed systems written in java. == Proposal == HTrace is an aid for understanding system behavior and for reasoning about performance issues in distributed systems. HTrace is primarily a low impedance library that a java distributed system can incorporate to generate ‘breadcrumbs’ or ‘traces’ along the path of execution, even as it crosses processes and machines. HTrace also includes various tools and glue for collecting, processing and ‘visualizing’ captured execution traces for analysis ex post facto of where time was spent and what resources were consumed. == Background == Distributed systems are made up of multiple software components running on multiple computers connected by networks. Debugging or profiling operations run over non-trivial distributed systems -- figuring execution paths and what services, machines, and libraries participated in the processing of a request -- can be involved. == Rationale == Rather than have each distributed system build its own custom ‘tracing’ libraries, ideally all would use a single project that provides necessary primitives and saves each project building its own visualizations and processing tools anew. Google described “...[a] large-scale distributed systems tracing infrastructure” in Dapper, a Large-Scale Distributed Systems Tracing Infrastructure. The paper tells a compelling story of what is possible when disparate systems standardize on a single tracing library and cooperate, ‘passing the baton’, filling out trace context as executions cross systems. HTrace aims to provide a rough equivalent in open source of the described core Dapper tools and library. As it is adopted by more projects, there will be a ‘network effect’ as HTrace will provide a more comprehensive view of activity on the cluster. For example, as HDFS gets HTrace support, we can connect this with the HTrace support in HBase to follow HBase requests as they enter HDFS. Given the success of HTrace depends on its being integrated by many projects, HTrace should be perceived as unhampered, free of any commercial, political, or legal ‘taint’. Being an Apache project would help in this regard. == Initial Goals == HTrace is a small project of narrow scope but with a grand vision: * Move the HTrace source and repository to Apache, a vendor-neutral location. Currently HTrace resides at a Cloudera-hosted repository. * Add past contributors as committers and institute Apache governance. * Evangelize and encourage HTrace diffusion. Initially we will continue a focus on the Hadoop space since that is where most of the initial contributors work and it is where HTrace has been initially deployed. * Building out the standalone visualization tool that ships with HTrace. * Build more community and add more committers == Current Status == Currently HTrace has a viable Java trace library that can be interpolated to create ‘traces’. The work that needs to be done on this library is mostly bug fixes, ease-of-use improvements, and performance tweaks. In the future, we may add libraries for other languages besides Java. HTrace has means of dumping traces to the filesystem, Twitters’ Zipkin (a tracing sink and visualization system developed by Twitter https://github.com/twitter/zipkin), or Apache HBase. Executions can be viewed either in Zipkin or in pygraph (https://code.google.com/p/python-graph/). Since the initial sprint in the summer of 2012 which saw HTrace patches proposed for Apache HDFS and committed to Apache HBase, development has been sporadic; mostly a single developer or two adding a feature or bug fixing. HTrace is currently undergoing a new “spurt”
Re: [VOTE] Accept HTrace into the Apache Incubator
+1 (binding) Regards, Arvind Prabhakar On Wed, Nov 5, 2014 at 11:36 AM, Roman Shaposhnik r...@apache.org wrote: On Wed, Nov 5, 2014 at 11:16 AM, Roman Shaposhnik r...@apache.org wrote: Following the discussion earlier in the thread: http://s.apache.org/Dk7 I would like to call a VOTE for accepting HTrace as a new incubator project. The proposal is available at: https://wiki.apache.org/incubator/HTraceProposal (a full version of the proposal is attached) Vote is open until at least Sunday, 9th November 2014, 23:59:00 UTC [ ] +1 accept Lens in the Incubator [ ] ±0 [ ] -1 because... Thanks, Roman. == Abstract == HTrace is a tracing framework intended for use with distributed systems written in java. == Proposal == HTrace is an aid for understanding system behavior and for reasoning about performance issues in distributed systems. HTrace is primarily a low impedance library that a java distributed system can incorporate to generate ‘breadcrumbs’ or ‘traces’ along the path of execution, even as it crosses processes and machines. HTrace also includes various tools and glue for collecting, processing and ‘visualizing’ captured execution traces for analysis ex post facto of where time was spent and what resources were consumed. == Background == Distributed systems are made up of multiple software components running on multiple computers connected by networks. Debugging or profiling operations run over non-trivial distributed systems -- figuring execution paths and what services, machines, and libraries participated in the processing of a request -- can be involved. == Rationale == Rather than have each distributed system build its own custom ‘tracing’ libraries, ideally all would use a single project that provides necessary primitives and saves each project building its own visualizations and processing tools anew. Google described “...[a] large-scale distributed systems tracing infrastructure” in Dapper, a Large-Scale Distributed Systems Tracing Infrastructure. The paper tells a compelling story of what is possible when disparate systems standardize on a single tracing library and cooperate, ‘passing the baton’, filling out trace context as executions cross systems. HTrace aims to provide a rough equivalent in open source of the described core Dapper tools and library. As it is adopted by more projects, there will be a ‘network effect’ as HTrace will provide a more comprehensive view of activity on the cluster. For example, as HDFS gets HTrace support, we can connect this with the HTrace support in HBase to follow HBase requests as they enter HDFS. Given the success of HTrace depends on its being integrated by many projects, HTrace should be perceived as unhampered, free of any commercial, political, or legal ‘taint’. Being an Apache project would help in this regard. == Initial Goals == HTrace is a small project of narrow scope but with a grand vision: * Move the HTrace source and repository to Apache, a vendor-neutral location. Currently HTrace resides at a Cloudera-hosted repository. * Add past contributors as committers and institute Apache governance. * Evangelize and encourage HTrace diffusion. Initially we will continue a focus on the Hadoop space since that is where most of the initial contributors work and it is where HTrace has been initially deployed. * Building out the standalone visualization tool that ships with HTrace. * Build more community and add more committers == Current Status == Currently HTrace has a viable Java trace library that can be interpolated to create ‘traces’. The work that needs to be done on this library is mostly bug fixes, ease-of-use improvements, and performance tweaks. In the future, we may add libraries for other languages besides Java. HTrace has means of dumping traces to the filesystem, Twitters’ Zipkin (a tracing sink and visualization system developed by Twitter https://github.com/twitter/zipkin), or Apache HBase. Executions can be viewed either in Zipkin or in pygraph (https://code.google.com/p/python-graph/). Since the initial sprint in the summer of 2012 which saw HTrace patches proposed for Apache HDFS and committed to Apache HBase, development has been sporadic; mostly a single developer or two adding a feature or bug fixing. HTrace is currently undergoing a new “spurt” of development with the effort to get HTrace added to Apache HDFS revived and a new standalone viewing facility being added in to HTrace itself. HTrace has been integrated by Apache Phoenix. === Meritocracy === HTrace, up to this, has been run by Apache committers and PMC members. We want to build out a diverse developer and user community and run the HTrace project in the Apache way. Users and new contributors will be treated with respect and welcomed; they will earn merit in the project by tendering quality patches and
Re: [VOTE] Accept HTrace into the Apache Incubator
+1 (binding) On Wed, Nov 5, 2014 at 11:16 AM, Roman Shaposhnik r...@apache.org wrote: Following the discussion earlier in the thread: http://s.apache.org/Dk7 I would like to call a VOTE for accepting HTrace as a new incubator project. The proposal is available at: https://wiki.apache.org/incubator/HTraceProposal Vote is open until at least Sunday, 9th November 2014, 23:59:00 UTC [ ] +1 accept Lens in the Incubator [ ] ±0 [ ] -1 because... - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Best regards, - Andy Problems worthy of attack prove their worth by hitting back. - Piet Hein (via Tom White)
[VOTE] Accept HTrace into the Apache Incubator
Following the discussion earlier in the thread: http://s.apache.org/Dk7 I would like to call a VOTE for accepting HTrace as a new incubator project. The proposal is available at: https://wiki.apache.org/incubator/HTraceProposal Vote is open until at least Sunday, 9th November 2014, 23:59:00 UTC [ ] +1 accept Lens in the Incubator [ ] ±0 [ ] -1 because... - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept HTrace into the Apache Incubator
Hey Roman Can you please attach the full proposal to the vote thread. The wiki can be removed/changed and this way it keeps the initial proposal and vote thread together -Jake On Wed, Nov 5, 2014 at 2:16 PM, Roman Shaposhnik r...@apache.org wrote: Following the discussion earlier in the thread: http://s.apache.org/Dk7 I would like to call a VOTE for accepting HTrace as a new incubator project. The proposal is available at: https://wiki.apache.org/incubator/HTraceProposal Vote is open until at least Sunday, 9th November 2014, 23:59:00 UTC [ ] +1 accept Lens in the Incubator [ ] ±0 [ ] -1 because... - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept HTrace into the Apache Incubator
+1 On Wed, Nov 5, 2014 at 11:16 AM, Roman Shaposhnik r...@apache.org wrote: Following the discussion earlier in the thread: http://s.apache.org/Dk7 I would like to call a VOTE for accepting HTrace as a new incubator project. The proposal is available at: https://wiki.apache.org/incubator/HTraceProposal Vote is open until at least Sunday, 9th November 2014, 23:59:00 UTC [ X] +1 accept HTrace in the Incubator [ ] ±0 [ ] -1 because... - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[VOTE] Accept HTrace into the Apache Incubator
On Wed, Nov 5, 2014 at 11:16 AM, Roman Shaposhnik r...@apache.org wrote: Following the discussion earlier in the thread: http://s.apache.org/Dk7 I would like to call a VOTE for accepting HTrace as a new incubator project. The proposal is available at: https://wiki.apache.org/incubator/HTraceProposal (a full version of the proposal is attached) Vote is open until at least Sunday, 9th November 2014, 23:59:00 UTC [ ] +1 accept Lens in the Incubator [ ] ±0 [ ] -1 because... Thanks, Roman. == Abstract == HTrace is a tracing framework intended for use with distributed systems written in java. == Proposal == HTrace is an aid for understanding system behavior and for reasoning about performance issues in distributed systems. HTrace is primarily a low impedance library that a java distributed system can incorporate to generate ‘breadcrumbs’ or ‘traces’ along the path of execution, even as it crosses processes and machines. HTrace also includes various tools and glue for collecting, processing and ‘visualizing’ captured execution traces for analysis ex post facto of where time was spent and what resources were consumed. == Background == Distributed systems are made up of multiple software components running on multiple computers connected by networks. Debugging or profiling operations run over non-trivial distributed systems -- figuring execution paths and what services, machines, and libraries participated in the processing of a request -- can be involved. == Rationale == Rather than have each distributed system build its own custom ‘tracing’ libraries, ideally all would use a single project that provides necessary primitives and saves each project building its own visualizations and processing tools anew. Google described “...[a] large-scale distributed systems tracing infrastructure” in Dapper, a Large-Scale Distributed Systems Tracing Infrastructure. The paper tells a compelling story of what is possible when disparate systems standardize on a single tracing library and cooperate, ‘passing the baton’, filling out trace context as executions cross systems. HTrace aims to provide a rough equivalent in open source of the described core Dapper tools and library. As it is adopted by more projects, there will be a ‘network effect’ as HTrace will provide a more comprehensive view of activity on the cluster. For example, as HDFS gets HTrace support, we can connect this with the HTrace support in HBase to follow HBase requests as they enter HDFS. Given the success of HTrace depends on its being integrated by many projects, HTrace should be perceived as unhampered, free of any commercial, political, or legal ‘taint’. Being an Apache project would help in this regard. == Initial Goals == HTrace is a small project of narrow scope but with a grand vision: * Move the HTrace source and repository to Apache, a vendor-neutral location. Currently HTrace resides at a Cloudera-hosted repository. * Add past contributors as committers and institute Apache governance. * Evangelize and encourage HTrace diffusion. Initially we will continue a focus on the Hadoop space since that is where most of the initial contributors work and it is where HTrace has been initially deployed. * Building out the standalone visualization tool that ships with HTrace. * Build more community and add more committers == Current Status == Currently HTrace has a viable Java trace library that can be interpolated to create ‘traces’. The work that needs to be done on this library is mostly bug fixes, ease-of-use improvements, and performance tweaks. In the future, we may add libraries for other languages besides Java. HTrace has means of dumping traces to the filesystem, Twitters’ Zipkin (a tracing sink and visualization system developed by Twitter https://github.com/twitter/zipkin), or Apache HBase. Executions can be viewed either in Zipkin or in pygraph (https://code.google.com/p/python-graph/). Since the initial sprint in the summer of 2012 which saw HTrace patches proposed for Apache HDFS and committed to Apache HBase, development has been sporadic; mostly a single developer or two adding a feature or bug fixing. HTrace is currently undergoing a new “spurt” of development with the effort to get HTrace added to Apache HDFS revived and a new standalone viewing facility being added in to HTrace itself. HTrace has been integrated by Apache Phoenix. === Meritocracy === HTrace, up to this, has been run by Apache committers and PMC members. We want to build out a diverse developer and user community and run the HTrace project in the Apache way. Users and new contributors will be treated with respect and welcomed; they will earn merit in the project by tendering quality patches and support that move the project forward. Those with a proven support and quality patch track record will be encouraged to become committers. === Community === There are just a few developers involved at the moment. If our project is
Re: [VOTE] Accept HTrace into the Apache Incubator
+1 (binding) -Jake On Wed, Nov 5, 2014 at 2:36 PM, Roman Shaposhnik r...@apache.org wrote: On Wed, Nov 5, 2014 at 11:16 AM, Roman Shaposhnik r...@apache.org wrote: Following the discussion earlier in the thread: http://s.apache.org/Dk7 I would like to call a VOTE for accepting HTrace as a new incubator project. The proposal is available at: https://wiki.apache.org/incubator/HTraceProposal (a full version of the proposal is attached) Vote is open until at least Sunday, 9th November 2014, 23:59:00 UTC [ ] +1 accept Lens in the Incubator [ ] ±0 [ ] -1 because... Thanks, Roman. == Abstract == HTrace is a tracing framework intended for use with distributed systems written in java. == Proposal == HTrace is an aid for understanding system behavior and for reasoning about performance issues in distributed systems. HTrace is primarily a low impedance library that a java distributed system can incorporate to generate ‘breadcrumbs’ or ‘traces’ along the path of execution, even as it crosses processes and machines. HTrace also includes various tools and glue for collecting, processing and ‘visualizing’ captured execution traces for analysis ex post facto of where time was spent and what resources were consumed. == Background == Distributed systems are made up of multiple software components running on multiple computers connected by networks. Debugging or profiling operations run over non-trivial distributed systems -- figuring execution paths and what services, machines, and libraries participated in the processing of a request -- can be involved. == Rationale == Rather than have each distributed system build its own custom ‘tracing’ libraries, ideally all would use a single project that provides necessary primitives and saves each project building its own visualizations and processing tools anew. Google described “...[a] large-scale distributed systems tracing infrastructure” in Dapper, a Large-Scale Distributed Systems Tracing Infrastructure. The paper tells a compelling story of what is possible when disparate systems standardize on a single tracing library and cooperate, ‘passing the baton’, filling out trace context as executions cross systems. HTrace aims to provide a rough equivalent in open source of the described core Dapper tools and library. As it is adopted by more projects, there will be a ‘network effect’ as HTrace will provide a more comprehensive view of activity on the cluster. For example, as HDFS gets HTrace support, we can connect this with the HTrace support in HBase to follow HBase requests as they enter HDFS. Given the success of HTrace depends on its being integrated by many projects, HTrace should be perceived as unhampered, free of any commercial, political, or legal ‘taint’. Being an Apache project would help in this regard. == Initial Goals == HTrace is a small project of narrow scope but with a grand vision: * Move the HTrace source and repository to Apache, a vendor-neutral location. Currently HTrace resides at a Cloudera-hosted repository. * Add past contributors as committers and institute Apache governance. * Evangelize and encourage HTrace diffusion. Initially we will continue a focus on the Hadoop space since that is where most of the initial contributors work and it is where HTrace has been initially deployed. * Building out the standalone visualization tool that ships with HTrace. * Build more community and add more committers == Current Status == Currently HTrace has a viable Java trace library that can be interpolated to create ‘traces’. The work that needs to be done on this library is mostly bug fixes, ease-of-use improvements, and performance tweaks. In the future, we may add libraries for other languages besides Java. HTrace has means of dumping traces to the filesystem, Twitters’ Zipkin (a tracing sink and visualization system developed by Twitter https://github.com/twitter/zipkin), or Apache HBase. Executions can be viewed either in Zipkin or in pygraph (https://code.google.com/p/python-graph/). Since the initial sprint in the summer of 2012 which saw HTrace patches proposed for Apache HDFS and committed to Apache HBase, development has been sporadic; mostly a single developer or two adding a feature or bug fixing. HTrace is currently undergoing a new “spurt” of development with the effort to get HTrace added to Apache HDFS revived and a new standalone viewing facility being added in to HTrace itself. HTrace has been integrated by Apache Phoenix. === Meritocracy === HTrace, up to this, has been run by Apache committers and PMC members. We want to build out a diverse developer and user community and run the HTrace project in the Apache way. Users and new contributors will be treated with respect and welcomed; they will earn merit in the project by tendering quality patches and support that move the
Re: [VOTE] Accept HTrace into the Apache Incubator
+1 (can't recall if my vote is binding as a Member, or if you have to be IPMC) On Wed, Nov 5, 2014 at 11:32 AM, Stack st...@duboce.net wrote: +1 On Wed, Nov 5, 2014 at 11:16 AM, Roman Shaposhnik r...@apache.org wrote: Following the discussion earlier in the thread: http://s.apache.org/Dk7 I would like to call a VOTE for accepting HTrace as a new incubator project. The proposal is available at: https://wiki.apache.org/incubator/HTraceProposal Vote is open until at least Sunday, 9th November 2014, 23:59:00 UTC [ X] +1 accept HTrace in the Incubator [ ] ±0 [ ] -1 because... - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Todd Lipcon Software Engineer, Cloudera
Re: [VOTE] Accept HTrace into the Apache Incubator
non-binding, but as you are a member you can ask at any time to be on the IPMC -Jake On Wed, Nov 5, 2014 at 2:39 PM, Todd Lipcon t...@cloudera.com wrote: +1 (can't recall if my vote is binding as a Member, or if you have to be IPMC) On Wed, Nov 5, 2014 at 11:32 AM, Stack st...@duboce.net wrote: +1 On Wed, Nov 5, 2014 at 11:16 AM, Roman Shaposhnik r...@apache.org wrote: Following the discussion earlier in the thread: http://s.apache.org/Dk7 I would like to call a VOTE for accepting HTrace as a new incubator project. The proposal is available at: https://wiki.apache.org/incubator/HTraceProposal Vote is open until at least Sunday, 9th November 2014, 23:59:00 UTC [ X] +1 accept HTrace in the Incubator [ ] ±0 [ ] -1 because... - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Todd Lipcon Software Engineer, Cloudera
Re: [VOTE] Accept HTrace into the Apache Incubator
+1 binding cheers and good luck! ++ Chris Mattmann, Ph.D. Chief Architect Instrument Software and Science Data Systems Section (398) NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA Office: 168-519, Mailstop: 168-527 Email: chris.a.mattm...@nasa.gov WWW: http://sunset.usc.edu/~mattmann/ ++ Adjunct Associate Professor, Computer Science Department University of Southern California, Los Angeles, CA 90089 USA ++ -Original Message- From: Roman Shaposhnik r...@apache.org Reply-To: general@incubator.apache.org general@incubator.apache.org Date: Wednesday, November 5, 2014 at 12:16 PM To: general@incubator.apache.org general@incubator.apache.org Subject: [VOTE] Accept HTrace into the Apache Incubator Following the discussion earlier in the thread: http://s.apache.org/Dk7 I would like to call a VOTE for accepting HTrace as a new incubator project. The proposal is available at: https://wiki.apache.org/incubator/HTraceProposal Vote is open until at least Sunday, 9th November 2014, 23:59:00 UTC [ ] +1 accept Lens in the Incubator [ ] ±0 [ ] -1 because... - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept HTrace into the Apache Incubator
+1 (binding) On Wed, Nov 5, 2014 at 11:39 AM, Jake Farrell jfarr...@apache.org wrote: +1 (binding) -Jake On Wed, Nov 5, 2014 at 2:36 PM, Roman Shaposhnik r...@apache.org wrote: On Wed, Nov 5, 2014 at 11:16 AM, Roman Shaposhnik r...@apache.org wrote: Following the discussion earlier in the thread: http://s.apache.org/Dk7 I would like to call a VOTE for accepting HTrace as a new incubator project. The proposal is available at: https://wiki.apache.org/incubator/HTraceProposal (a full version of the proposal is attached) Vote is open until at least Sunday, 9th November 2014, 23:59:00 UTC [ ] +1 accept Lens in the Incubator [ ] ±0 [ ] -1 because... Thanks, Roman. == Abstract == HTrace is a tracing framework intended for use with distributed systems written in java. == Proposal == HTrace is an aid for understanding system behavior and for reasoning about performance issues in distributed systems. HTrace is primarily a low impedance library that a java distributed system can incorporate to generate ‘breadcrumbs’ or ‘traces’ along the path of execution, even as it crosses processes and machines. HTrace also includes various tools and glue for collecting, processing and ‘visualizing’ captured execution traces for analysis ex post facto of where time was spent and what resources were consumed. == Background == Distributed systems are made up of multiple software components running on multiple computers connected by networks. Debugging or profiling operations run over non-trivial distributed systems -- figuring execution paths and what services, machines, and libraries participated in the processing of a request -- can be involved. == Rationale == Rather than have each distributed system build its own custom ‘tracing’ libraries, ideally all would use a single project that provides necessary primitives and saves each project building its own visualizations and processing tools anew. Google described “...[a] large-scale distributed systems tracing infrastructure” in Dapper, a Large-Scale Distributed Systems Tracing Infrastructure. The paper tells a compelling story of what is possible when disparate systems standardize on a single tracing library and cooperate, ‘passing the baton’, filling out trace context as executions cross systems. HTrace aims to provide a rough equivalent in open source of the described core Dapper tools and library. As it is adopted by more projects, there will be a ‘network effect’ as HTrace will provide a more comprehensive view of activity on the cluster. For example, as HDFS gets HTrace support, we can connect this with the HTrace support in HBase to follow HBase requests as they enter HDFS. Given the success of HTrace depends on its being integrated by many projects, HTrace should be perceived as unhampered, free of any commercial, political, or legal ‘taint’. Being an Apache project would help in this regard. == Initial Goals == HTrace is a small project of narrow scope but with a grand vision: * Move the HTrace source and repository to Apache, a vendor-neutral location. Currently HTrace resides at a Cloudera-hosted repository. * Add past contributors as committers and institute Apache governance. * Evangelize and encourage HTrace diffusion. Initially we will continue a focus on the Hadoop space since that is where most of the initial contributors work and it is where HTrace has been initially deployed. * Building out the standalone visualization tool that ships with HTrace. * Build more community and add more committers == Current Status == Currently HTrace has a viable Java trace library that can be interpolated to create ‘traces’. The work that needs to be done on this library is mostly bug fixes, ease-of-use improvements, and performance tweaks. In the future, we may add libraries for other languages besides Java. HTrace has means of dumping traces to the filesystem, Twitters’ Zipkin (a tracing sink and visualization system developed by Twitter https://github.com/twitter/zipkin), or Apache HBase. Executions can be viewed either in Zipkin or in pygraph (https://code.google.com/p/python-graph/). Since the initial sprint in the summer of 2012 which saw HTrace patches proposed for Apache HDFS and committed to Apache HBase, development has been sporadic; mostly a single developer or two adding a feature or bug fixing. HTrace is currently undergoing a new “spurt” of development with the effort to get HTrace added to Apache HDFS revived and a new standalone viewing facility being added in to HTrace itself. HTrace has been integrated by Apache Phoenix. === Meritocracy === HTrace, up to this, has been run by Apache committers and PMC members. We want to build out a diverse developer and user
Re: [VOTE] Accept HTrace into the Apache Incubator
+1 (binding) I voted already on what appears to be a separate thread. Watch for duplicate. On Wed, Nov 5, 2014 at 11:48 AM, Mattmann, Chris A (3980) chris.a.mattm...@jpl.nasa.gov wrote: +1 binding cheers and good luck! ++ Chris Mattmann, Ph.D. Chief Architect Instrument Software and Science Data Systems Section (398) NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA Office: 168-519, Mailstop: 168-527 Email: chris.a.mattm...@nasa.gov WWW: http://sunset.usc.edu/~mattmann/ ++ Adjunct Associate Professor, Computer Science Department University of Southern California, Los Angeles, CA 90089 USA ++ -Original Message- From: Roman Shaposhnik r...@apache.org Reply-To: general@incubator.apache.org general@incubator.apache.org Date: Wednesday, November 5, 2014 at 12:16 PM To: general@incubator.apache.org general@incubator.apache.org Subject: [VOTE] Accept HTrace into the Apache Incubator Following the discussion earlier in the thread: http://s.apache.org/Dk7 I would like to call a VOTE for accepting HTrace as a new incubator project. The proposal is available at: https://wiki.apache.org/incubator/HTraceProposal Vote is open until at least Sunday, 9th November 2014, 23:59:00 UTC [ ] +1 accept Lens in the Incubator [ ] ±0 [ ] -1 because... - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept HTrace into the Apache Incubator
+1 (binding) On Wed, Nov 5, 2014 at 11:16 AM, Roman Shaposhnik r...@apache.org wrote: Following the discussion earlier in the thread: http://s.apache.org/Dk7 I would like to call a VOTE for accepting HTrace as a new incubator project. The proposal is available at: https://wiki.apache.org/incubator/HTraceProposal Vote is open until at least Sunday, 9th November 2014, 23:59:00 UTC [ ] +1 accept Lens in the Incubator [ ] ±0 [ ] -1 because... - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- http://hortonworks.com/download/ -- CONFIDENTIALITY NOTICE NOTICE: This message is intended for the use of the individual or entity to which it is addressed and may contain information that is confidential, privileged and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any printing, copying, dissemination, distribution, disclosure or forwarding of this communication is strictly prohibited. If you have received this communication in error, please contact the sender immediately and delete it from your system. Thank You.
Re: [VOTE] Accept HTrace into the Apache Incubator
+1 On Wed, Nov 5, 2014 at 11:37 AM, Roman Shaposhnik r...@apache.org wrote: Following the discussion earlier in the thread: http://s.apache.org/Dk7 I would like to call a VOTE for accepting HTrace as a new incubator project. The proposal is available at: https://wiki.apache.org/incubator/HTraceProposal Vote is open until at least Sunday, 9th November 2014, 23:59:00 UTC [ ] +1 accept Lens in the Incubator [ ] ±0 [ ] -1 because...
Re: [VOTE] Accept HTrace into the Apache Incubator
+1 (non-binding) On Wed, Nov 5, 2014 at 1:34 PM, Billie Rinaldi bil...@apache.org wrote: +1 On Wed, Nov 5, 2014 at 11:37 AM, Roman Shaposhnik r...@apache.org wrote: Following the discussion earlier in the thread: http://s.apache.org/Dk7 I would like to call a VOTE for accepting HTrace as a new incubator project. The proposal is available at: https://wiki.apache.org/incubator/HTraceProposal Vote is open until at least Sunday, 9th November 2014, 23:59:00 UTC [ ] +1 accept Lens in the Incubator [ ] ±0 [ ] -1 because... -- Regards, Venkatesh “Perfection (in design) is achieved not when there is nothing more to add, but rather when there is nothing more to take away.” - Antoine de Saint-Exupéry
Re: [VOTE] Accept HTrace into the Apache Incubator
I think the concept is great. Would look forward to support for other Hadoop related projects (Hive, for example) Also would be interested to see whether we can leverage this to correlate audit information across different systems +1 non-binding On Wed, Nov 5, 2014 at 11:36 AM, Roman Shaposhnik r...@apache.org wrote: On Wed, Nov 5, 2014 at 11:16 AM, Roman Shaposhnik r...@apache.org wrote: Following the discussion earlier in the thread: http://s.apache.org/Dk7 I would like to call a VOTE for accepting HTrace as a new incubator project. The proposal is available at: https://wiki.apache.org/incubator/HTraceProposal (a full version of the proposal is attached) Vote is open until at least Sunday, 9th November 2014, 23:59:00 UTC [ ] +1 accept Lens in the Incubator [ ] ±0 [ ] -1 because... Thanks, Roman. == Abstract == HTrace is a tracing framework intended for use with distributed systems written in java. == Proposal == HTrace is an aid for understanding system behavior and for reasoning about performance issues in distributed systems. HTrace is primarily a low impedance library that a java distributed system can incorporate to generate ‘breadcrumbs’ or ‘traces’ along the path of execution, even as it crosses processes and machines. HTrace also includes various tools and glue for collecting, processing and ‘visualizing’ captured execution traces for analysis ex post facto of where time was spent and what resources were consumed. == Background == Distributed systems are made up of multiple software components running on multiple computers connected by networks. Debugging or profiling operations run over non-trivial distributed systems -- figuring execution paths and what services, machines, and libraries participated in the processing of a request -- can be involved. == Rationale == Rather than have each distributed system build its own custom ‘tracing’ libraries, ideally all would use a single project that provides necessary primitives and saves each project building its own visualizations and processing tools anew. Google described “...[a] large-scale distributed systems tracing infrastructure” in Dapper, a Large-Scale Distributed Systems Tracing Infrastructure. The paper tells a compelling story of what is possible when disparate systems standardize on a single tracing library and cooperate, ‘passing the baton’, filling out trace context as executions cross systems. HTrace aims to provide a rough equivalent in open source of the described core Dapper tools and library. As it is adopted by more projects, there will be a ‘network effect’ as HTrace will provide a more comprehensive view of activity on the cluster. For example, as HDFS gets HTrace support, we can connect this with the HTrace support in HBase to follow HBase requests as they enter HDFS. Given the success of HTrace depends on its being integrated by many projects, HTrace should be perceived as unhampered, free of any commercial, political, or legal ‘taint’. Being an Apache project would help in this regard. == Initial Goals == HTrace is a small project of narrow scope but with a grand vision: * Move the HTrace source and repository to Apache, a vendor-neutral location. Currently HTrace resides at a Cloudera-hosted repository. * Add past contributors as committers and institute Apache governance. * Evangelize and encourage HTrace diffusion. Initially we will continue a focus on the Hadoop space since that is where most of the initial contributors work and it is where HTrace has been initially deployed. * Building out the standalone visualization tool that ships with HTrace. * Build more community and add more committers == Current Status == Currently HTrace has a viable Java trace library that can be interpolated to create ‘traces’. The work that needs to be done on this library is mostly bug fixes, ease-of-use improvements, and performance tweaks. In the future, we may add libraries for other languages besides Java. HTrace has means of dumping traces to the filesystem, Twitters’ Zipkin (a tracing sink and visualization system developed by Twitter https://github.com/twitter/zipkin), or Apache HBase. Executions can be viewed either in Zipkin or in pygraph (https://code.google.com/p/python-graph/). Since the initial sprint in the summer of 2012 which saw HTrace patches proposed for Apache HDFS and committed to Apache HBase, development has been sporadic; mostly a single developer or two adding a feature or bug fixing. HTrace is currently undergoing a new “spurt” of development with the effort to get HTrace added to Apache HDFS revived and a new standalone viewing facility being added in to HTrace itself. HTrace has been integrated by Apache Phoenix. === Meritocracy === HTrace, up to this, has been run by Apache committers and PMC members. We want to build out a diverse developer and
Re: [VOTE] Accept HTrace into the Apache Incubator
On Wednesday, 5 November 2014, Roman Shaposhnik r...@apache.org wrote: On Wed, Nov 5, 2014 at 11:16 AM, Roman Shaposhnik r...@apache.org javascript:; wrote: Following the discussion earlier in the thread: http://s.apache.org/Dk7 I would like to call a VOTE for accepting HTrace as a new incubator project. The proposal is available at: https://wiki.apache.org/incubator/HTraceProposal (a full version of the proposal is attached) Vote is open until at least Sunday, 9th November 2014, 23:59:00 UTC [ ] +1 accept Lens in the Incubator [ ] ±0 [ ] -1 because... +1 (non-binding) Lieven Thanks, Roman. == Abstract == HTrace is a tracing framework intended for use with distributed systems written in java. == Proposal == HTrace is an aid for understanding system behavior and for reasoning about performance issues in distributed systems. HTrace is primarily a low impedance library that a java distributed system can incorporate to generate ‘breadcrumbs’ or ‘traces’ along the path of execution, even as it crosses processes and machines. HTrace also includes various tools and glue for collecting, processing and ‘visualizing’ captured execution traces for analysis ex post facto of where time was spent and what resources were consumed. == Background == Distributed systems are made up of multiple software components running on multiple computers connected by networks. Debugging or profiling operations run over non-trivial distributed systems -- figuring execution paths and what services, machines, and libraries participated in the processing of a request -- can be involved. == Rationale == Rather than have each distributed system build its own custom ‘tracing’ libraries, ideally all would use a single project that provides necessary primitives and saves each project building its own visualizations and processing tools anew. Google described “...[a] large-scale distributed systems tracing infrastructure” in Dapper, a Large-Scale Distributed Systems Tracing Infrastructure. The paper tells a compelling story of what is possible when disparate systems standardize on a single tracing library and cooperate, ‘passing the baton’, filling out trace context as executions cross systems. HTrace aims to provide a rough equivalent in open source of the described core Dapper tools and library. As it is adopted by more projects, there will be a ‘network effect’ as HTrace will provide a more comprehensive view of activity on the cluster. For example, as HDFS gets HTrace support, we can connect this with the HTrace support in HBase to follow HBase requests as they enter HDFS. Given the success of HTrace depends on its being integrated by many projects, HTrace should be perceived as unhampered, free of any commercial, political, or legal ‘taint’. Being an Apache project would help in this regard. == Initial Goals == HTrace is a small project of narrow scope but with a grand vision: * Move the HTrace source and repository to Apache, a vendor-neutral location. Currently HTrace resides at a Cloudera-hosted repository. * Add past contributors as committers and institute Apache governance. * Evangelize and encourage HTrace diffusion. Initially we will continue a focus on the Hadoop space since that is where most of the initial contributors work and it is where HTrace has been initially deployed. * Building out the standalone visualization tool that ships with HTrace. * Build more community and add more committers == Current Status == Currently HTrace has a viable Java trace library that can be interpolated to create ‘traces’. The work that needs to be done on this library is mostly bug fixes, ease-of-use improvements, and performance tweaks. In the future, we may add libraries for other languages besides Java. HTrace has means of dumping traces to the filesystem, Twitters’ Zipkin (a tracing sink and visualization system developed by Twitter https://github.com/twitter/zipkin), or Apache HBase. Executions can be viewed either in Zipkin or in pygraph (https://code.google.com/p/python-graph/). Since the initial sprint in the summer of 2012 which saw HTrace patches proposed for Apache HDFS and committed to Apache HBase, development has been sporadic; mostly a single developer or two adding a feature or bug fixing. HTrace is currently undergoing a new “spurt” of development with the effort to get HTrace added to Apache HDFS revived and a new standalone viewing facility being added in to HTrace itself. HTrace has been integrated by Apache Phoenix. === Meritocracy === HTrace, up to this, has been run by Apache committers and PMC members. We want to build out a diverse developer and user community and run the HTrace project in the Apache way. Users and new contributors will be treated with respect and welcomed; they will earn merit in the project by tendering quality patches and