Member since
04-27-2016
218
Posts
133
Kudos Received
25
Solutions
My Accepted Solutions
| Title | Views | Posted |
|---|---|---|
| 3610 | 08-31-2017 03:34 PM | |
| 7470 | 02-08-2017 03:17 AM | |
| 3296 | 01-24-2017 03:37 AM | |
| 10595 | 01-19-2017 03:57 AM | |
| 6024 | 01-17-2017 09:51 PM |
06-23-2016
06:35 PM
2 Kudos
Yes, the connection cannot be deleted while it is providing data to a downstream component. The downstream component must be disabled or deleted before the connection can be deleted.
... View more
06-22-2016
05:44 PM
Thank you Andrew, it helped me resolving my issue.
... View more
06-23-2016
05:27 AM
3 Kudos
@milind pandit
I believe this feature is in roadmap for YARN. Currently we don't have any report etc. to keep track of historical performance metrics. Note - You can create your own script to get the required values from yarn REST API. Please have a look at https://community.hortonworks.com/articles/16151/yarn-que-utilization-ambari-widget.html to add queue utilization widget in Ambari. [ Not exact solution to the question but we can track queue utilization ]
... View more
06-21-2016
09:05 AM
1 Kudo
@milind pandit You can get access time using FileStatus#getAccessTime() as follows: public class HdfsAtime {
private static SimpleDateFormat sdf = new SimpleDateFormat("yyyy-MM-dd'T'HH:mm:ssZ");
public static void main(String[] args) throws IOException {
FileSystem fs = FileSystem.get(new Configuration());
printFileStatus(fs, new Path(args[0]));
fs.close();
}
private static void printFileStatus(FileSystem fs, Path root) throws IOException {
FileStatus[] fss = fs.listStatus(root);
for (FileStatus status : fss) {
if (status.isDirectory()) {
printFileStatus(fs, status.getPath());
} else {
System.out.println(
sdf.format(new Date(status.getAccessTime())) + " "
+ sdf.format(new Date(status.getModificationTime())) + " "
+ Path.getPathWithoutSchemeAndAuthority(status.getPath()));
}
}
}
}
And, in order to enable access time, you may need to set dfs.namenode.accesstime.precision an appropriate value (set 0 by HDP default). <property>
<name>dfs.namenode.accesstime.precision</name>
<value>3600000</value>
</property>
... View more
04-15-2018
10:31 AM
So, still only way right now is to use REST API? any developments on the subject?
... View more
10-20-2017
06:18 AM
Thanks @Timothy Spann for this answer, I was wondering which parameter in the nifi propertiescontrols size of the Event Driven Thread Pool ?
... View more
04-20-2017
01:00 PM
, I had the same problem. Check : https://issues.apache.org/jira/browse/HIVE-16398 and https://issues.apache.org/jira/browse/AMBARI-9821 There is a problem with hive.aux.jars.path
... View more
06-15-2016
10:50 PM
2 Kudos
Cdc is cool and coming
... View more
06-15-2016
05:11 PM
3 Kudos
Check out the ControlRate processor https://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi.processors.standard.ControlRate/index.html and a backpressure feature of NiFi https://nifi.apache.org/docs/nifi-docs/html/getting-started.html#connecting-processors
... View more
06-15-2016
02:23 PM
1 Kudo
NiFi processors have their own transaction concept called a session. Each processor starts a session, performs one or more operations, and then commits or rolls back the session. You can see the general idea in the AbstractProcessor that many processors extends from: https://github.com/apache/nifi/blob/master/nifi-api/src/main/java/org/apache/nifi/processor/AbstractProcessor.java
... View more
- « Previous
- Next »