From users-return-7169-archive-asf-public=cust-asf.ponee.io@trafficserver.apache.org Thu Jul 26 21:58:56 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id D1260180677 for ; Thu, 26 Jul 2018 21:58:55 +0200 (CEST) Received: (qmail 87653 invoked by uid 500); 26 Jul 2018 19:58:54 -0000 Mailing-List: contact users-help@trafficserver.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@trafficserver.apache.org Delivered-To: mailing list users@trafficserver.apache.org Received: (qmail 87636 invoked by uid 99); 26 Jul 2018 19:58:54 -0000 Received: from mail-relay.apache.org (HELO mailrelay2-lw-us.apache.org) (207.244.88.137) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 26 Jul 2018 19:58:54 +0000 Received: from [17.44.27.238] (unknown [17.44.27.238]) by mailrelay2-lw-us.apache.org (ASF Mail Server at mailrelay2-lw-us.apache.org) with ESMTPSA id 791232B19; Thu, 26 Jul 2018 19:58:53 +0000 (UTC) From: Leif Hedstrom Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) Subject: [PROPOSAL] Mark log collation as deprecated for v8.0.0 Message-Id: <2BDBB838-3E2F-4BE4-A103-853D0229FE99@apache.org> Date: Thu, 26 Jul 2018 13:58:52 -0600 To: dev , Mailing-List trafficserver X-Mailer: Apple Mail (2.3445.9.1) Hi all, I=E2=80=99d like to mark the log collation feature as deprecated for the = v8.0.0 release, such that we can remove it from v9.0.0. I have a number = of reasons for this 1) It=E2=80=99s generally really broken. For example, the orphaned logs = files are not handled in any reasonable way, making the feature IMO = unusable. 2) No one has stepped up to the plate to fix anything other than the = critical issues discovered (such as Peter=E2=80=99s memory leak fix). 3) Perhaps most importantly, this is not a problem that ATS should solve = iMO. There are much better systems out there, such as Kafka, Elastic = Search, Splunk etc., all which solves this problem in a much better way. If you have objections to this, expect to have to do some serious work = on this code base, because as I see it, it=E2=80=99s not up to the = quality we expect from ATS. Cheers, =E2=80=94 Leif