glorv
glorv
@lddlww This will not cause lightning fails because the outer loop will retry ingest the kv pairs again. This Error is confusing, there is a pr that will change this...
@overvenus could you paste the full log file? The `listenCheckpointUpdates` is an async action, and its error is always ignored. So I think the first error is the real cause...
I have looked into this issue a bit, there are pros and cons for both of the two solutions: 1. Rename the table name during importing - pros - Available...
@IANTHEREAL @kennytm @overvenus @Little-Wallace PTAL
> actually table locking is not sufficient to protect against Lightning failing 🤔. When Lightning crashes, the session holding the lock will be broken and the other sessions will be...
Since #400 is merged, I think this issue can be closed? @YuJuncen
Should be caused by https://github.com/tikv/tikv/issues/9496
the newest progress log format is as follows: ``` [2020/08/18 17:15:38.048 +08:00] [INFO] [restore.go:523] [progress] [files="304/337 (90.2%)"] [tables="7/9 (77.8%)"] [speed(MiB/s)=115.4747196733547] [state=writing] [remaining=1m5s] ``` So this issue is outdated now.
@3pointer Please add a unit test and an integration test
We are planning to take two steps to optimize the progress log: 1. Short term optimization. for local backend, add progress for import phase something like `[import=66GB/100GB(66%)]`. 2. Long term...