> On Apr 27, 2015, at 12:15 AM, Yongming Zhao <ming....@gmail.com> wrote:
> 
> on the collation:
>  I don’t get that many critical bugs on collation: project = TS AND component 
> = Logging AND resolution = Unresolved AND text ~ "collation"  ORDER BY due 
> ASC, priority DESC, created ASC
> so, what is the problem we would like to remove it completely?


We closed a few of them as Won’t Fix. But the issues that were crippling were

        - There is no way to replay an orphaned log

and together with

        https://issues.apache.org/jira/browse/TS-2629
        https://issues.apache.org/jira/browse/TS-2062
        https://issues.apache.org/jira/browse/TS-2101
        https://issues.apache.org/jira/browse/TS-2781
        https://issues.apache.org/jira/browse/TS-910


this becomes completely crippling (it filled up our disks).


        
> 
>  the current ATS logging a ugly but very good in performance thinking log 
> system, the SAC is a dedicated commercial server to offer log collation 
> service, due to that we are now open sourced, that is a good idea removing 
> the duplicated SAC codes.  In our using with syslog-ng, it’s performance may 
> affect very busy ATS systems, that is why Yunkai pushed many collation 
> improvements.

No one has said anything about the logging infrastructure itself. In fact, I do 
not think it’s ugly, I think it’s very good. This has nothing to do with that, 
logging will work as it does.

> 
>  yes, logging has some ugly bugs, but collation should not that bad after 
> Yunkai’s work, and it does not bother you if you just logging to local disk 
> and collection with the other systems, right?


Yes, it did bother us, because the misbehavior around orphaned logs are 
crippling.

> 
>  please consider keep this feature, I am very happy that a simple collation 
> works for me out of box.
> 
>  sure you may find someone will take interest in supporting it, only if it is 
> still there.


So, I take it that 

1) You use this feature?

2) You will support this feature, and work on the code?



I could probably be convinced to give this feature another year “probation”, 
but only under the conditions that you answered “yes” to both questions above. 
If so, I’ll file a Jira on the biggest issue, that orphaned logs are abandoned 
with no way to get inserted again.


Anyone else have any thoughts on this?


— Leif

Reply via email to