Github user liuyu000 commented on a diff in the pull request: https://github.com/apache/trafodion/pull/1361#discussion_r159642419 --- Diff: docs/provisioning_guide/src/asciidoc/_chapters/requirements.adoc --- @@ -331,13 +331,38 @@ default. Depending on the size of a user table, we have experienced timeout fail from this setting. The underlying issue is the length of the execution of the coprocessor within HBase. + NOTE: HBase uses the smaller of `hbase.rpc.timeout` and `hbase.client.scanner.timeout.period` to calculate the scanner timeout. -| hbase.snapshot.master.timeoutMillis and hbase.snapshot.region.timeout | 10 minutes | HBase's default setting is 60000 milliseconds. +| hbase.snapshot.master.timeoutMillis + +and + +hbase.snapshot.region.timeout | 10 minutes | HBase's default setting is 60000 milliseconds. If you experience timeout issues with HBase snapshots when you use the {project-name} Bulk Loader or other statements, you can set the value for these two HBase properties to 10 minutes (600,000 milliseconds). -| hbase.hregion.max.filesize | 107374182400 bytes | HBase's default setting is 10737418240 (10 GB). We have increased the setting to -107374182400 (100 GB), which reduces the number of HStoreFiles per table and appears to reduce disruptions to active transactions from +| hbase.hregion.max.filesize | 107374182400 bytes | HBase's default setting is 10737418240 bytes (10 GB). You can increased the setting to --- End diff -- Oops, sorry, I've corrected, thanks Dave :)
---