Database Reference
In-Depth Information
Listing 12-1.
Node re-imaging status entries
11/10/2013 12:45:20 PM +00:00,11/10/2013 12:44:39 PM +00:00,
xxxxxxxxxxxxxxxxxxxxxxxxxx,IsotopeWorkerNode,IsotopeWorkerNode_IN_1,4,
xxxxxxxxxxxxxxxxxx,2224,1020,SetupLogEntryEvent,1002,Info,null,MdsLogger,ClusterSetup,
Microsoft.Hadoop.Deployment.Engine,Azure reimaging state: 3 - REIMAGE_DATA_LOSS:
Services do not exist; Java directory does not exist.
Fresh installation.,1.0.0.0,xxxxxxxxxxxxxxxx,xxxxxxxxxxxxxx,False,null,null,null,
null,null,2013/11/10 12:44:39.480,Diagnostics,0000000000000000000,
0000000055834815115, 11/10/2013 12:44:00 PM +00:00
If there are any errors while deploying the Apache components or the services, due to some race condition while
accessing the file system, you may see log entries in this file similar to Listing 12-2.
Listing 12-2.
Error during deployment
Diagnostics Information: 1001 : OrigTS : 2013/07/20 21:47:21.109; EventId : 1002;
TraceLevel : Info; DeploymentEnvironment : ; ClassName : MdsLogger;
Component : ClusterSetup; ComponentAction : Microsoft.Hadoop.Deployment.Engine;
Details : Manually taking the backup off all files as the directory rename failed with exception
System.IO.IOException: The process cannot access the file because it is being used by another process.
at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.Directory.Move(String sourceDirName, String destDirName)
at Microsoft.Hadoop.Deployment.Engine.Commands.AzureBeforeHadoopInstallCommand
.Execute(DeploymentContext deploymentContext, INodeStore nodeStore); Version : 1.0.0.0;
ActivityId : 8f270dd7-4691-4a69-945f-e0a1a81605c1; AzureVMName : RD00155D6135E3;
IsException : False; ExceptionType : ; ExceptionMessage : ; InnerExceptionType : ;
InnerExceptionMessage : ; Exception : ;
You may also come across scenarios where the cluster-creation process completes but you don't see the packages
that should have been deployed to the nodes in place. For example, the cluster deployment is done but you don't
find Hive installed in the
C:\Apps\Dist\
directory. These installer and deployment logs could give you some insight
if something went wrong after VM provisioning. In most of these cases, re-creating the cluster is the easiest and
recommended solution.
For the HDInsight emulator, the same pair of deployment logs is generated, but in a different directory. They can
be found in the
C:\HadoopInstallFiles\
directory as shown in Figure
12-1
.
Figure 12-1.
HadoopInstallFiles directory
