After modifying the configuration, you must restart the cluster. A rolling restart applies the changes with minimal impact on the cluster. The larger the cluster, the smaller the impact.
On the Parameter Settings page, on the Modifiable Parameters tab, find the
hbase.hregion.majorcompaction parameter. In the Actions column, click Modify and change the value to 0 (the default value is 604800000). Then, click the Restart button in the upper-right corner of the page to restart the cluster.- The system records a history of your changes.
- Future versions will allow you to apply some parameter changes without restarting the cluster.
- The following table lists some of the configurable parameters. For a complete list, see the console.
| Parameter | Default | Description |
| hbase.hregion.majorcompaction | 604800000 | The default value is 604800000 milliseconds (one week). You can set it to 0 to disable automatic major compactions. Future versions will support triggering compactions periodically or within a specific time window. |
| hbase.ipc.server.callqueue.read.ratio | 0 | Specifies the proportion of the call queue dedicated to read requests to enable read/write splitting. |
| hbase.ipc.server.callqueue.scan.ratio | 0 | Controls read/write splitting. |
| hbase.regionserver.global.memstore.lowerLimit | 0.3 | The lower limit for memstore usage. After forced flushes begin, they continue until usage drops below this threshold. |
| hbase.regionserver.global.memstore.size | 0.35 | The upper limit for memstore usage as a percentage of the heap. Exceeding this limit forces a flush. |
| hbase.rpc.timeout | 60000 | The timeout period for Remote Procedure Call (RPC) requests, in milliseconds. You can increase this value. |
| hfile.block.cache.size | 0.4 | The percentage of the heap allocated to the block cache. For read-heavy workloads, you can increase this value to 0.5. |
该文章对您有帮助吗？