[KUDU-1210] Print nicer FATAL message when required CPU flags are not present

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: Public beta
• Fix Version/s: 0.6.0
• Component/s: util
• Target Version/s: 0.6.0
• Code Review: http://gerrit.cloudera.org:8080/1327
• Assignee: Todd Lipcon
• Reporter: Todd Lipcon
• Created: 07/Oct/15 21:48
• Updated: 17/Nov/15 21:33
• Resolved: 17/Nov/15 21:33

Description

Currently if a user tries to run Kudu on a machine that doesn't have SSSE3 or SSE4.2, they get a SIGILL when we try to run a instruction from those instruction sets. Instead, we should check for those flags at startup and FATAL with a nice message.

If this turns out to limit adoption, we can put in some effort to cordon off the SSE-enabled parts of the code and provide non-SSE alternatives.