You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@incubator.apache.org by Dave Neuman <ne...@apache.org> on 2017/11/20 18:13:55 UTC
Re: [RESULT] [VOTE] Release Apache Traffic Control 2.0.0 incubating (RC6)
+1 However....
We need to add a release note suggesting that traffic stats works best with
influxdb version < 1.3.x. As of 1.3.x InfluxDB now returns a 400 response
when the client attempts to write points that are outside of the retention
policy. When this happens, Traffic Stats seems to hold on to the "old"
points and attempts to write them again on the next POST. This causes what
is essentially a memory leak in Traffic Stats since it continues to hold
onto and tries to write stats that are outside of the retention policy.
This may or may not affect a user, depending upon which stats they are
trying to write to influxdb. For example, we write the wrap_count to
influxdb, this is a stat that does not often change within 24 hours, so we
see the memory leak with stats not written on each poll of traffic stats.
In versions < 1.3.x InfluxDB would still not write the point, but it would
accept the write request and just drop the points outside of the retention
policy on the floor.
This is fixed here:
https://github.com/apache/incubator-trafficcontrol/pull/1289 and will be in
the next release of traffic control.
Also, we should note that you need to set selinux to "unenforcing" in order
to get the build to work, otherwise you fail on permissions erros. You can
do this with
`setenforce 0` as root.
Thanks,
Dave
On Thu, Jul 6, 2017 at 3:26 PM, Eric Friedrich (efriedri) <
efriedri@cisco.com> wrote:
> Dear IPMC Community,
>
> I am pleased to announce that the Incubator PMC has approved 2.0.0-RC6 of
> Apache Traffic Control (Incubating) for release as “Apache Traffic Control
> (incubating) 2.0.0"
>
> The vote has passed with:
> - three binding "+1" votes
> - no "0" votes
> - no "-1" votes
>
> The votes were (https://lists.apache.org/thread.html/
> c44716e02d175b78def5d1a219474e6f5c397120e33d64208158511e@%
> 3Cgeneral.incubator.apache.org%3E<https://lists.apache.org/thread.html/
> c44716e02d175b78def5d1a219474e6f5c397120e33d64208158511e@<ge
> neral.incubator.apache.org>>):
> - +1, Justin Mclean (binding)
> - +1, John D. Ament (binding)
> - +1, Phil Sorber (binding)
>
> Thank you, for your support!
>
> —Eric
>
> On Jun 30, 2017, at 5:27 PM, Phil Sorber <sorber@apache.org<mailto:sorb
> er@apache.org>> wrote:
>
> Checksums match.
>
> GPG sig verifies, but is untrusted:
> $ gpg --verify apache-trafficcontrol-2.0.0-incubating.tar.gz.asc
> gpg: assuming signed data in `apache-trafficcontrol-2.0.0-
> incubating.tar.gz'
> gpg: Signature made Fri 16 Jun 2017 10:25:33 AM MDT using RSA key ID
> 9AB7BDD5
> gpg: Good signature from "Eric Friedrich (CODE SIGNING KEY) <
> friede@apache.org<ma...@apache.org>>"
> gpg: WARNING: This key is not certified with a trusted signature!
> gpg: There is no indication that the signature belongs to the
> owner.
> Primary key fingerprint: C3ED F3D4 C5EE F3E5 5932 3FF8 F220 0BAB 9AB7 BDD5
>
> No signatures:
> $ gpg --list-sigs 9AB7BDD5
> pub 4096R/9AB7BDD5 2017-04-25
> uid Eric Friedrich (CODE SIGNING KEY) <friede@apache.org
> <ma...@apache.org>>
> sig 3 9AB7BDD5 2017-04-25 Eric Friedrich (CODE SIGNING KEY) <
> friede@apache.org<ma...@apache.org>>
> sub 4096R/F445ABB1 2017-04-25
> sig 9AB7BDD5 2017-04-25 Eric Friedrich (CODE SIGNING KEY) <
> friede@apache.org<ma...@apache.org>>
>
> I won't -1 on that, but we should try to have every RM make sure their keys
> are trusted. I've already spoken with Eric about this.
>
> Build also works, with one caveat. You have to set selinux to unenforcing,
> otherwise you fail from permissions errors. You can do this with
> `setenforce 0` as root. I won't -1 for this either, but we should add that
> to the build documentation.
>
> -rw-r--r--. 1 phil phil 51M Jun 30 15:12
> traffic_monitor-2.0.0-5668.85d14ebe.el7.x86_64.rpm
> -rw-r--r--. 1 phil phil 910K Jun 30 15:10
> traffic_ops-2.0.0-5668.85d14ebe.el7.src.rpm
> -rw-r--r--. 1 phil phil 858K Jun 30 15:10
> traffic_ops-2.0.0-5668.85d14ebe.el7.x86_64.rpm
> -rw-r--r--. 1 phil phil 22K Jun 30 15:10
> traffic_ops_ort-2.0.0-5668.85d14ebe.el7.src.rpm
> -rw-r--r--. 1 phil phil 21K Jun 30 15:10
> traffic_ops_ort-2.0.0-5668.85d14ebe.el7.x86_64.rpm
> -rw-r--r--. 1 phil phil 142K Jun 30 15:12
> traffic_portal-2.0.0-5668.85d14ebe.el7.src.rpm
> -rw-r--r--. 1 phil phil 3.6M Jun 30 15:12
> traffic_portal-2.0.0-5668.85d14ebe.el7.x86_64.rpm
> -rw-r--r--. 1 phil phil 17M Jun 30 15:12
> traffic_router-2.0.0-5668.85d14ebe.el7.x86_64.rpm
> -rw-r--r--. 1 phil phil 417K Jun 30 15:11
> traffic_stats-2.0.0-5668.85d14ebe.el7.src.rpm
> -rw-r--r--. 1 phil phil 5.0M Jun 30 15:11
> traffic_stats-2.0.0-5668.85d14ebe.el7.x86_64.rpm
>
> +1 binding.
>
> Thanks!
>
> On Wed, Jun 28, 2017 at 5:20 PM Justin Mclean <justin@classsoftware.com<
> mailto:justin@classsoftware.com>>
> wrote:
>
> Hi,
>
> The build instructions will be put in place once the release is done
> -- catch-22.
>
> Yep another reason for including them in the release IMO.
>
> Would Jira issues for the copyright and build instruction issues be
> sufficient?
>
> Yes. Changing my vote to +1 binding.
>
> Thanks,
> Justin
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org<mailto:
> general-unsubscribe@incubator.apache.org>
> For additional commands, e-mail: general-help@incubator.apache.org<mailto:
> general-help@incubator.apache.org>
>
>
>
>
Re: [RESULT] [VOTE] Release Apache Traffic Control 2.0.0 incubating (RC6)
Posted by Dave Neuman <ne...@apache.org>.
Oops. I did reply to the wrong email! Sorry.
On Mon, Nov 20, 2017 at 12:47 Dan Kirkwood <da...@gmail.com> wrote:
> Dave, did you mean for this to be for 2.1.0 RC2? You replied to
> the wrong email..
>
> -dan
>
> On Mon, Nov 20, 2017 at 11:13 AM, Dave Neuman <ne...@apache.org> wrote:
> > +1 However....
> > We need to add a release note suggesting that traffic stats works best
> with
> > influxdb version < 1.3.x. As of 1.3.x InfluxDB now returns a 400
> response
> > when the client attempts to write points that are outside of the
> retention
> > policy. When this happens, Traffic Stats seems to hold on to the "old"
> > points and attempts to write them again on the next POST. This causes
> what
> > is essentially a memory leak in Traffic Stats since it continues to hold
> > onto and tries to write stats that are outside of the retention policy.
> > This may or may not affect a user, depending upon which stats they are
> > trying to write to influxdb. For example, we write the wrap_count to
> > influxdb, this is a stat that does not often change within 24 hours, so
> we
> > see the memory leak with stats not written on each poll of traffic stats.
> >
> > In versions < 1.3.x InfluxDB would still not write the point, but it
> would
> > accept the write request and just drop the points outside of the
> retention
> > policy on the floor.
> >
> > This is fixed here:
> > https://github.com/apache/incubator-trafficcontrol/pull/1289 and will
> be in
> > the next release of traffic control.
> >
> > Also, we should note that you need to set selinux to "unenforcing" in
> order
> > to get the build to work, otherwise you fail on permissions erros. You
> can
> > do this with
> > `setenforce 0` as root.
> >
> >
> > Thanks,
> > Dave
> >
> > On Thu, Jul 6, 2017 at 3:26 PM, Eric Friedrich (efriedri) <
> > efriedri@cisco.com> wrote:
> >
> >> Dear IPMC Community,
> >>
> >> I am pleased to announce that the Incubator PMC has approved 2.0.0-RC6
> of
> >> Apache Traffic Control (Incubating) for release as “Apache Traffic
> Control
> >> (incubating) 2.0.0"
> >>
> >> The vote has passed with:
> >> - three binding "+1" votes
> >> - no "0" votes
> >> - no "-1" votes
> >>
> >> The votes were (https://lists.apache.org/thread.html/
> >> c44716e02d175b78def5d1a219474e6f5c397120e33d64208158511e@%
> >> 3Cgeneral.incubator.apache.org%3E<https://lists.apache.org/thread.html/
> >> c44716e02d175b78def5d1a219474e6f5c397120e33d64208158511e@<ge
> >> neral.incubator.apache.org>>):
> >> - +1, Justin Mclean (binding)
> >> - +1, John D. Ament (binding)
> >> - +1, Phil Sorber (binding)
> >>
> >> Thank you, for your support!
> >>
> >> —Eric
> >>
> >> On Jun 30, 2017, at 5:27 PM, Phil Sorber <sorber@apache.org<mailto:sorb
> >> er@apache.org>> wrote:
> >>
> >> Checksums match.
> >>
> >> GPG sig verifies, but is untrusted:
> >> $ gpg --verify apache-trafficcontrol-2.0.0-incubating.tar.gz.asc
> >> gpg: assuming signed data in `apache-trafficcontrol-2.0.0-
> >> incubating.tar.gz'
> >> gpg: Signature made Fri 16 Jun 2017 10:25:33 AM MDT using RSA key ID
> >> 9AB7BDD5
> >> gpg: Good signature from "Eric Friedrich (CODE SIGNING KEY) <
> >> friede@apache.org<ma...@apache.org>>"
> >> gpg: WARNING: This key is not certified with a trusted signature!
> >> gpg: There is no indication that the signature belongs to the
> >> owner.
> >> Primary key fingerprint: C3ED F3D4 C5EE F3E5 5932 3FF8 F220 0BAB 9AB7
> BDD5
> >>
> >> No signatures:
> >> $ gpg --list-sigs 9AB7BDD5
> >> pub 4096R/9AB7BDD5 2017-04-25
> >> uid Eric Friedrich (CODE SIGNING KEY) <
> friede@apache.org
> >> <ma...@apache.org>>
> >> sig 3 9AB7BDD5 2017-04-25 Eric Friedrich (CODE SIGNING KEY) <
> >> friede@apache.org<ma...@apache.org>>
> >> sub 4096R/F445ABB1 2017-04-25
> >> sig 9AB7BDD5 2017-04-25 Eric Friedrich (CODE SIGNING KEY) <
> >> friede@apache.org<ma...@apache.org>>
> >>
> >> I won't -1 on that, but we should try to have every RM make sure their
> keys
> >> are trusted. I've already spoken with Eric about this.
> >>
> >> Build also works, with one caveat. You have to set selinux to
> unenforcing,
> >> otherwise you fail from permissions errors. You can do this with
> >> `setenforce 0` as root. I won't -1 for this either, but we should add
> that
> >> to the build documentation.
> >>
> >> -rw-r--r--. 1 phil phil 51M Jun 30 15:12
> >> traffic_monitor-2.0.0-5668.85d14ebe.el7.x86_64.rpm
> >> -rw-r--r--. 1 phil phil 910K Jun 30 15:10
> >> traffic_ops-2.0.0-5668.85d14ebe.el7.src.rpm
> >> -rw-r--r--. 1 phil phil 858K Jun 30 15:10
> >> traffic_ops-2.0.0-5668.85d14ebe.el7.x86_64.rpm
> >> -rw-r--r--. 1 phil phil 22K Jun 30 15:10
> >> traffic_ops_ort-2.0.0-5668.85d14ebe.el7.src.rpm
> >> -rw-r--r--. 1 phil phil 21K Jun 30 15:10
> >> traffic_ops_ort-2.0.0-5668.85d14ebe.el7.x86_64.rpm
> >> -rw-r--r--. 1 phil phil 142K Jun 30 15:12
> >> traffic_portal-2.0.0-5668.85d14ebe.el7.src.rpm
> >> -rw-r--r--. 1 phil phil 3.6M Jun 30 15:12
> >> traffic_portal-2.0.0-5668.85d14ebe.el7.x86_64.rpm
> >> -rw-r--r--. 1 phil phil 17M Jun 30 15:12
> >> traffic_router-2.0.0-5668.85d14ebe.el7.x86_64.rpm
> >> -rw-r--r--. 1 phil phil 417K Jun 30 15:11
> >> traffic_stats-2.0.0-5668.85d14ebe.el7.src.rpm
> >> -rw-r--r--. 1 phil phil 5.0M Jun 30 15:11
> >> traffic_stats-2.0.0-5668.85d14ebe.el7.x86_64.rpm
> >>
> >> +1 binding.
> >>
> >> Thanks!
> >>
> >> On Wed, Jun 28, 2017 at 5:20 PM Justin Mclean <justin@classsoftware.com
> <
> >> mailto:justin@classsoftware.com>>
> >> wrote:
> >>
> >> Hi,
> >>
> >> The build instructions will be put in place once the release is done
> >> -- catch-22.
> >>
> >> Yep another reason for including them in the release IMO.
> >>
> >> Would Jira issues for the copyright and build instruction issues be
> >> sufficient?
> >>
> >> Yes. Changing my vote to +1 binding.
> >>
> >> Thanks,
> >> Justin
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> <mailto:
> >> general-unsubscribe@incubator.apache.org>
> >> For additional commands, e-mail: general-help@incubator.apache.org
> <mailto:
> >> general-help@incubator.apache.org>
> >>
> >>
> >>
> >>
>
Re: [RESULT] [VOTE] Release Apache Traffic Control 2.0.0 incubating (RC6)
Posted by Dan Kirkwood <da...@gmail.com>.
Dave, did you mean for this to be for 2.1.0 RC2? You replied to
the wrong email..
-dan
On Mon, Nov 20, 2017 at 11:13 AM, Dave Neuman <ne...@apache.org> wrote:
> +1 However....
> We need to add a release note suggesting that traffic stats works best with
> influxdb version < 1.3.x. As of 1.3.x InfluxDB now returns a 400 response
> when the client attempts to write points that are outside of the retention
> policy. When this happens, Traffic Stats seems to hold on to the "old"
> points and attempts to write them again on the next POST. This causes what
> is essentially a memory leak in Traffic Stats since it continues to hold
> onto and tries to write stats that are outside of the retention policy.
> This may or may not affect a user, depending upon which stats they are
> trying to write to influxdb. For example, we write the wrap_count to
> influxdb, this is a stat that does not often change within 24 hours, so we
> see the memory leak with stats not written on each poll of traffic stats.
>
> In versions < 1.3.x InfluxDB would still not write the point, but it would
> accept the write request and just drop the points outside of the retention
> policy on the floor.
>
> This is fixed here:
> https://github.com/apache/incubator-trafficcontrol/pull/1289 and will be in
> the next release of traffic control.
>
> Also, we should note that you need to set selinux to "unenforcing" in order
> to get the build to work, otherwise you fail on permissions erros. You can
> do this with
> `setenforce 0` as root.
>
>
> Thanks,
> Dave
>
> On Thu, Jul 6, 2017 at 3:26 PM, Eric Friedrich (efriedri) <
> efriedri@cisco.com> wrote:
>
>> Dear IPMC Community,
>>
>> I am pleased to announce that the Incubator PMC has approved 2.0.0-RC6 of
>> Apache Traffic Control (Incubating) for release as “Apache Traffic Control
>> (incubating) 2.0.0"
>>
>> The vote has passed with:
>> - three binding "+1" votes
>> - no "0" votes
>> - no "-1" votes
>>
>> The votes were (https://lists.apache.org/thread.html/
>> c44716e02d175b78def5d1a219474e6f5c397120e33d64208158511e@%
>> 3Cgeneral.incubator.apache.org%3E<https://lists.apache.org/thread.html/
>> c44716e02d175b78def5d1a219474e6f5c397120e33d64208158511e@<ge
>> neral.incubator.apache.org>>):
>> - +1, Justin Mclean (binding)
>> - +1, John D. Ament (binding)
>> - +1, Phil Sorber (binding)
>>
>> Thank you, for your support!
>>
>> —Eric
>>
>> On Jun 30, 2017, at 5:27 PM, Phil Sorber <sorber@apache.org<mailto:sorb
>> er@apache.org>> wrote:
>>
>> Checksums match.
>>
>> GPG sig verifies, but is untrusted:
>> $ gpg --verify apache-trafficcontrol-2.0.0-incubating.tar.gz.asc
>> gpg: assuming signed data in `apache-trafficcontrol-2.0.0-
>> incubating.tar.gz'
>> gpg: Signature made Fri 16 Jun 2017 10:25:33 AM MDT using RSA key ID
>> 9AB7BDD5
>> gpg: Good signature from "Eric Friedrich (CODE SIGNING KEY) <
>> friede@apache.org<ma...@apache.org>>"
>> gpg: WARNING: This key is not certified with a trusted signature!
>> gpg: There is no indication that the signature belongs to the
>> owner.
>> Primary key fingerprint: C3ED F3D4 C5EE F3E5 5932 3FF8 F220 0BAB 9AB7 BDD5
>>
>> No signatures:
>> $ gpg --list-sigs 9AB7BDD5
>> pub 4096R/9AB7BDD5 2017-04-25
>> uid Eric Friedrich (CODE SIGNING KEY) <friede@apache.org
>> <ma...@apache.org>>
>> sig 3 9AB7BDD5 2017-04-25 Eric Friedrich (CODE SIGNING KEY) <
>> friede@apache.org<ma...@apache.org>>
>> sub 4096R/F445ABB1 2017-04-25
>> sig 9AB7BDD5 2017-04-25 Eric Friedrich (CODE SIGNING KEY) <
>> friede@apache.org<ma...@apache.org>>
>>
>> I won't -1 on that, but we should try to have every RM make sure their keys
>> are trusted. I've already spoken with Eric about this.
>>
>> Build also works, with one caveat. You have to set selinux to unenforcing,
>> otherwise you fail from permissions errors. You can do this with
>> `setenforce 0` as root. I won't -1 for this either, but we should add that
>> to the build documentation.
>>
>> -rw-r--r--. 1 phil phil 51M Jun 30 15:12
>> traffic_monitor-2.0.0-5668.85d14ebe.el7.x86_64.rpm
>> -rw-r--r--. 1 phil phil 910K Jun 30 15:10
>> traffic_ops-2.0.0-5668.85d14ebe.el7.src.rpm
>> -rw-r--r--. 1 phil phil 858K Jun 30 15:10
>> traffic_ops-2.0.0-5668.85d14ebe.el7.x86_64.rpm
>> -rw-r--r--. 1 phil phil 22K Jun 30 15:10
>> traffic_ops_ort-2.0.0-5668.85d14ebe.el7.src.rpm
>> -rw-r--r--. 1 phil phil 21K Jun 30 15:10
>> traffic_ops_ort-2.0.0-5668.85d14ebe.el7.x86_64.rpm
>> -rw-r--r--. 1 phil phil 142K Jun 30 15:12
>> traffic_portal-2.0.0-5668.85d14ebe.el7.src.rpm
>> -rw-r--r--. 1 phil phil 3.6M Jun 30 15:12
>> traffic_portal-2.0.0-5668.85d14ebe.el7.x86_64.rpm
>> -rw-r--r--. 1 phil phil 17M Jun 30 15:12
>> traffic_router-2.0.0-5668.85d14ebe.el7.x86_64.rpm
>> -rw-r--r--. 1 phil phil 417K Jun 30 15:11
>> traffic_stats-2.0.0-5668.85d14ebe.el7.src.rpm
>> -rw-r--r--. 1 phil phil 5.0M Jun 30 15:11
>> traffic_stats-2.0.0-5668.85d14ebe.el7.x86_64.rpm
>>
>> +1 binding.
>>
>> Thanks!
>>
>> On Wed, Jun 28, 2017 at 5:20 PM Justin Mclean <justin@classsoftware.com<
>> mailto:justin@classsoftware.com>>
>> wrote:
>>
>> Hi,
>>
>> The build instructions will be put in place once the release is done
>> -- catch-22.
>>
>> Yep another reason for including them in the release IMO.
>>
>> Would Jira issues for the copyright and build instruction issues be
>> sufficient?
>>
>> Yes. Changing my vote to +1 binding.
>>
>> Thanks,
>> Justin
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org<mailto:
>> general-unsubscribe@incubator.apache.org>
>> For additional commands, e-mail: general-help@incubator.apache.org<mailto:
>> general-help@incubator.apache.org>
>>
>>
>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org