kunal642 commented on a change in pull request #3738:
URL: https://github.com/apache/carbondata/pull/3738#discussion_r420770234
##########
File path: docs/index-server.md
##########
@@ -82,6 +82,15 @@ the pruned blocklets which would be further used for result
fetching.
**Note:** Multiple JDBC drivers can connect to the index server to use the
cache.
+## Enabling Size based distribution for Legacy stores
+The default round robin based distribution causes unequal distribution of
cache amoung the executors, which can cause any 1 of the executors to be
bloated with too much cache and cause performance degrade.
Review comment:
done
##########
File path: docs/index-server.md
##########
@@ -82,6 +82,15 @@ the pruned blocklets which would be further used for result
fetching.
**Note:** Multiple JDBC drivers can connect to the index server to use the
cache.
+## Enabling Size based distribution for Legacy stores
+The default round robin based distribution causes unequal distribution of
cache amoung the executors, which can cause any 1 of the executors to be
bloated with too much cache and cause performance degrade.
+This problem can be solved by running the upgrade_segment command which will
fill the data size values for each segment in the tablestatus file. Any cache
loaded after this can use the traditional size based distribution.
Review comment:
done
##########
File path: docs/index-server.md
##########
@@ -19,8 +19,8 @@
## Background
-Carbon currently prunes and caches all block/blocklet datamap index
information into the driver for
-normal table, for Bloom/Index datamaps the JDBC driver will launch a job to
prune and cache the
+Carbon currently prunes and caches all block/blocklet index information into
the driver for
+normal table, for Bloom/Index indexes the JDBC driver will launch a job to
prune and cache the
Review comment:
done
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
