wu-sheng commented on PR #9575: URL: https://github.com/apache/skywalking/pull/9575#issuecomment-1242032644
> The reason of this bug is the BINDING is ThreadLoacal and OAP parse two rules in one thread. I am confused about how to resolve it. May be we should use multiple threads to do these? @kezhenxu94 Any suggestion? This is an interesting bug, as we never have LAL used in this kind of complexity, This is a good and real scenario. From my understanding, this status should be able to override through `sink` and `slowSQL` functions. It is true that the previous LAL declared it is aborted unless other LAL declare to persistent. Meanwhile, if this log has been declared `sink`, then other's `abort` should not be able to override as the log should be persistent as declared. I want to confirm, is `slowSQL` declare the status? As slowSQL is just shipping the data into sources(OAL), the log should be `abort` as the final status. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
