Skip to main content

Fixing Hive “Too Many Counters” MapReduce Failures

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.


When Hive queries use many operators, MapReduce can hit its default counter limit and fail with a “Too many counters” exception. This short note explains why it happens (Hive creates multiple counters per operator), how to raise mapreduce.job.counters.max safely, and how to estimate how many operators your query uses with EXPLAIN so you can tune the setting without guessing.

Symptom

A Hive job fails with an error like: 

Ended Job = job_xxxxxx with exception
'org.apache.hadoop.mapreduce.counters.LimitExceededException
 (Too many counters: 201 max=200)'
FAILED: Execution Error, return code 1 from org.apache.hadoop.hive.ql.exec.MapRedTask
Intercepting System.exit(1)

The query might be complex, but otherwise looks syntactically fine. The problem is not your SQL, it’s the number of counters that MapReduce is willing to track.

Why this happens: operators and counters

Hive uses counters to track statistics for built-in operators (see the Hive LanguageManual UDF / operators documentation). For each operator, Hive can create multiple counters; historically this was around four counters per operator.

On top of that, a MapReduce job has its own counters for:

  • Input / output bytes and records
  • Tables, partitions, files
  • Custom job- and framework-level metrics

The default maximum number of counters in classic MapReduce was relatively low (for example, 200), so a sufficiently complex query with many operators could exceed this limit and trigger a LimitExceededException.

The fix: raise mapreduce.job.counters.max

To avoid this exception, increase the maximum number of counters allowed per job by setting: 

<property>
  <name>mapreduce.job.counters.max</name>
  <value>1120</value>
</property>

Add this to mapreduce-site.xml (or the equivalent config for your distribution) and restart the relevant services so Hive and MapReduce pick up the new setting.

A value slightly above 1000 is often enough for complex Hive queries while still keeping memory overhead manageable. You can adjust this based on your query patterns and any additional counters used by your environment.

Estimating how many counters you need

The number of counters required is roughly proportional to the number of operators used in the query. A simple way to get a sense of this is:

  1. Run EXPLAIN EXTENDED on your query to see the full operator tree.
  2. Search for “operator” lines in the explain output and count them.

Example workflow:

hive> EXPLAIN EXTENDED <your_query> > explain.out

grep -ri "operator" explain.out | wc -l

This gives you a rough count of operators. Multiply by the number of counters per operator (historically ~4) and add some headroom for framework counters to decide how high you should set mapreduce.job.counters.max.

Impact on other MapReduce jobs

Raising mapreduce.job.counters.max:

  • Prevents Hive jobs from failing as they approach the previous counter limit.
  • Does not break other MapReduce jobs, but they can now allocate more counters if needed.
  • Has a small memory and bookkeeping cost per additional counter; keep the value reasonable and not arbitrarily huge.

If you see the “Too many counters” error, adjusting this single setting is usually enough to unblock Hive while keeping your MapReduce cluster stable.

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