phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ramkrish86 <>
Subject [GitHub] phoenix pull request: Phoenix 180
Date Thu, 04 Sep 2014 04:31:56 GMT
Github user ramkrish86 commented on the pull request:
        java.lang.IllegalArgumentException: KeyValue size too large
            at org.apache.hadoop.hbase.client.HTable.validatePut(
            at org.apache.hadoop.hbase.client.HTable.doPut(
            at org.apache.hadoop.hbase.client.HTable.put(
            at org.apache.hadoop.hbase.coprocessor.CoprocessorHost$Environment$HTableWrapper.put(
            at org.apache.phoenix.schema.stat.StatisticsTable.updateStats(
            at org.apache.phoenix.schema.stat.StatisticsScanner.close(
            at org.apache.hadoop.hbase.regionserver.compactions.DefaultCompactor.compact(
            at org.apache.hadoop.hbase.regionserver.DefaultStoreEngine$DefaultCompactionContext.compact(
            at org.apache.hadoop.hbase.regionserver.HStore.compact(
            at org.apache.hadoop.hbase.regionserver.HRegion.compact(
            at org.apache.hadoop.hbase.regionserver.CompactSplitThread$
            at java.util.concurrent.ThreadPoolExecutor.runWorker(
            at java.util.concurrent.ThreadPoolExecutor$
    What could be ideal value for those guidePost collection - Like after how many bytes could
we collect the guideposts?  And for the what could be the best value based
on its distribution?

If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

View raw message