InfoSphere Streams Technical Overview - Use Cases Big Data - Jerome CHAILLOUX
High Availability for IBM InfoSphere Streams V4.0
-
Upload
lisanl -
Category
Data & Analytics
-
view
110 -
download
0
Transcript of High Availability for IBM InfoSphere Streams V4.0
© 2015 IBM Corporation
High Availability
IBM InfoSphere Streams Version 4.0
Steve Halverson
Senior Software Engineer
2 © 2015 IBM Corporation
Important Disclaimer
THE INFORMATION CONTAINED IN THIS PRESENTATION IS PROVIDED FOR INFORMATIONALPURPOSES ONLY.
WHILE EFFORTS WERE MADE TO VERIFY THE COMPLETENESS AND ACCURACY OF THEINFORMATION CONTAINED IN THIS PRESENTATION, IT IS PROVIDED “AS IS”, WITHOUT WARRANTYOF ANY KIND, EXPRESS OR IMPLIED.
IN ADDITION, THIS INFORMATION IS BASED ON IBM’S CURRENT PRODUCT PLANS AND STRATEGY,WHICH ARE SUBJECT TO CHANGE BY IBM WITHOUT NOTICE.
IBM SHALL NOT BE RESPONSIBLE FOR ANY DAMAGES ARISING OUT OF THE USE OF, OROTHERWISE RELATED TO, THIS PRESENTATION OR ANY OTHER DOCUMENTATION.
NOTHING CONTAINED IN THIS PRESENTATION IS INTENDED TO, OR SHALL HAVE THE EFFECT OF:
• CREATING ANY WARRANTY OR REPRESENTATION FROM IBM (OR ITS AFFILIATES OR ITS ORTHEIR SUPPLIERS AND/OR LICENSORS); OR
• ALTERING THE TERMS AND CONDITIONS OF THE APPLICABLE LICENSE AGREEMENTGOVERNING THE USE OF IBM SOFTWARE.
IBM’s statements regarding its plans, directions, and intent are subject to change orwithdrawal without notice at IBM’s sole discretion. Information regarding potentialfuture products is intended to outline our general product direction and it should notbe relied on in making a purchasing decision. The information mentioned regardingpotential future products is not a commitment, promise, or legal obligation to deliverany material, code or functionality. Information about potential future products maynot be incorporated into any contract. The development, release, and timing of anyfuture features or functionality described for our products remains at our solediscretion.
THIS INFORMATION IS BASED ON IBM’S CURRENT PRODUCT PLANS AND STRATEGY, WHICH ARE SUBJECT TO CHANGE BY IBM WITHOUT NOTICE.
IBM SHALL NOT BE RESPONSIBLE FOR ANY DAMAGES ARISING OUT OF THE USE OF, OR OTHERWISE RELATED TO, THIS PRESENTATION OR ANY OTHER DOCUMENTATION.
3 © 2015 IBM Corporation
Agenda
Domain High Availability
Instance High Availability
Questions
4 © 2015 IBM Corporation
High Availability
domain.highAvailabilityCount and instance.highAvailabilityCount
– Default value is 1
– Value = active + standby → 3 implies active(1) + standby(2)
Active Service
– Typically one service is active
• sws
– One for entire domain
• jmx
– At most one per resource
– All jmx services are active (for load distribution)
• hc/app
– Active service per resource
– At most 1 standby service per resource
Standby Services
– Waiting in a dormant state
– Spread across several systems or can be duplicated on single systems
– If active service fails, restore state and assume responsibilities
5 © 2015 IBM Corporation
Domain Controller
New service introduced in Version 4.0 (controller)
– Manages all services that run on a resource
Can be registered as a Linux system service
– Automatically starts when system boots
– Must have root authority to register/start/stop/unregister
Detect streams service failures
– Automatically restart services if they fail or are killed
– Leader controller monitors health of other controllers
Monitor streams service health
– Automatically quiesce services that appear to be unresponsive
6 © 2015 IBM Corporation
Domain Host Tags
Generic Placement
– management
• Resource eligible for all domain services unless explicit placement
Explicit Placement
– Take precedence over generic management tag
• authentication
– aas service
• audit
– auditlog service
• jmx
– jmx management service
• sws
– console/rest services
Recommendation is that resources are explicitly tagged
7 © 2015 IBM Corporation
Instance Host Tags
Generic Placement
– management
• Resource eligible for all instance services unless explicit placement
Explicit Placement
– view
• Take precedence over generic management tag
• view service
– application
• hc/app service
– Custom Tags
• auditlog service
Recommendation is that resources are explicitly tagged
8 © 2015 IBM Corporation
Demo
Create domain with high availability
Create instance with high availability
Tag resources for high availability
9 © 2015 IBM Corporation
SWS and JMX considerations
sws
– Need resource specific certificate
– Url is available using streamtool command
• streamtool geturl
– Each resource tagged for sws should be setup properly
– Console/rest urls can change if resource fails
jmx
– Urls are available using streamtool command
• streamtool getjmxconnect
– Jmx connect url can change if resources fails
10 © 2015 IBM Corporation
Questions?