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

Why Is Customer Obsession Disappearing?

By
Many companies trade real customer-obsession for automated, low-empathy support. Through examples from Coinbase, PayPal, GO Telecommunications and AT&T, this article shows how reliance on AI chatbots, outsourced call centers, and KPI-driven workflows erodes trust, NPS and customer retention. It argues that human-centric support—treating support as strategic investment instead of cost—is still a core growth engine in competitive markets. It's wild that even with all the cool tech we've got these days, like AI solving complex equations and doing business across time zones in a flash, so many companies are still struggling with the basics: taking care of their customers. The drama around Coinbase's customer support is a prime example of even tech giants messing up. And it's not just Coinbase — it's a big-picture issue for the whole industry. At some point, the idea of "customer obsession" got replaced with "customer automation," and no...
Read more

How to scale MySQL perfectly

By
When MySQL reaches its limits, scaling cannot rely on hardware alone. This article explains how strategic techniques such as caching, sharding and operational optimisation can drastically reduce load and improve application responsiveness. It outlines how in-memory systems like Redis or Memcached offload repeated reads, how horizontal sharding mechanisms distribute data for massive scale, and how tools such as Vitess, ProxySQL and HAProxy support routing, failover and cluster management. The summary also highlights essential practices including query tuning, indexing, replication and connection management. Together these approaches form a modern DevOps strategy that transforms MySQL from a single bottleneck into a resilient, scalable data layer able to grow with your application. When your MySQL database reaches its performance limits, vertical scaling through hardware upgrades provides a temporary solution. Long-term growth, though, requires a more comprehensive approach. This invo...
Read more

What the Heck is Superposition and Entanglement?

By
This post is about superposition and interference in simple, intuitive terms. It describes how quantum states combine, how probability amplitudes add, and why interference patterns appear in systems such as electrons, photons and waves. The goal is to give a clear, non mathematical understanding of how quantum behavior emerges from the rules of wave functions and measurement. If you’ve ever heard the words superposition or entanglement thrown around in conversations about quantum physics, you may have nodded politely while your brain quietly filed them away in the "too confusing to deal with" folder.  These aren't just theoretical quirks; they're the foundation of mind-bending tech like Google's latest quantum chip, the Willow with its 105 qubits. Superposition challenges our understanding of reality, suggesting that particles don't have definite states until observed. This principle is crucial in quantum technologies, enabling phenomena like quantum comp...
Read more