-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug] [Connector-V2] connector-maxcompute: The source reader may cause data duplication #8379
Comments
Failed to connect to github.com port 443 after 21089 ms: Couldn't connect to server.
package org.apache.seatunnel.connectors.seatunnel.maxcompute.source; import org.apache.seatunnel.shade.com.typesafe.config.Config; import org.apache.seatunnel.api.configuration.ReadonlyConfig; import com.aliyun.odps.data.Record; import java.util.ArrayList; @slf4j
} |
Search before asking
What happened
When maxcompute source split enumerator assign pending splits, the assignSplitOperation is sent to task group worker and source reader execute pollNext(Collector output) completed, if split enumerator signalNoMoreSplits Operation
is not arrived, the pollNext(Collector output) may execute again. This leads to the set of splits read more than once. It is easy to hanpened when the cluster's system load is high.
SeaTunnel Version
2.3.7
SeaTunnel Config
Running Command
Error Exception
Zeta or Flink or Spark Version
zeta
Java or Scala Version
java 1.8
Screenshots
No response
Are you willing to submit PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: