Answer-first summary for fast verification
Answer: Investigate the cause of the memory leak by reviewing the application logs and code, apply necessary fixes to the code, and then restart the cluster to ensure the fixes are effective and to clear any residual issues.
The best course of action is to investigate the cause of the memory leak, as this approach addresses the root cause of the issue, preventing future occurrences. After identifying and fixing the issue in the code, restarting the cluster ensures that the fixes are applied and any residual issues are cleared. This method balances the need for a quick resolution with the importance of a thorough investigation to prevent recurrence. Option A is not ideal because it does not address the underlying cause of the memory leak. Option C is not recommended as it allows the performance issues to persist, potentially worsening the situation. Option D is ineffective because it does not resolve the root cause of the memory leak, likely leading to the same issues reoccurring.
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
In a scenario where a Databricks cluster is experiencing performance issues due to a memory leak, and the team is under pressure to minimize downtime while ensuring the issue is thoroughly resolved, what is the BEST course of action? Consider the need for quick resolution, the importance of identifying the root cause to prevent recurrence, and the impact on ongoing data processing tasks. Choose the most appropriate option from the following:
A
Immediately restart the cluster to quickly resolve the performance issues without any investigation, as this is the fastest way to restore functionality.
B
Investigate the cause of the memory leak by reviewing the application logs and code, apply necessary fixes to the code, and then restart the cluster to ensure the fixes are effective and to clear any residual issues.
C
Continue running the cluster as is, monitoring the situation closely, but take no immediate action to avoid any disruption to ongoing processes.
D
Restart the cluster and immediately rerun the same jobs without any changes, assuming the restart will permanently resolve the memory leak issue.
No comments yet.