IBM Data and AI Ideas Portal for Customers


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:

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,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The product management team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive notification on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

Additional Information

To view our roadmaps: http://ibm.biz/Data-and-AI-Roadmaps

Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases

IBM Employees:

The correct URL for entering your ideas is: https://hybridcloudunit-internal.ideas.aha.io


Status Not under consideration
Workspace Db2 Big SQL
Created by Guest
Created on Oct 20, 2017

Add request resilience to data node failure as Hive does with map reduce

We use BigSql 4.0.1 for 1 year and a half.

Today when we want to plan a maintenance on one of our Hadoop cluster DataNode, we have running BigSql queries that can fail due to node beiing brought down.

 

I would like the engine to retry the request part on another worker node if the node is no longer reachable.

 

That way BigSql will be resilient to a single datanode failure.

 

Remember that datanode failure becomes a fairly normal event if you grow your cluster to 100 or 1000 nodes !!!

 

Regards,

 

Gaël