Blog
Wawasan data & infrastruktur
Artikel teknis seputar database, infrastruktur, dan best practice dari tim SolusiDB.
-
Clear Systemd Journal Logs in Ubuntu 22.04
systemd uses its own logging system called the journal. It’s a centralized logging system that collects logs from all parts of the system, including the kernel, services, and applications. This makes it easier to manage and analyze logs. Here are some key things to know about the journal: Storage: By default, journal logs are+ Read More
Baca selengkapnya -
GlusterFS as Storage Domain for OLVM
Using GlusterFS as a storage domain for Oracle Linux Virtualization Manager (OLVM) offers several advantages, particularly in terms of scalability, high availability, and cost-effectiveness. Here’s a breakdown of how it works and its benefits: How it Works: GlusterFS Setup: You’ll need to set up a GlusterFS cluster, which involves multiple servers (at least 2-3 for+ Read More
Baca selengkapnya -
Oracle Linux Virtualization Manager (OLVM)
Oracle Linux Virtualization Manager (OLVM) is a powerful, open-source server virtualization management platform that simplifies the deployment, monitoring, and management of Kernel-based Virtual Machines (KVMs) in an Oracle Linux environment. It offers enterprise-grade performance and is fully supported by Oracle Key Features and Benefits: Open Source and Cost-Effective: OLVM is based on the open-source oVirt+ Read More
Baca selengkapnya -
Introduce GlusterFS
GlusterFS is an open-source, scalable, distributed file system designed to handle large amounts of data across multiple storage servers. Developed by Gluster Inc. (later acquired by Red Hat), GlusterFS is highly flexible and can be used for a variety of storage scenarios, including cloud storage, media streaming, and big data analytics. Key Features of GlusterFS+ Read More
Baca selengkapnya -
PostgreSQL – Memory Architecture
PostgreSQL’s memory architecture is designed to efficiently manage data access, ensure high performance, and optimize resource utilization. Here’s a detailed exploration of the various memory components and their roles within PostgreSQL: 1. Memory Categories PostgreSQL uses different types of memory areas for various purposes, broadly categorized as follows: Shared Memory: Used for inter-process communication and+ Read More
Baca selengkapnya -
PostgreSQL – Process Architecture
Understanding the various processes in PostgreSQL is crucial for optimizing performance, managing resources, and troubleshooting issues. PostgreSQL uses a multi-process architecture, where each connection is handled by a separate backend process. Here’s a deep dive into the key processes in PostgreSQL: 1. Postmaster Process Role: The main server process that is responsible for initializing the+ Read More
Baca selengkapnya -
Open Socket & Open Files in PostgreSQL
In the context of PostgreSQL (and operating systems in general), “open sockets” and “open files” refer to two different types of resources that are managed by the system. Here’s a detailed comparison: 1. Definition Open Sockets: Sockets are endpoints for communication between processes over a network. In PostgreSQL, they facilitate client-server communication, either over TCP/IP+ Read More
Baca selengkapnya -
Open Socket in PostgreSQL
Open sockets in PostgreSQL are essential for managing network connections between clients and the database server. Understanding how PostgreSQL handles sockets can help optimize performance, troubleshoot connection issues, and ensure secure communication. Here’s a comprehensive look at this topic: 1. What Are Sockets? A socket is an endpoint for sending and receiving data across a+ Read More
Baca selengkapnya -
Configurations in PostgreSQL for Heavy Read Workloads
Configuring PostgreSQL and the operating system for a heavy read workload involves optimizing various settings to improve performance, reduce latency, and ensure efficient resource utilization. Below are recommended configurations and best practices: PostgreSQL Configuration Memory Settings: shared_buffers: Allocate 25-40% of your system’s RAM. This is PostgreSQL’s primary memory cache for data. For example:shared_buffers = 8GBPurpose:+ Read More
Baca selengkapnya -
Configurations in PostgreSQL for Heavy Write Workloads
Optimizing PostgreSQL and the operating system for a heavy write workload involves careful tuning of both PostgreSQL settings and OS configurations. Here’s a concise guide to the best configurations: PostgreSQL Configuration Memory Settings: shared_buffers: Set 25-40% of total RAM. Purpose It stores frequently accessed data and index pages to reduce the need for disk+ Read More
Baca selengkapnya -
Calculating maximum connections in PostgreSQL
Calculating the maximum number of connections for a PostgreSQL server involves considering both the available RAM and CPU. Here’s a structured approach to help you determine an appropriate max_connections value based on your system’s resources. General Guidelines RAM Consideration: PostgreSQL uses memory for each connection, so the available RAM significantly affects the maximum number of+ Read More
Baca selengkapnya -
Open Files in PostgreSQL
Open file management in PostgreSQL is a crucial aspect of the database’s performance and stability. Each PostgreSQL backend process interacts with various files, including data files, indexes, WAL (Write-Ahead Log) files, and temporary files. Understanding how PostgreSQL handles open files helps in tuning the system and troubleshooting issues like “too many open files.” Here’s a+ Read More
Baca selengkapnya -
PostgreSQL Architecture
PostgreSQL is a powerful, open-source relational database management system (RDBMS) known for its robustness, extensibility, and standards compliance. Understanding its architecture is crucial for optimizing performance, ensuring reliability, and effectively managing databases. Here’s a deep dive into PostgreSQL architecture: 1. Overall Architecture PostgreSQL follows a client-server architecture, where the server process handles all database requests+ Read More
Baca selengkapnya -
PostgreSQL – Logical Replication – Overview
Pada PostgreSQL memiliki fitur replikasi, yang bertujuan untuk menjaga availability data yang kita miliki, meminimalisir resiko terjadinya kehilangan data yang di akibatkan oleh hardware failure, os crash dan lain sebagainya. Selain itu juga pada PostgreSQL replikasi juga berguna untuk membagi beban kerja dari server / instance database untuk meningkatkan performance aplikasi kita. Pada PostgreSQL memiliki+ Read More
Baca selengkapnya -
MongoDB best practices – 5. Replication best practices
Pada MongoDB telah memiliki fitur peplikasi, yang berguna untuk redudansi, high availability dan kemampuan high throughput. Berikut beberapa hal yang harus diperhatikan untuk replikasi MongoDB : Always use replica setsSekecil apapun data yang kita miliki, jika sudah memasuki environment productions, sebaiknya MongoDB di set replikasi, karena kita tidak pernah mengetahui apa yang akan terjadi dengan+ Read More
Baca selengkapnya -
MongoDB best practices – 4. Security best practices
Pada mongodb, memiliki fitur security untuk tetap menjaga keamanan database kita, berikut ini adalah beberapa rekomendasi yang harus dilakukan untuk menjaga data kita tetap secure: Enable Authentication HTTP Interface status harus di disable RESTful API harus di disable JSON API harus di disable Koneksi atau komunikasi ke MongoDB menggunakan SSL Mengaktifkan Audit log untuk semua+ Read More
Baca selengkapnya -
MongoDB best practices – 3. Write durability best practices
Pada mongodb proses penulisan dan durability dapat kita atur dengan baik agar tidak mengurangi performance dari aplikasi yang kita miliki. Contohnya adalah pengaturan data flush ke Disk pada WiredTiger storage engine, defaultnya adalah 60 detik setelah checkpoint terakhir atau setelah 2G data di tulis. Variable tersebut dapat di ubah dengan mengganti nilai wiredTigerCheckpointDelaySecs. Atau jika+ Read More
Baca selengkapnya -
MongoDB best practices – 2. Schema design best practices
Mongodb adalah schema less tidak seperti DBMS yang memiliki struktur table. Yang dilakukan terhadap mongodb adalah hanya membuat collections dan Indexing. Berikut beberapa tipsnya: Use the appropriate storage enginePada mongodb memiliki storage engine berupa WiredTiger (mulai mongodb 3.2) , MMAPv1 (di remove pada versi 4.2) dan In-Memory Storage Engine (pada mongodb enterprise). Indexing EarlyPada saat+ Read More
Baca selengkapnya -
MongoDB best practices – 1. Operational best practices
Enable JournalingJournaling menggunakan WAL (write-ahead log) file untuk dapat menjaga integrity data ketika database kita mengalami crash atau mati secara tiba-tiba, maka secara otomatis data akan di recover. Pada type storage engine MMAPv1, secara default Journaling akan enable. Sedangkan pada type storage engine WiredTiger journaling dan check point digunakan secara bersamaan untuk memastikan durability Data.+ Read More
Baca selengkapnya -
Swiss Army knife for managing PostgreSQL
The following are some commands commonly used by DBAs as tools for checking PostgreSQL databases Uptime service PostgreSQL SELECT (now() – pg_postmaster_start_time()) as Uptime; List Current Process select pid as PROCESS_ID, usename as USER, datname as DATABASE, client_addr as HOST, application_name as APP_NAME, backend_start as STARTED_AT, state as STATE from pg_stat_activity; Count Current Process select+ Read More
Baca selengkapnya -
Upgrade MySQL-5.7 to MariaDB-10.2 Galera
Scenario Existing server -DB: MySQL-5.7 Master-slave, DB size: 140GB New Server – DB = MariaDB-10.2 (Galera Cluster) Following are the steps that must be done to migrate and upgrade MySQL-5.7 to MariaDB-10.2 Stop the mysql service on the MySQL-5.7 server # service mysql stop Copy the full directory / var / lib / mysql or+ Read More
Baca selengkapnya -
Setup Maxscale HA using Keepalived and Maxctrl
MariaDB MaxScale is a database proxy which does load balancing and query routing from client applications to backend database servers. In a basic configuration, MaxScale is a single point of failure. In this blog post we show how to setup a more resilient MaxScale HA cluster using Keepalived and MaxCtrl. Keepalived is a routing software+ Read More
Baca selengkapnya -
Install MongoDB on CentOS-7.x (64bit)
Configure the package management system (yum). Create a /etc/yum.repos.d/mongodb-org-4.0.repo file so that you can install MongoDB directly using yum: # vi /etc/yum.repos.d/mongodb-org-4.0.repo name=MongoDB Repository baseurl=https://repo.mongodb.org/yum/redhat/$releasever/mongodb-org/4.0/x86_64/ gpgcheck=1 enabled=1 gpgkey=https://www.mongodb.org/static/pgp/server-4.0.asc Disable SeLinux. # vi /etc/sysconfig/selinux #This file controls the state of SELinux on the system.#SELINUX= can take one of these three values:#enforcing – SELinux security policy is+ Read More
Baca selengkapnya -
New MariaDB Platform Launches in the Cloud
MariaDB is releasing MariaDB Platform X3, an open source database that unites transactional and analytical workloads at scale, and introducing a new MariaDB Managed Service supporting public and hybrid cloud deployments. “Public cloud service offerings have fallen short in helping companies succeed across their diverse cloud and on-prem environments,” said Michael Howard, CEO, MariaDB Corporation.+ Read More
Baca selengkapnya