Closed makalaaneesh closed 1 day ago
@makalaaneesh can we do this change also
SetMaxIdleConns(paralleljobs)
To me this seems harmless and should fix the issue for large databases to a go extend, what do you think.
Yeaah, I was thinking about it. For the most part, no concerns. Just about total connections to source db being parallel-jobs x 2 (pg_dump/ora2pg using parallel-jobs and voyager layer using parallel-jobs). But since it's capped, I don't think it should be a big problem. Let me go ahead and do it. cc: @hbhanawat
Implements fixes 1,3 in https://github.com/yugabyte/yb-voyager/issues/1920 : When goroutines A,B,C,D encounter an error, they should not bring down the process, they should silently log the error and continue, as this is not a critical process.