Member since
09-29-2015
56
Posts
8
Kudos Received
6
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
2555 | 06-08-2016 02:49 PM | |
1389 | 04-14-2016 11:14 PM | |
4446 | 01-20-2016 03:22 AM | |
2138 | 12-21-2015 09:05 PM | |
2554 | 12-15-2015 10:55 PM |
06-08-2016
06:28 PM
@Piotr Pruski How are you setting up replication? Is it using Feed Replication or is it using Falcon recipe. Can you please do "falcon admin -version" and share the result. Can you also share the feed entity ?
... View more
06-08-2016
02:49 PM
Can you please change the "stats" and "meta" location in Feed to /tmp/${YEAR}-${MONTH}-${DAY}-${HOUR} and try again? If updating stats and meta locations will ensure eviction succeeds, then this is an improvement we will have to make in Falcon.
... View more
05-19-2016
08:44 PM
The working and staging dir should have the following permissions. hadoop fs -chown -R falcon /user/falcon/sbpRndCluster/ hadoop fs -chmod -R 777 /user/falcon/sbpRndCluster/staging hadoop fs -chmod -R 755 /user/falcon/sbpRndCluster/working Once you set these permissions, submitting cluster should be straightforward. When you see errors like "Unable to validate the location with path: /apps/falcon/primaryCluster/staging for cluster:sbpRndCluster due to transient failures", can you please share the logs from falcon.application.log, this will give us more information about what is happening.
... View more
05-17-2016
04:14 PM
@Hanna Lee Please make sure the execute endpoint is using port 8050. You can find this in Yarn configs under yarn.resourcemanager.address. This port can be 8032 on some nodes, but I think sandbox uses 8050. Once you have the right port, please restart falcon and try submitting cluster again. The restart is required because there could be a stale FileSystem object in Falcon server.
... View more
04-14-2016
11:14 PM
To add to what @vramachandran said, Falcon also supports replication to Azure ( http://hortonworks.com/hadoop-tutorial/incremental-backup-data-hdp-azure-disaster-recovery-burst-capacity/) and AWS as well.
... View more
02-02-2016
09:49 PM
Ah, my bad. Too many messages here and I missed your solution. Thanks @Sowmya Ramesh
... View more
02-02-2016
09:40 PM
@Nayan Paul : I might have found the problem. Here is what you have for the process. <validity start="2015-12-01T23:33Z" end="2018-01-03T23:33Z"/> </cluster> ...
<parallel>1</parallel> <order>FIFO</order> <frequency>minutes(5)</frequency>
The input feed you have is 2016-01, almost a month after the validity start 2015-12. You have one process instance running every 5 minutes, so that is approximately 72x31 instances that should be processed before getting to 2016-01. So your process instances in 2015-12 are waiting for input feed 2015-12.... and will wait for almost a month since you said FIFO order should be used.
Create input feed 2015-12 and you will see data being processed end to end. Let me know if this solves the issue.
... View more
02-01-2016
10:51 PM
@Ashnee Sharma : Did @Kuldeep Kulkarni's response answer your question? If yes, please accept the answer
... View more
01-21-2016
07:22 PM
@bsaini , @Artem Ervits
... View more
01-21-2016
07:21 PM
Hi Team, The information in 2.3.0 docs had an error. Please use information at https://docs.hortonworks.com/HDPDocuments/HDP2/HDP-2.3.4/bk_installing_manually_book/content/configuring_oozie_for_falcon.html , I will work with documentation team to get 2.3.0 doc fixed.
... View more