Skip to main content

Don’t Put Hadoop or HBase Temp Directories in /tmp: Protecting Your Metadata

By Anonymous
Struggling with delivery, architecture alignment, or platform stability?

I help teams fix systemic engineering issues: processes, architecture, and clarity.
→ See how I work with teams.


Many early Hadoop installations lost HDFS metadata because temporary directories were left under /tmp, which is routinely cleaned by Linux on reboot. This article explains why hadoop.tmp.dir and hbase.tmp.dir must point to a stable path, how this impacts NameNode edit logs and checkpoints, and what a safe configuration looks like today for both Hadoop and HBase clusters.

In early Hadoop 0.20 clusters, it was common to leave the default hadoop.tmp.dir configuration unchanged. On many Linux systems, however, /tmp is automatically cleaned during reboot. If your Hadoop or HBase temp directories live there, you risk losing critical metadata when the operating system wipes that directory.

For the SecondaryNameNode and related components, this can mean the loss of:

  • Recent edit logs
  • Checkpointed fsimage files
  • Other temporary metadata needed for recovery

If these files are removed, the NameNode may not be able to replay its edits after a crash, leading to a failed restart or a painful recovery process.

Configuring a Safe hadoop.tmp.dir

The first step is to move hadoop.tmp.dir to a stable location outside /tmp. Use a path on a persistent filesystem with enough capacity and proper backup or snapshot policies.

Example entry for core-site.xml: 

<property> <name>hadoop.tmp.dir</name> <value>/var/lib/hadoop/tmp/${user.name}</value> </property>

You can choose any appropriate base directory, such as:

  • /var/lib/hadoop/tmp
  • /data1/hadoop/tmp
  • A dedicated mount attached to your storage system

After updating the configuration, restart the SecondaryNameNode (and other Hadoop daemons as required) so they start using the new, persistent location.

Configuring a Safe hbase.tmp.dir

The same principle applies to HBase. Leaving hbase.tmp.dir under /tmp is risky for cluster stability. Update hbase-site.xml with a persistent path: 

<property> <name>hbase.tmp.dir</name> <value>/var/lib/hbase/tmp/${user.name}</value> </property>

Again, choose a directory on durable storage with sufficient capacity. Restart your HBase services after the change so they use the new locations.

Modern Perspective: Still Relevant?

Even with modern Hadoop distributions, NameNode HA, and cloud-based storage, the core idea remains important:

  • Avoid storing any critical metadata or temp data on ephemeral locations that OS tools or init scripts may wipe.
  • Ensure that temp directories used by Hadoop and HBase live on stable volumes.
  • Monitor disk usage and include these paths in your backup or snapshot strategy where appropriate.

Misconfigured temp directories are still a surprisingly common source of metadata loss, especially in test or ad-hoc clusters that later grow into production-critical systems.

By moving hadoop.tmp.dir and hbase.tmp.dir away from /tmp, you significantly reduce the risk of losing checkpoints, edit logs or other files required for a clean restart after a crash or reboot.

Related guides:

If you need help with distributed systems, backend engineering, or data platforms, check my Services.

Labels:

Most read articles

Building a Model-Agnostic Multi-Agent System with OpenClaw

By
Over one week we rebuilt our AI stack around OpenClaw’s multi-agent architecture to avoid provider lock-in and stop wasting premium tokens. By aligning models to tasks, diversifying fallbacks across providers, enforcing minimal tool access, and switching to memory-first workflows with ephemeral sessions, we reduced token usage per task by about 70% and cut our monthly bill by 77% while improving operational resilience. How We Achieved 77% Cost Reduction and Provider Independence Over the past week, we rebuilt our AI infrastructure around OpenClaw’s multi-agent architecture. The result was a 77% cost reduction , provider independence , and a delegation system that routes work to the most cost-effective model for each job. Below is the technical journey of optimizing a 7-agent squad with OpenClaw. The Challenge: Model Provider Lock-In We started with a simple problem: our entire squad defaulted to a single model provider. This created three issues: Cost inefficiency beca...
Read more

BacNet => MQTT in Production: The Real Cost of Bridging BACnet to MQTT at Scale

By
bacnet2mqtt looks simple in a README and expensive in production. Once BACnet polling, reconnection behavior, stale state, and MQTT publishing collide, teams discover they are not deploying a lightweight adapter but operating infrastructure. This article breaks down where bacnet2mqtt works, where it becomes a bottleneck, and which production patterns reduce the operational damage before incidents, backlogs, and silent data loss turn a building integration into a long-running engineering problem. I inherited a building controls integration problem 18 months ago. Three office floors. 217 BACnet sensors covering temperature, occupancy, and HVAC actuators. The data was trapped inside the building automation network while the business wanted analytics, reporting, and compliance visibility in the data platform. The obvious answer looked easy enough: deploy bacnet2mqtt, bridge BACnet into MQTT, and push the stream into the lakehouse stack. The repository made it sound like a w...
Read more

Connect BACnet to the Cloud with bacnet-mqtt-gateway

By
The bacnet-mqtt-gateway project is an open source protocol bridge that translates BACnet building automation traffic into MQTT messages for cloud and IoT systems. It provides discovery, polling, bidirectional writes, APIs, security, and easy deployment via Docker. Many enterprises struggle to unify BACnet with modern data pipelines and cloud platforms because BACnet is local-network only and not cloud ready. This gateway provides a scalable, secure, production-ready adapter for MQTT ecosystems and smart building integrations. The Problem with BACnet Building automation runs on BACnet . HVAC controllers, lighting systems, metering equipment: they all speak ASHRAE 135 . The protocol handles local control loops well. It fails at cloud ingress. BACnet relies on UDP broadcasts. These do not route over the internet or into VPCs. Your chiller controller cannot talk to AWS IoT Core . Your VAV box cannot publish to an MQTT broker. The air gap between operational technology and modern cl...
Read more