Runtime.getRuntime().maxMemory()) that all threads may use. Threshold size in bytes up to which results from parallelly executed query results are spooled to disk above which the query will fail. Threshold size in bytes after which results from parallelly executed query results are spooled to disk. Unless your client is controlling the timestamps while reading and writing data, this parameter should be left alone. If false, then the max timestamp found while traversing the table over which statistics are being collected is used as the timestamp. Server-side parameter that if true causes the current time on the server-side to be used as the timestamp of rows in the statistics table when background tasks such as compactions or splits occur. The default value is 15 min.Ĭlient-side parameter that determines the minimum amount of time in milliseconds that must pass before statistics may again be manually collected through another UPDATE STATISTICS call. Server-side paramater that determines the frequency in milliseconds for which statistics will be refreshed from the statistics table and subsequently used by the client. Otherwise, if not set, then the parameter is used. If set to a value greater than zero, then the guidepost width is determiend by MAX_FILE_SIZE of table / .region. Server-side parameter that specifies the number of guideposts per region. A smaller amount increases parallelization, but also increases the number of chunks which must be merged on the client side. Server-side parameter that specifies the number of bytes between guideposts. If zero, a SynchronousQueue is used instead of the bounded round robin queue. Max queue depth of the bounded round robin backing the client side thread pool executor, beyond which an attempt to queue additional work is rejected. As the number of machines/cores in the cluster grows, this value should be increased. Number of threads in client side thread pool executor. Maximum time in milliseconds that excess idle threads will wait for a new tasks before terminating when the number of threads is greater than the cores in the client side thread pool executor. Default is 30 seconds.Ĭlient-side property specifying the number of milliseconds after which a query will timeout on the client. Server-side property specifying the timeout in seconds for a transaction to complete. Server-side property specifying the HDFS directory used to store snapshots of the transaction state. The table below outlines the full set of Phoenix-specific configuration properties and their defaults. In addition to these properties, there are of course all the HBase configuration properties with the most important ones documented here. The configuration is done through a series of Phoenix-specific properties specified both on client and server-side hbase-site.xml files. Phoenix provides many different knobs and dials to configure and tune the system to run more optimally on your cluster.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |