User:Elukey/Analytics/Hadoop testing cluster
- 1 Purpose of Kerberos
- 2 Map of the testing hosts
- 3 How do I..
- 4 How do I... (Analytics admins version)
- 5 Tests by Joal
Purpose of Kerberos
Hadoop by default does not ship with a strong authentication mechanism for users and daemons. In order to enable its "Secure mode", an external authentication service must be plugged in, and the only compatible one is Kerberos.
When enabled, like in the Hadoop test cluster, it means that users and daemons will need to authenticate to our Kerberos service before being able to use Hadoop. Please read the next sections to get more info about what do to.
Map of the testing hosts
The Hadoop test cluster is composed by old Hadoop Analytics nodes:
- analytics1028 - Hadoop master (Yarn Resource Manager, HDFS Namenode, MapReduce History server)
- analytics1029 - Hadoop master-standby (Yarn Resource Manager, HDFS Namenode)
- analytics1030 - Hadoop coordinator (Hive Server 2, Hive Metastore, Oozie, etc..)
- analytics10[31-38,40] - Hadoop worker nodes (Yarn Node Manager, HDFS Datanode, HDFS Journalnode)
- analytics1039 - Hadoop UIs (yarn.wikimedia.org, Hue)
- analytics1041 - Druid single node test cluster
- an-tool1006 - Client node - SWAP/jupyterhub
This little cluster is aimed to test the Secure mode enabled (Kerberos) before reaching production.
How do I..
Authenticate via Kerberos
kinit command, insert your password and then execute any command (spark, etc..). This is very important since if you don't do it, you'll see horrible error messages reported by basically anything you'll use. The kinit command grants you a so called Kerberos TGT, that will be used to allow you to authenticate to various services/hosts. The ticket last 24h, so you will not need to run kinit every time, just once a day. You can inspect the status of your ticket via
Get a password for Kerberos
Ask to Luca (elukey) on Freenode #wikimedia-analytics or via email. You'll receive an email containing a temporary password, that you'll be required to change during you first authentication (see section above).
- This is really annoying, can't we just use LDAP or something similar to avoid another password?
- We tried really hard but for a lot of technical reasons, the integration would be complicated and cumbersome to maintain for Analytics and SRE. There might be some changes in the future, but for now we'll have to deal with another password to remember.
Run a recurrent job via Cron or similar without kinit every day
The option that is currently available is a Kerberos keytab: a file with permissions set that only the owner can read, holding the password to authenticate to Kerberos. We use keytabs for daemons/services, and we'll plan to provide those to users with the need to run periodical jobs. The major drawbacks are:
- our security standard lowers down a bit, since it is sufficient to ssh to a host to access HDFS (as opposed to also know a password). This is more or less the current scheme, so not a big deal, but we have to think about it.
- The keytab needs to be generated for every host that needs to have this automation and it also needs to be regenerated and re-deployed when the user changes the password (this doesn't happen for daemons of course). It is currently not automated, and it requires a ping to Analytics every time..
To summarize: we'll work on a solution, possibly shaped by feedback from users, but for the first iteration we'll not provide keytabs for all users (only selectively deploying those if needed). If you think that your use case needs it, please ping Analytics.
Know what datasets I can use
In the Hadoop test cluster we have only a few datasets available:
- webrequest (sampled)
- pageviews (sampled)
If you need more, please ping Luca or the Analytics team :)
Check the Yarn Resource Manager's UI
ssh -L 8088:analytics1028.eqiad.wmnet:8088 analytics1028.eqiad.wmnet
Then localhost:8088 on the browser.
ssh -L 8080:analytics1039.eqiad.wmnet:80 analytics1039.eqiad.wmnet
Then localhost:8080 on the browser.
hive cli is compatible with Kerberos, even if it uses an old protocol (connecting to the Hive Metastore and HDFS directly). The
beeline command line uses the Hive 2 server via JDBC and it is also compatible with Kerberos. You just need to authenticate as described above and then run the tool on an-tool1006.eqiad.wmnet.
Use Spark 2
On an-tool1006, authenticate via kinit and then use the spark shell as you are used to. There are currently some limitations:
- Due to https://issues.apache.org/jira/browse/SPARK-23476, spark 2.3.x in local mode seems to not work with the option spark.authenticate = true. It is not set by default from Analytics, but if you use it be aware. The issue is fixed in Spark 2.4, that we are planning to deploy soon.
spark2-thriftserverrequires the hive keytab, that is only present on an-coord1001, so when running on client nodes it will return the following error:
org.apache.hive.service.ServiceException: Unable to login to kerberos with given principal/keytab
We added authentication and encryption options to the Spark2 defaults when testing Kerberos, since by default there is none provided/enforced. These options will ensure proper auth/encryption of traffic exchanged by Spark workers for example.
Use Jupyterhub (SWAP replica)
ssh -N an-tool1006.eqiad.wmnet -L 8000:127.0.0.1:8000
You can authenticate to Kerberos running kinit in the Terminal window. Please remember that it will be needed only once every 24h, not every time.
How do I... (Analytics admins version)
Check the status of the HDFS Namenodes and Yarn Resource Managers
Most of the commands are the same, but of course to authenticate as the user hdfs you'll need to use a keytab:
sudo -u hdfs kerberos-run-command hdfs /usr/bin/yarn rmadmin -getServiceState analytics1028-eqiad-wmnet sudo -u hdfs kerberos-run-command hdfs /usr/bin/hdfs haadmin -getServiceState analytics1029-eqiad-wmnet
Tests by Joal
The basics - All good :)
Oozie - All good :)
|hive2||Needs hive2 server URI, hive2 server principal, credential settings (hive2 credential type in workflow), and credential reference in every hive2 action||Tested with |
|fs||No configuration needed, credentials set in oozie itself.||Tested with |
|No configuration, working as is (expected, no cross-component communication needed)||Tested with |
|shell||No configuration, working as is (expected, no cross-component communication needed)||Tested with |
|spark||Configuration needed if spark uses Hive Metastore (
When using hive metastore: hive metastore URI, hive metastore principal, credential settings (hcat credential type in workflow), and credential reference in every spark action
|Tested with updated |
|MapReduce||No configuration needed, credentials set in oozie itself.||Tested with a new workflow created on purpose|
SWAP - Some problematic things :)
- Running HDFS commands in jupyter terminal behave as expected: failure without
kinit, success with it
- Local spark kernels (pyspark or scala-spark) work as long as not accessing hdfs or hive withtout
kinit. For hive access or hdfs access,
- YARN spark kernels (pyspark and scala-spark, normal or large) don't work without
- No errors are reported in the notebook when the kernel doesn't manage to start (due to missing
- Notebook kernels need to be restarted after the
kinitgot issued to pick the new ticket. This means all computation stored in notebook cache is lost.
- Notebook kernel having been started with a valid
kinit(i should say kerb ticket ...) works even after
kdestroyis called on the term.