About vina

csguna · ‎07-21-2017

As pointed mostly like it will be the resource allocation on those parameter good that you found it in that thread .I was close to narrow it down . Guess what sometimes it could be some socket configuration on the OS too . The logs will clearly guide us to it .

Shafiullah · ‎06-05-2017

Hi, I have to delete that node from azure. then Cloudera was not able to find it and i was able to stop and delete the service. Earlier i only stopped that node in Azure. Somehow it still was able to attached to it. Anyhow, that node was of no use so i deleted it. I was able to move the Activity monitor to different host by creating the database for it. Also, the de-commissioning and deletion of host is also done from cluster. The parcel distribution is also fine now.

SACHINICHAKE09 · ‎06-20-2016

yeah... its working.. i was able to find out its hex value (its control-v + control-a) character but was not applying '$' symbol. Thank you so much .. 🙂 really appreciated..

clouderazone · ‎05-23-2016

Yes the link was helpful. As per the property "dfs.datanode.du.reserved", it was configured to use 4.25 GB and hence I consider now that 4.25 GB is allocated for each data directory in a given node. Since I had two data directory partitions, the reserved space combined would be 8.5 GB per node and which brings the configured capacity on each node to be 23.5 GB (32GB - 8.5GB). I arrived at the following formula === > Configured Capacity = Total Disk Space allocated for Data Directories (dfs.data.dir) - Reserved Space for Non DFS Use (dfs.datanode.du.reserved)

Online	Offline
Last Visited	‎02-04-2021 10:28 AM

Member Since	‎01-08-2016 02:11 AM
Last Visited	‎02-04-2021 10:28 AM
Posts	22
Kudos received	1

Cloudera Community

Re: "Configured Capacity" shows less size than the...

Re: jpb submitted to mapreduce in Yarn is stuck wh...

Re: Activity monitor Issue

Re: how to export file which field delimited by "^...

Re: "Configured Capacity" shows less size than the...