Known installation issues.
During the Cloudera Data Science Workbench startup process, you might see certain timeout issues.
This is due to an issue with some pods taking longer to start up and other dependent processes timing out. Restart the CDSW service to get past this issue.
Pods not ready in cluster default ['role/<pod_name>'].
Cloudera Bug: DSE-6855
- Cloudera Data Science Workbench restricts a maximum of 50 concurrent Sessions, Jobs, Models, Applications, and Spark Executors that can run parallel by single users. You can use the Workers API to create additional pods which count toward the 50 limit.
- Cloudera Data Science Workbench cannot be managed by Apache Ambari.
- Apache Phoenix requires additional configuration to run commands successfully from
within Cloudera Data Science Workbench engines (sessions, jobs, experiments, models).
Workaround: Explicitly set HBASE_CONF_PATH to a valid path before running Phoenix