Rohith, Thanks for starting a useful discussion. +1 for using tools for deadlock detection.
Before starting to use new tools, I'd like to mention findbugs: I think it's useful to enable findbugs to check IS2_INCONSISTENT_SYNC. There are lots exclusion of the rule in findbugs-exclusion.xml. I think some deadlock we faced could be prevented with the check. About the dynamic checker, it's useful to use it. One technical problem we will have is how to use it. Can we add the test with JCarder? Thanks, - Tsuyoshi On Wed, Dec 24, 2014 at 7:34 PM, Rohith Sharma K S <[email protected]> wrote: > > Hi folks, > > Recently in YARN project(last 1 year), there 12 deadlock issues or potential > deadlock issues were detected and fixed too. And many more might be there > also!! > > As going further in production ready releases, point of concern is, avoiding > these type of issues that may appear in the production deployment which would > cause severe impact and loss. So if there would be any tool integrated to > HadoopQA by default which identifies suspicious deadlock cycles like JCarder, > then it would be great in identifying issues in earlier stages rather than > issue reporting after release deploy in cluster. > > Any thought or suggestions on this? > > Thanks & Regards > Rohith Sharma K S > > This e-mail and its attachments contain confidential information from HUAWEI, > which is intended only for the person or entity whose address is listed > above. Any use of the information contained herein in any way (including, but > not limited to, total or partial disclosure, reproduction, or dissemination) > by persons other than the intended recipient(s) is prohibited. If you receive > this e-mail in error, please notify the sender by phone or email immediately > and delete it! >
