[
https://issues.apache.org/jira/browse/KUDU-2179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Will Berkeley resolved KUDU-2179.
---------------------------------
Resolution: Fixed
Fix Version/s: 1.8.0
Fixed by 0d4740b7692c0cb5c39cca73276b395921bd3ae4. Note that the upgraded ksck
checksum process will work when run against older clusters that support
checksum scans with snapshots.
> Have ksck not use a single snapshot for all tablets
> ---------------------------------------------------
>
> Key: KUDU-2179
> URL: https://issues.apache.org/jira/browse/KUDU-2179
> Project: Kudu
> Issue Type: Improvement
> Components: ksck
> Reporter: Andrew Wong
> Assignee: Will Berkeley
> Priority: Major
> Fix For: 1.8.0
>
>
> When ksck runs, it selects a single timestamp and does a snapshot scan at
> this time across all tablets. If the scans run for a long time (e.g. due to
> heavy traffic to the tservers), some scans may be attempted on data that has
> already been GC'ed, surfacing the errors:
> {{Error: Invalid argument: Snapshot timestamp is earlier than the ancient
> history mark. Consider increasing the value of the configuration parameter
> --tablet_history_max_age_sec. Snapshot timestamp: P: 1507232752670708 usec,
> L: 0 Ancient History Mark: P: 1507232752970869 usec, L: 0 Physical time
> difference: -0.300s}}
> This could be remediated by batching these scans and selecting a new
> timestamp for each batch.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
