Member since
09-24-2015
76
Posts
32
Kudos Received
10
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
724 | 02-24-2017 09:17 AM | |
3762 | 02-13-2017 04:49 PM | |
1353 | 09-26-2016 06:44 AM | |
674 | 09-16-2016 06:24 AM | |
1125 | 08-25-2016 02:27 PM |
09-13-2019
01:37 PM
Short Description: This article will help to renew kerberos ticket with Falcon. Article It has been seen that Falcon server fails to perform operations after kerberos credentials expire and following exception occur. Caused by: org.apache.hadoop.security.authentication.client.AuthenticationException: GSSException: No valid credentials provided (Mechanism level: Failed to find any Kerberos tgt) To solve this issue, we must set following parameter in Falcon startup.properties through ambari-ui to revalidate kerberos credentials. Value for this properties is in seconds. Stop Falcon server Set parameter : *.falcon.service.authentication.token.validity=<value in seconds> Start Falcon server Note: This article is for version greater than HDP-2.5.* .
... View more
- Find more articles tagged with:
- Falcon
- FAQ
- Kerberos
- Sandbox & Learning
Labels:
03-10-2017
11:34 PM
@n c Logs file you shared from Oozie and Falcon is not helping much to understand actual issue you are facing while running replication. From Falcon logs I found that one WF replication job (0000000-170309153350882-oozie-oozi-W) executed successfully. So if you are seeing that no replication happened can you please look to Oozie UI for this WF job and try to get corresponding Hadoop job to see whether it ran successfully or not.
... View more
03-10-2017
10:36 PM
@mayki wogno Just try to see if by deleting oozie auth token, if it helps you. rm ~/.oozie-auth-token
... View more
03-10-2017
06:54 PM
@n c I have just checked the falconlog.txt and found that replication job executed successfully. WF id : workflowId=0000000-170309153350882-oozie-oozi-W status=SUCCEEDED, Even for this WF job counters get populate as well showing how many bytes and files copied to backup cluster.
... View more
03-09-2017
07:11 PM
@n c Can you please share the falcon application log (/var/log/falcon/falcon.application.log) and oozie logs from /var/log/oozie to diagnose the issue, when you submit the falcon mirroring job.
... View more
02-24-2017
09:17 AM
@Sankar T To resolve this issue, following is the workaround : 1. Remove service org.apache.falcon.metadata.MetadataMappingService from *.application.services in falcon startup.properties available in /etc/falcon/conf/ 2. Restart falcon server Hope this helps
... View more
02-13-2017
04:49 PM
1 Kudo
@Abb Code Just try to see if by defining the required variable through global section in workflow.xml helps you. More details about defining global is available at following URL. https://oozie.apache.org/docs/4.2.0/WorkflowFunctionalSpec.html#a19_Global_Configurations
... View more
02-07-2017
08:51 AM
1 Kudo
@rahul gulati Earlier I observed that this similar exception occurred at the time of launching of Oozie workflow. Can you try to set following memory related parameter in Oozie workflow.xml with some higher value like 1024mb so that workflow launches successfully. For e.g: <property>
<name>oozie.launcher.mapred.map.child.java.opts</name>
<value>-Xmx1024m</value>
</property> See if this helps you.
... View more
01-13-2017
02:48 PM
@Shihab It looks like that Falcon server did not come up properly due to which Falcon webUI and client is having issues. Can you please share the falcon application log from Falcon logs directory to analyze the Falcon server issue.
... View more
09-26-2016
06:44 AM
2 Kudos
@alina n If there is delay in running of job through Oozie, just please check that ResourceManager must not be in overwhelming state and there must be sufficient capacity in cluster to execute jobs.
... View more
09-16-2016
06:24 AM
2 Kudos
@alina n It looks like that you need to add value “localhost” or "127.0.0.1" for parameter hadoop.proxyuser.oozie.hosts in /etc/hadoop/conf/core-site.xml. Once you add this through ambari-ui, please save and restart the Oozie service.
<property>
<name>hadoop.proxyuser.oozie.hosts</name>
<value>127.0.0.1,localhost,sandbox.hortonworks.com</value>
</property> Hope this helps you.
... View more
09-08-2016
05:18 AM
7 Kudos
In this article, we will see how to
perform the mirroring of Hive data and metadata using Falcon from source
cluster to destination cluster. This article is based on HDP 2.5.
Configure Hive Configure
source and target Hive by clicking “Hive” from the Ambari Services
menu, then click “configs” to add following custom properties on Ambari
UI by scroll down to “Custom hive-site”, click it and then click “Add
Property”. Add following property name with value: hive.metastore.event.listeners = org.apache.hive.hcatalog.listener.DbNotificationListener
hive.metastore.dml.events = true Press OK to save the changes, then click Restart all the impacted services.
Bootstrap Table and DB Before creating Hive DR mirroring job to replicate Hive data/metadata for a DB or Table, it is required to perform initial bootstrap of Table and DB from source to target cluster.
Table Bootstrap For bootstrapping table replication, do an EXPORT of the table in question at source cluster, distcp the export directory to the target cluster, and do an IMPORT at target cluster. Export-Import can be seen here : https://cwiki.apache.org/confluence/display/Hive/LanguageManual+ImportExport For example create the table global_sales and insert records: hive > create table global_sales
(customer_id string, item_id string, quantity float, price float, time timestamp)
partitioned by (country string);
hive > insert into table global_sales partition (country = 'us') values ('c1', 'i1', '1', '1', '2001-01-01 01:01:01'); Start Bootstrap ## On source cluster :
hive > export table global_sales to '/user/ambari-qa/export_sql';
$ hadoop distcp hdfs://machine-1-1.openstacklocal:8020/user/ambari-qa/export_sql
hdfs://machine-2-1.openstacklocal:8020/user/ambari-qa/import_sql
## On target cluster :
hive > import table global_sales from '/user/ambari-qa/import_sql'; Above steps will set up the target table in sync with source table so that the events on the source cluster that modify the table will then be replicated over. Database Bootstrap For bootstrapping DB replication, first target DB must be created. This step is expected because DB replication definitions can be set up only on pre-existing DB by users. Second, we need to export all tables in the source D B and import them in the target DB, as described in Table bootstrap.
Set up source and target cluster staging/working directory Source cluster: [root@machine-1-1 ~]# su - falcon hadoop fs -mkdir -p /apps/falcon/primaryCluster/staging hadoop fs -mkdir -p /apps/falcon/primaryCluster/working hadoop fs -chmod 777 /apps/falcon/primaryCluster/staging Target cluster: [root@machine-2-1 ~]# su - falcon hadoop fs -mkdir -p /apps/falcon/backupCluster/staging hadoop fs -mkdir -p /apps/falcon/backupCluster/working hadoop fs -chmod 777 /apps/falcon/backupCluster/staging
Create cluster entity Navigate to Falcon UI from Ambari services menu and create source cluster entity using Falcon UI by clicking “Create” -> “Cluster” Save the source cluster entity by clicking “Next”->”Save” . Create target cluster entity using Falcon UI by clicking “Create” -> “Cluster” Save the cluster entity by clicking “Next”->”Save” .
Insert records in source Hive server for replication. Insert some records in source Hive server to replicate to target Hive server. hive > insert into table global_sales partition (country = 'uk') values ('c2', 'i2', '2', '2', '2001-01-01 01:01:02');
Prepare and submit Hive DR Mirroring To submit the Hive DR mirroring job, click “Create”->”Mirror”->”Hive” and then fill the required values.
Click Next -> Save the Hive DR mirror job.
Submit and Schedule HiveDR
Check output Once scheduled Hive DR process completed (checked from Oozie UI), verify the target Hive server for output. Earlier, we inserted two records at source Hive server and now at target Hive server both records are available. ---
... View more
- Find more articles tagged with:
- disaster-recovery
- Falcon
- Governance & Lifecycle
- Hive
- How-ToTutorial
- Oozie
Labels:
09-05-2016
01:21 PM
Thanks @asitabh kumar
... View more
09-04-2016
05:21 PM
@asitabh kumar I have verified the oozie with version HDP 2.5.0.0-1245 and found that Oozie bin is available. $ ls /usr/hdp/2.5.0.0-1245/oozie/bin/
oozie ooziedb.sh oozied.distro oozie.distro oozied.sh oozie-env.sh oozie-run.sh oozie-setup.sh oozie-start.sh oozie-stop.sh oozie-sys.sh
Can you please let us know what are the steps you have tried, to deploy the HDP due to which you have got the Oozie bin missing.
... View more
09-02-2016
10:50 AM
1 Kudo
@chennuri gouri shankar Can you please attach the workflow.xml for further look. From the exception, it looks like that you are trying to run the workflow.xml on secure cluster. So just ensure that you have specified the hcat credential profile before hive action node. Hcat credential must contain the Hive metastore URI and Hive Kerberos principal. More details to specify the hcat credential profile is available at following link : https://oozie.apache.org/docs/4.2.0/DG_ActionAuthentication.html
... View more
08-30-2016
12:06 PM
@J. D. Bacolod Yes, it always good to configure and specify queue for better utilization of the compute resources rather running in default queue.
... View more
08-30-2016
06:23 AM
1 Kudo
@Arun A K Please do some Entity submission from Falcon CLI and then you can see submitted and scheduled entities on Falcon UI. The version you are using in that view capability of submitted entities is only available.
... View more
08-30-2016
06:11 AM
1 Kudo
@Arun A K Thanks for specifying the version. Have you done a successful submission of Falcon entities like (Cluster,Feed and process) from CLI before clicking these URL's from Falcon UI.
... View more
08-30-2016
05:40 AM
@Arun A K Which version of Falcon you are using. The links which you are seeing will show details about the submitted feed (data) entity, submitted/schedueld process entity and cluster entity.
... View more
08-25-2016
02:27 PM
1 Kudo
@da li As @Predrag Minovic mentioned for sharelib setup create, use following Oozie sharelib setup create command through 'oozie' user. /usr/hdp/current/oozie-server/bin/oozie-setup.sh sharelib create -fs hdfs://<hdfs hostname>:<hdfs port> -locallib /usr/hdp/current/oozie-server/oozie-sharelib.tar.gz Above command will create timestamp based oozie share lib directory to HDFS directory /user/oozie/share/lib . Hope this help you.
... View more
07-27-2016
12:04 PM
This issue is getting tracked on the following Apache Falcon JIRA : https://issues.apache.org/jira/browse/FALCON-1955
... View more
06-29-2016
11:32 AM
@mayki wogno Order of schema and ACL is required to changed. It must be like this :
...
<ACL owner="falcon" group="hadoop" permission="0755"/>
<schema location="hcat" provider="hcat"/>
....
... View more
05-30-2016
06:16 PM
@yjiang What is the HDP version you are using, for which you have seen that Falcon does not mirror data.
... View more
05-27-2016
09:27 AM
@mayki wogno Earlier 'location data path' in your feed section raised an alert as Frequency " ${YEAR}/${MONTH}/${DAY}/${HOUR}" was missing from data path. Thanks for confirming that it works now for you.
... View more
05-27-2016
08:50 AM
@mayki wogno 'location data path' in feed section is initial source data path, which can be overridden by 'location data path' if defined in source cluster section.
... View more
05-26-2016
03:36 PM
@mayki wogno Thanks for sharing the feed replication entity xml. I have looked around your entity and found that the exception occurred as location type data path is not defined with frequency. <location type="data"path="/tmp/falcon/"/> Can you define path as follows: path="/tmp/falcon/next-vers-current/${YEAR}/${MONTH}/${DAY}/${HOUR}" I am hoping once you define with frequency this will work. Also in the shared entity I am seeing that you have specified the same HDFS path for source and target. Can you please check this as well.
... View more
05-26-2016
12:19 PM
@mayki wogno To answer your question, atleast frequency based data feed must be available on primary cluster to copy the data on backup cluster periodically through scheduled feed replication. If data is not available on primary cluster, then scheduled instance will be in waiting state for data availability.
... View more
03-21-2016
04:42 PM
@Amit Tewari Is the job in pipeline successful, can you just check status. I think job might have failed due to which output did not generate. You can check the Oozie webui for the job status.
... View more
02-05-2016
06:52 AM
2 Kudos
@Saurabh Kumar Currently Falcon can't update the cluster entities but work is in progress to update the cluster entities https://issues.apache.org/jira/browse/FALCON-141 .
... View more
01-29-2016
03:39 PM
1 Kudo
@Nayan PaulCan you share the process entity as well the feed entity . From the exception it looks like that in the input element of process entity EL value for "start" attribute has been defined before the actual input feed entity datetime.
... View more