StarRocks Is Not Enterprise Ready

It appears that your document is an in-depth technical assessment of StarRocks' database system, focusing on its reliability and performance issues. The analysis highlights several critical problems:

1. Memory Management Issues:

   • BE nodes frequently crash due to out-of-memory (OOM) errors.
   • Memory tracking is unreliable; reported memory usage can be vastly inaccurate.
   • Compaction tasks can enter infinite retry loops, causing system instability.

2. Query Result Integrity Problems:

   • Iceberg cache serves stale data without any error or warning.
   • Arrow Flight silently drops rows from results under certain conditions.
   • Non-deterministic functions like RAND() are incorrectly pushed down, leading to empty result sets.

3. Real-Time Ingestion Reliability Issues:

   • StreamLoad operations can freeze the entire cluster.
   • Flink connector fails with HTTP 404 errors upon pipeline restarts in shared-data mode.
   • Kafka Connect jobs get stuck in transaction states for extended periods, causing delays.
   • INSERT performance degrades significantly as tables grow.

4. Query Performance Instability:

   • Cost-Based Optimizer (CBO) selects inefficient plans when statistics are stale or inaccurate.

Read the full article at DEV Community

---

Want to create content about this topic? Use Nemati AI tools to generate articles, social posts, and more.