This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
Shape the future of IBM!
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Search existing ideas
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
Specific links you will want to bookmark for future use
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
IBM Employees should enter Ideas at https://ideas.ibm.com
See this idea on ideas.ibm.com
We are replicating data from DB2 to Cockroach DB using the CDC FlexRep flavor. And we have a highly available multi region/multi cluster Cockroach DB which allows client to access the database anytime. A client connecting to the Database uses a Network Load Balancer which decides which node is healthy and points the traffic to that node. During an event of a node failure we observe that CDC is able to identify the failure but instead of reconnecting to the database by making a new connection it keeps using the already established connection and retries there and eventually fails after the retry limit is reached. Having a feature to make new connections and then retrying a failed transaction will make the CDC a true highly available system.
Needed By | Month |
By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.
When there is a node down scenario then we typically a client using a PostgreSQL gets an error with org.postgresql.util.PSQLException: ERROR: server Where as for an error that requires a transaction restart for Cockroach DB with a healthy DB connections receive a 40001 error cods. Attached are some of the common Cockroach DB errors that can be resolved by just retrying the UOW to the database using the same connection. https://www.cockroachlabs.com/docs/stable/common-errors
But in case of a multi node Cockroach DB cluster and one node goes down CDC has to trap the org.postgresql.util.PSQLException: ERROR: server kind of error and then restart the subscription.
Can you please share if the "node down" situation will result in a different sql code returned from the database compared to the "not node down" scenario?