[
https://issues.apache.org/jira/browse/HDDS-10041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tsz-wo Sze updated HDDS-10041:
------------------------------
Description:
It is generally a bad practice to start a thread inside a constructor; see
[https://stackoverflow.com/questions/11834173/why-shouldnt-i-use-thread-start-in-the-constructor-of-my-class]
Also, quite a few tests (such as TestOzoneManagerDoubleBuffer) has to stop the
daemon in order to eliminate the race condition in the very beginning.
was:
It is generally a bad practice to start a thread inside a constructor; see
https://stackoverflow.com/questions/11834173/why-shouldnt-i-use-thread-start-in-the-constructor-of-my-class
Also, quite a few tests (such as TestOzoneManagerDoubleBuffer) has to stop the
daemon till to eliminate the race condition in the very beginning.
> Do not start the daemon inside the OzoneManagerDoubleBuffer constructor
> -----------------------------------------------------------------------
>
> Key: HDDS-10041
> URL: https://issues.apache.org/jira/browse/HDDS-10041
> Project: Apache Ozone
> Issue Type: Sub-task
> Components: OM
> Reporter: Tsz-wo Sze
> Assignee: Tsz-wo Sze
> Priority: Major
>
> It is generally a bad practice to start a thread inside a constructor; see
> [https://stackoverflow.com/questions/11834173/why-shouldnt-i-use-thread-start-in-the-constructor-of-my-class]
> Also, quite a few tests (such as TestOzoneManagerDoubleBuffer) has to stop
> the daemon in order to eliminate the race condition in the very beginning.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
