Solutions to Common Problems
Problems |
Possible Causes |
Solutions |
---|---|---|
Logs include APPARENT DEADLOCK entries for c3p0. |
These deadlock messages are cause by the c3p0 process not making progress at the expected rate. This can indicate either that c3p0 is deadlocked or that its progress is slow enough to trigger these messages. In many cases, progress is occurring and these messages should not be seen as catastrophic. |
There are a variety of ways to react to these log entries.
|
Starting Services |
||
After you click the Start button to start a service, the Finished status doesn't display. |
The host machine is disconnected from the Server, as indicated by missing heartbeats on the Hosts tab. |
|
After you click Start to start a service, the Finished status displays but there are error messages. The subcommands to start service components (such as JobTracker and one or more TaskTrackers) do not start. |
A port specified in the Configuration tab of the service is already being used in your cluster. For example, the JobTracker port is in use by another process. |
Enter an available port number in the port property (such as JobTracker port) in the Configuration tab of the service. |
There are incorrect directories specified in the Configuration tab of the service (such as the log directory). |
Enter correct directories in the Configuration tab of the service. |