StarRocks tanlayapsizmi?
Avval bu risklarni tekshiring.
Biz StarRocks ochiq GitHub issues, release notes va field reports-ini oʼrgandik. Mana topganlarimiz — manbalar bilan.
> source: github.com/StarRocks/starrocks
> source: docs.starrocks.io/releasenotes
> source: community field reports
> yanked: 3.3.1, 3.3.10, 3.4.1
> open: #67760, #72036, #53472
> warning: DO NOT downgrade 4.0→3.5.0
> warning: DO NOT downgrade 3.3→3.2.0-3.2.2
> RECOMMENDATION: run production-risk POC
STARROCKS OCHIQ MUAMMOLARI
// github.com/StarRocks/starrocks/issues
Metadata loss: 3.3.10 va 3.4.1 release-lar qaytarildi
StarRocks-ning ikki minor release-i FE Leader almashuvida metadata yoʼqolishi sababli nashrdan olib tashlandi.
Iceberg-da FE OOM: issue #67760 (ochiq)
6.6M partitsiyali Iceberg katalogida Frontend hammasini xotiraga yuklaydi. Natija: 20GB+ heap, crash.
Import vaqtida versiya yoʼqolishi: PR #59006
Clone/decommission sikllari replikalarning versiyalarni oʼtkazib yuborishiga olib keldi.
RocksDB meta buzilishi: issue #72036 (ochiq)
Storage migratsiyasida RocksDB "out-of-order keys" xatosini chiqaradi, BE crash.
CSV importda qatorlar yoʼqolishi: issue #53472 (ochiq)
64MB+ CSV fayllarni skip_header bilan yuklashda deterministik qator yoʼqolishi.
Stream Load vaqtida CN OOM: field report
270 parallel Stream Loads 3 CN-da OOM, broken pipe va toʼliq toʼxtashga olib keldi.
Upgrade vaqtida delete-vector CRC xatolari: PR #65354
ABA upgrade/downgrade (3.4→4.0→3.4) ssenariyida CRC32 validatsiyasi buziladi.
UNION rewrite → FE OOM: PR #59030
Query planner bagi: UNION qayta yozish cheksiz boʼsh qatorlar generatsiya qildi, FE OOM bilan qulab tushdi.
NEGA VELODB — PRODUCTION UCHUN XAVFSIZROQ
// velodb.io + doris.apache.org
Apache 2.0 — litsenziya riskisiz
StarRocks Elastic License 2.0 managed-service cheklovlari bilan. Doris/VeloDB — Apache 2.0, cheklovsiz.
Workload isolation tayyor
Doris Workload Groups mixed read/write workloads uchun CPU/IO izolyatsiya beradi.
CDC/Flink — production-ready yoʼl
VeloDB Flink Connector exactly-once, group commit va whole-database sync qoʼllaydi.
Markaziy Osiyodagi lokal hamkor
Datanomix — KZ va UZ-dagi VeloDB eksklyuziv hamkori. Audit, pilot, on-prem/BYOC.
FAQ
// faq.jsonld
Bu StarRocks-ga qarshi reklama emasmi?
Yoʼq. Barcha maʼlumotlar ochiq GitHub issues va rasmiy release notes-dan. Bu risklarni tanlov oldidan bilish kerak.
StarRocks qachon yaxshi tanlov?
Sof OLAP workload, kuchli platform-jamoa, aniq upgrade-strategiya boʼlganda.
Nega Apache Doris emas, VeloDB?
Apache Doris — open-source. VeloDB enterprise support + Datanomix Markaziy Osiyodagi hamkor qoʼshadi.
Pilotga nima kiradi?
Stek audit, VeloDB deploy, latency oʼlchash, CDC-test, taqqosiy hisobot. Tekin, 2 hafta.
2 haftada tekin VeloDB piloti
Maʼlumotlaringizga ulaymiz, farqni koʼrsatamiz.