[GIRAPH-212] Security is busted since GIRAPH-168

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 1.0.0
• Fix Version/s: 1.0.0
• Component/s: build
• Assignee: Eugene Joseph Koontz
• Reporter: Jakob Homan
• Created: 21/Jun/12 18:38
• Updated: 02/May/13 02:29
• Resolved: 03/Oct/12 23:42

Description

As reported on the mailing list and verified here on our clusters, something's gone screwy with Giraph jobs on secure hadoop. I reverted back before GIRAPH-168 and this goes away, although I've not found out what it is yet (and may not be 168).

RPC clients are trying to open connections with the wrong configuration relative to the servers.

Issue Links

• depends upon: GIRAPH-229 fix prop.jarLocation for hadoop_facebook profile
• is related to: GIRAPH-200 remove hadoop RPC and keep just netty
• is related to: GIRAPH-211 Add secure authentication to Netty IPC
• relates to: GIRAPH-168 Simplify munge directive usage with new munge flag HADOOP_SECURE (rather than HADOOP_FACEBOOK) and remove usage of HADOOP