[
https://issues.apache.org/jira/browse/BEAM-7230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16962474#comment-16962474
]
Luke Cwik commented on BEAM-7230:
---------------------------------
Also, the connection factory here assumes that only one JdbcIO connector using
a PoolableDataSourceProvider and only one using a
DataSourceProviderFromDataSourceConfiguration will ever be used within a
pipeline since the connection pool will return the "first" DataSource that is
initialized since those classes all share the sameinstance` static variable.
The caching should really be from DataSourceConfiguration -> Instance
The good news is that DataSourceConfiguration is an AutoValue so it implements
an equals method so they are comparable.
> Using JdbcIO creates huge amount of connections
> -----------------------------------------------
>
> Key: BEAM-7230
> URL: https://issues.apache.org/jira/browse/BEAM-7230
> Project: Beam
> Issue Type: Bug
> Components: runner-dataflow
> Affects Versions: 2.11.0
> Reporter: Brachi Packter
> Assignee: Ismaël Mejía
> Priority: Major
> Fix For: 2.13.0
>
> Time Spent: 3h
> Remaining Estimate: 0h
>
> I want to write form DataFlow to GCP cloud SQL, I'm using connection pool,
> and still I see huge amount of connections in GCP SQL (4k while I set
> connection pool to 300), and most of them in sleep.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
