Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Saat membuat layanan Dataproc Metastore, Anda dapat memilih untuk menggunakan
layanan Dataproc Metastore 2 atau layanan Dataproc Metastore 1.
Dokumen ini menjelaskan cara mengontrol pemakaian resource untuk
Dataproc Metastore 1.
Jenis tingkat layanan
Dataproc Metastore menggunakan tingkat layanan untuk menangani berbagai tingkat
stabilitas dan workload. Anda dapat memilih paket layanan saat membuat layanan
Dataproc Metastore. Anda juga dapat mengubah tingkat layanan
layanan yang ada.
Ada dua jenis tingkat layanan:
Developer: Tingkat Developer biasanya digunakan untuk produksi untuk
project bukti konsep berbiaya rendah. Paket ini memberikan skalabilitas terbatas
dan tidak ada fault-tolerance.
Enterprise: Tingkat Enterprise biasanya digunakan untuk project
produksi. Paket ini memberikan skalabilitas yang fleksibel, fault tolerance, dan ketersediaan tinggi multi-zona. Paket ini dapat menangani workload Dataproc Metastore yang berat.
Secara default, layanan Dataproc Metastore baru dibuat dengan tingkat Developer.
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Sulit dipahami","hardToUnderstand","thumb-down"],["Informasi atau kode contoh salah","incorrectInformationOrSampleCode","thumb-down"],["Informasi/contoh yang saya butuhkan tidak ada","missingTheInformationSamplesINeed","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2025-08-27 UTC."],[[["\u003cp\u003eDataproc Metastore offers two service versions, Metastore 1 and Metastore 2, allowing you to choose the appropriate version when creating a service.\u003c/p\u003e\n"],["\u003cp\u003eDataproc Metastore 1 has service tiers, which are \u003ccode\u003eDeveloper\u003c/code\u003e for low-cost proof-of-concept projects with limited scalability and no fault tolerance and \u003ccode\u003eEnterprise\u003c/code\u003e for production projects with scalability, fault tolerance, and high availability.\u003c/p\u003e\n"],["\u003cp\u003eYou can select or change the service tier when creating or modifying a Dataproc Metastore service.\u003c/p\u003e\n"],["\u003cp\u003eNew Dataproc Metastore services default to the \u003ccode\u003eDeveloper\u003c/code\u003e tier.\u003c/p\u003e\n"]]],[],null,["# Dataproc Metastore service tiers\n\nWhen you create a Dataproc Metastore service, you can choose to use\na *Dataproc Metastore 2 service* or a *Dataproc Metastore 1\nservice*.\n\nThis document explains how to control resource consumption for\nDataproc Metastore 1.\n\nTypes of service tiers\n----------------------\n\nDataproc Metastore uses service tiers to handle varying levels of\nstability and workloads. You can select the service tier when you create a\nDataproc Metastore service. You can also change the service tier of\nan existing service.\n\nThere are two types of service tiers:\n\n- **Developer** : The `Developer` tier is typically used for production for\n low-cost proof-of-concept projects. This tier provides limited scalability\n and no fault tolerance.\n\n- **Enterprise** : The `Enterprise` tier is typically used for production\n projects. This tier provides flexible scalability, fault tolerance,\n and multi-zone high availability. It can handle heavy Dataproc Metastore workloads.\n\nBy default, new Dataproc Metastore services are created with the\n`Developer` tier.\n\nWhat's next\n-----------\n\n- [Create a service](/dataproc-metastore/docs/create-service)\n- [Release notes](/dataproc-metastore/docs/release-notes)\n- [Version policy](/dataproc-metastore/docs/version-policy)"]]
