@Dominique De Vito When creating the KDC server the database holds the Master key The keytab contains pairs of Kerberos principals and keys in the encrypted form The Keytab is authenticated the against the Master key in KDC server which is generated using kdb5_util HTH ... View more

@Michael Bronson I meant using i.e Firewall to block the public-repo-1.hortonworks.com public IP or disable it in the repo by setting enabled=0 (false) instead of 1 (true) see below [HDP-UTILS-1.1.0.21] name=HDP-UTILS-1.1.0.21baseurl=http://public-repo-1.hortonworks.com/HDP-UTILS-1.1.0.21/repos/xx path=/ enabled=0 That you can use a script ... View more

@Michael Bronson The replication relies on the WAL files in pg_xlog and px_xlog generated these can be deleted by PostgreSQL automatically. Unless you have enabled replication for this Postgres instance? If it keeps WAL files for too long then check the settings at WAL configuration. WAL Files are a record of all the transactions that have taken place .. but that's it - a delta between state before and state after, essentially. Which means you have to have a BASE to start off of before you can apply any WAL Files. If you clear out WAL archives without creating a new BASE, then you will be in trouble when you try to restore your database (via PITR) from them. If you are going to delete WAL files, then you need to make sure you have a valid base to build from again afterward. Did you activate some parameters in your default postgresql.conf like archiving/replication? If so stop the Postgres database, comment out the lines and restart the databases it quite simply. Stopped the DB, commented the options in postgresql.conf and restarted. PostgreSQL will take care of deleting everything automatically ... View more

@Michael Bronson I think you need to quite understand what the parameters mean once spark.history.fs.cleaner.enabled has been set to true The Key/Value pairs Value is in Hour(s) /days spark.history.fs.cleaner.maxAge =1d Job history files older than this will be deleted when the filesystem history cleaner runs. spark.history.fs.cleaner.interval=1h This dictates how often the filesystem job history cleaner checks for files to delete. Files are only deleted if they are older than spark.history.fs.cleaner.maxAge so in your case above the maxAge is 1 day=12h so expect the files to be deleted only then. To test or validate you can change it to 2h and those files should be gone 3h HTH ... View more

@Michael Bronson Sorry to get back late there is no real test. But you could retry the same manipulation by upload conf file to zookeper you shouldn't get the same error ... View more