carbondata-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From kunalkap...@apache.org
Subject [carbondata] branch master updated: [CARBONDATA-3492]: Added prepriming in the Index Server Documentation
Date Thu, 16 Jan 2020 05:22:56 GMT
This is an automated email from the ASF dual-hosted git repository.

kunalkapoor pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/carbondata.git


The following commit(s) were added to refs/heads/master by this push:
     new 7d3987b  [CARBONDATA-3492]: Added prepriming in the Index Server Documentation
7d3987b is described below

commit 7d3987b0bd54bd3d381b94871c9873cf618154ce
Author: Vikram Ahuja <vikramahuja8803@gmail.com>
AuthorDate: Wed Jan 8 11:59:21 2020 +0530

    [CARBONDATA-3492]: Added prepriming in the Index Server Documentation
    
    This PR consists of the documentation changes for the feature Index Server Cache Prepriming.
    
    This closes #3566
---
 docs/index-server.md | 15 ++++++++++++++-
 1 file changed, 14 insertions(+), 1 deletion(-)

diff --git a/docs/index-server.md b/docs/index-server.md
index 7aff6df..7eba589 100644
--- a/docs/index-server.md
+++ b/docs/index-server.md
@@ -116,9 +116,20 @@ meaning that no matter how small the splits are they would be written
to the fil
 102400KB which will mean if the size of the splits for a executor cross this value then they
would
 be written to file.
 
-The user can set the location for these file by using 'carbon.indexserver.temp.path'. By
default
+The user can set the location for these files by using 'carbon.indexserver.temp.path'. By
default
 table path would be used to write the files.
 
+## Prepriming
+As each query is responsible for caching the pruned datamaps, thus a lot of execution time
is wasted in reading the 
+files and caching the datmaps for the first query.
+To avoid this problem we have introduced Pre-Priming which allows each data manipulation
command like load, insert etc 
+to fire a request to the index server to load the corresponding segments into the index server.
+When index server receives a request it checks whether the request is for pre-priming, if
it is then the request is 
+processed in a new thread, and a dummy response is immediately returned to the client.
+Since pre-priming acts as an async call, it does not have any negative performance impacts.

+
+The user can enable prepriming by using 'carbon.indexserver.enable.prepriming' = 'true/false'.
By default this is set as false.
+
 ## Configurations
 
 ##### carbon.properties(JDBCServer) 
@@ -130,6 +141,8 @@ table path would be used to write the files.
 | carbon.index.server.port | NA | The port on which the index server is started. |
 | carbon.disable.index.server.fallback | false | Whether to enable/disable fallback for index
server. Should be used for testing purposes only. Refer: [Fallback](#fallback)|
 |carbon.index.server.max.jobname.length|NA|The max length of the job to show in the index
server service UI. For bigger queries this may impact performance as the whole string would
be sent from JDBCServer to IndexServer.|
+|carbon.indexserver.enable.prepriming|false|Enable the use of prepriming in the Index Server
to improve the performance of first time query.|
+
 
 
 ##### carbon.properties(IndexServer) 


Mime
View raw message