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,
Post an idea
Upvote ideas that matter most to you
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.
Suppress the "Operation category READ is not supported in state standby" warning message
Warning messages are appearing in all jobs and commands that use DataStage datasets after the Hadoop primary namenode server (xhadnamem1p) fails over to the secondary node (xhadnamem2p). In some cases the warnings are causing aborts due to the number of messages (one per node per dataset). The warning message is "WARN ipc.Client: Exception encountered while connecting to the server : org.apache.hadoop.ipc.RemoteException(org.apache.hadoop.ipc.StandbyException): Operation category READ is not supported in state standby." We believe this may be caused by part of the underlying architecture that is still referencing the primary node (xhadnamem1p) and we'd like to know what configuration change can be made to prevent these warnings from occurring. Please note that these particular warnings cannot be mapped to informational or removed from the jobs via message handlers because the message category also encompasses other messages that are critical.
Do not place IBM confidential, company confidential, or personal information into any field.