In HBase, the "memory to disk" flush operation

In HBase, the "memory to disk" flush operation (or "memstore flush") happens when data in the memstore (in-memory storage) is flushed to disk as HFiles in HDFS. This flush can occur based on multiple triggers rather than a strict time interval, including:

  1. Memstore Size Limit: The primary trigger is when the size of the memstore reaches a defined threshold. The default maximum memstore size per RegionServer is set by the configuration parameter hbase.regionserver.global.memstore.size, typically as a fraction of the total heap size. When the memstore fills up, it triggers an automatic flush to disk.

  2. Time-Based Flush (Optional): Although time-based flushes are not the main flush trigger, HBase provides an optional parameter for a maximum delay, which can ensure that data gets written to disk within a certain time, even if the memstore size limit hasn't been reached. This parameter is:

    • hbase.hregion.memstore.flush.period: This sets the maximum time (in milliseconds) that data can stay in memory before it must be flushed to disk. By default, this is set to 0 (disabled), meaning there is no strict time limit, and only the memstore size triggers the flush. If enabled, it will enforce a flush after the specified time, regardless of the memstore size.

    For example:

    hbase.hregion.memstore.flush.period=3600000  # Flush after 1 hour

  3. Manual Flush: You can also manually flush data by calling flush() on a table or RegionServer using the HBase shell or API. This is useful in certain situations for performance tuning or maintenance.

Best Practice

Leaving hbase.hregion.memstore.flush.period disabled (the default) generally provides optimal performance, as HBase will flush based on memory thresholds instead of time, which is often more efficient. However, in scenarios where you want to ensure data persistence on disk more frequently (such as during a heavy load with risk of data loss in case of crashes), you can configure this parameter to enforce a periodic flush.

댓글

댓글 쓰기

이 블로그의 인기 게시물

Using the MinIO API via curl

Using the MinIO API via curl is straightforward, as MinIO is compatible with Amazon S3 API, so most commands follow a similar syntax. Here’s a guide on how to use curl with the MinIO API for some common operations like uploading, downloading, and managing objects. Prerequisites Access Key and Secret Key : Obtain your MinIO Access Key and Secret Key. MinIO Endpoint : Know your MinIO server endpoint, e.g., http://localhost:9000 . Bucket : You may need an existing bucket name, or create a new one using the commands below. Authentication Header For requests to work with MinIO, you need to include authentication in the headers. MinIO uses AWS Signature Version 4 for signing requests. Common Examples 1. List Buckets To list all buckets in your MinIO account, use: curl -X GET \ - -url "http://localhost:9000/" \ - H "Authorization: AWS <AccessKey>:<Signature>" 2. Create a Bucket To create a new bucket, use: curl -X PUT \ - -url "htt...
자세한 내용 보기

How to checkout branch of remote git, 깃 리모트 브랜치 체크아웃

To check out a branch from a remote Git repository, you can follow these steps: 1. Fetch the remote branches First, ensure that your local repository is aware of the remote branches by using git fetch . This updates your local references to the remote branches. git fetch origin 2. Check out the remote branch Once the remote branches are fetched, you can check out the desired branch using git checkout -b and specifying the remote branch. Command: git checkout -b < local -branch- name > origin/<remote-branch- name > Explanation: <local-branch-name> : The name you want to give to your local branch. origin/<remote-branch-name> : Refers to the branch on the remote called origin (which is the default name for the main remote repository) and the branch you want to check out. Example: If the remote branch is called feature-branch and you want to create a local branch with the same name, you would run: git checkout -b feature -branch origin / feature -...
자세한 내용 보기

PySpark Dataframe from HBase

To filter data from HBase and write it back using PySpark, follow these steps: Read data from HBase into a PySpark DataFrame. Filter the DataFrame using PySpark transformations. Write the filtered DataFrame to your desired format (e.g., HBase, Parquet, CSV, etc.). Below is the complete example covering these tasks. 1. Reading, Filtering, and Writing Data Step-by-Step Code from pyspark.sql import SparkSession from pyspark.sql.functions import col # Step 1: Initialize Spark Session with HBase Configurations spark = SparkSession.builder \ .appName( "HBase-PySpark Read-Write" ) \ .config( "spark.jars" , "/path/to/hbase-client.jar,/path/to/hadoop-common.jar" ) \ .config( "spark.hadoop.hbase.zookeeper.quorum" , "localhost" ) \ .config( "spark.hadoop.hbase.zookeeper.property.clientPort" , "2181" ) \ .getOrCreate() # Step 2: Define the HBase Table Catalog hbase_table = "my_table...
자세한 내용 보기

how to delete all issues on project in sentry, 센트리 이슈 삭제하기

As of now, Sentry doesn't have a direct feature to delete all issues in bulk through the web interface. However, there are a few methods you can use to archive, resolve, or delete issues programmatically or by adjusting project settings: 1. Bulk Archive Issues from the Web Interface Though there is no mass delete option, you can bulk archive or resolve issues, which essentially hides them from active issue lists. Steps: Go to your Sentry project. In the issue list view, select the issues you want to archive or resolve. Use the "Select All" checkbox to select multiple issues. Choose "Resolve" or "Archive" from the bulk action dropdown. However, this doesn't delete the issues permanently; they will be archived or marked as resolved. 2. Adjust Retention Policy (Data Retention Settings) If you're looking to remove older issues, you can adjust the retention policy at the organization level. Sentry allows you to configure how long issue...
자세한 내용 보기

Create topic on Kafka with partition count, 카프카 토픽 생성하기

To create a Kafka topic with 100 partitions, you can use the Kafka command-line tool ( kafka-topics.sh or kafka-topics.bat for Windows). When creating a topic, you can specify the number of partitions and the replication factor. Here’s how to create a topic with 100 partitions: Step-by-step instructions: Open a terminal on your machine where Kafka is installed. Run the kafka-topics.sh command with the necessary options to create the topic: kafka - topics . sh - - create - - bootstrap - server localhost:9092 - - replication - factor 1 - - partitions 100 - - topic < topic_name > --bootstrap-server localhost:9092 : Specifies the Kafka broker (or cluster) address. Replace localhost:9092 with your actual Kafka broker address if it’s different. --replication-factor 1 : Specifies the number of replicas for each partition. In this example, it's set to 1 , but in a production environment, you’ll want a higher replication factor for redundancy. --partitions 10...
자세한 내용 보기

The logs of the kubelet service

The logs of the kubelet service can be found depending on how the system is set up. Here are the most common locations: 1. Systemd Logs If your system uses systemd to manage services (most modern Linux distributions do), you can view the kubelet logs using journalctl : View Real-time Logs: sudo journalctl -u kubelet -f View Historical Logs: sudo journalctl -u kubelet 2. Log File on Disk On some systems, kubelet writes its logs to a file in /var/log . The exact location depends on the configuration: Common Locations : /var/log/kubelet.log /var/lib/kubelet/logs If the log file is not there, check the kubelet service configuration for custom log paths. 3. Kubernetes Configuration Flags The kubelet log location can be customized using the --log-dir or --log-file flags in the kubelet service configuration. To verify: Check the kubelet service file: cat /etc/systemd/system/kubelet .service .d / 10 -kubeadm.conf Look for logging-related flags, such as: Exec...
자세한 내용 보기

To switch to a specific tag in a Git repository

To switch to a specific tag in a Git repository, you can use the git checkout or git switch command. Here's how you can do it: 1. List Available Tags First, you may want to see a list of all available tags in the repository: git tag 2. Checkout a Specific Tag Once you know the tag you want to switch to, you can use either git checkout or git switch (if you're using a newer version of Git, which recommends git switch for checking out branches). Using git checkout : git checkout <tag- name > Using git switch (recommended for newer versions of Git): git switch -- detach <tag- name > The --detach flag is necessary because tags are not branches; they are just pointers to specific commits. Using --detach makes your HEAD point to the tag without modifying any branch. 3. Verify the Checkout After switching to the tag, verify that you're on the correct commit: git status This will show the tag you're currently on (you'll see somethi...
자세한 내용 보기

max_active_runs of Airflow

In Apache Airflow, if you want to ensure that a new run of a DAG doesn’t start before the previous one has completed, you can use the max_active_runs parameter in the DAG definition. Setting this parameter to 1 ensures that only one instance of the DAG is running at any given time. Setting max_active_runs for a DAG Here’s an example of how to set up a DAG with max_active_runs=1 : from airflow import DAG from airflow.operators.dummy_operator import DummyOperator from datetime import datetime # Define the DAG with DAG( 'my_dag' , description= 'A sample DAG' , schedule_interval= '@daily' , # Set your schedule start_date=datetime( 2023 , 1 , 1 ), catchup= False , max_active_runs= 1 # This prevents new runs before the previous run completes ) as dag: # Define tasks start = DummyOperator(task_id= 'start' ) end = DummyOperator(task_id= 'end' ) # Define task dependencies ...
자세한 내용 보기

Auto-populate a calendar in an MUI (Material-UI) TextField component

To auto-populate a calendar in an MUI (Material-UI) TextField component, you can make use of the MUI DatePicker component. Here's an example of how you can achieve this: First, make sure you have installed the necessary dependencies. You'll need Material-UI and its pickers library. npm install @material-ui/core @material-ui/pickers Import the required components and functions in your code: import React, { useState } from 'react' ; import TextField from '@material-ui/core/TextField' ; import { KeyboardDatePicker, MuiPickersUtilsProvider } from '@material-ui/pickers' ; import DateFnsUtils from '@date-io/date-fns' ; Create a functional component and define the state to hold the selected date value: const MyForm = () => { const [selectedDate, setSelectedDate] = useState( null ); const handleDateChange = (date) => { setSelectedDate(date); }; return ( <MuiPickersUtilsProvider utils={DateFnsUtils}>...
자세한 내용 보기