RE: Problem Debugging InvokeHTTP Processor in Nifi 1.8.0

e FlowFile, then sending that to the InvokeHTTP processor. Thanks -Mark On Nov 16, 2018, at 3:29 PM, Williams, Jim mailto:jwilli...@alertlogic.com> > wrote: Hey Mark, Replication is problematic, since the HTTP server I am accessing is internal to my company. Howev

RedisConnectionPoolService - Incorrectly Attempts to Connect to localhost

Hello, I'm trying to set up the RedisConnectionPoolService/RedisDistributedMapCacheClientService. Some basic observations: * This is a standalone Nifi 1.8.0 server * SELinux is disabled on the server * There are no iptables rules configured for blocking on the server *

Re: Empty "nifi users" page.

Matt, I think the JIRA you filed may be substantially similar to NIFI-5636 I filed a little while ago. I'm not sure if there is a process for de-duplication, if they do turn out to be the same? https://issues.apache.org/jira/browse/NIFI-5636 Warm Regards, Jim Williams

Re: DistributeLoad across a NiFi cluster

Edward, Documentation on this feature may be found here: https://nifi.apache.org/docs/nifi-docs/html/user-guide.html#settings Warm regards, Jim Williams From: Edward Armes Sent: Thursday, July 4, 2019 5:54 AM To: users@nifi.apache.org Subject: Re:

RE: Kafka to parquet to s3

afka to parquet to s3 Thanks Jim for the insights on advantages, this worked for me as well. Any thoughts on partitioning and filesize so the S3 PUT costs are not too high? I do not see options on the convertavrotoparquet for this -Dweep On Mon, Jul 8, 2019 at 6:09 PM Williams,

RE: NiFi cluster heavy cpu usage

Lei, I have seen this on 1.9.2 standalone and cluster deployments. Every time I have seen this so far, the reason has been an input port in a process group which is not connected by an output port. The input port can be identified in the user interface by drilling down to the active thread.

RE: Kafka to parquet to s3

Dweep, I have been working on a project where Parquet files are being written to S3. I’ve had the liberty to use the most up-to-date version of Nifi, so I have implemented this on 1.9.2. The approach I have taken is something like this: (Get stuff in JSON format) --> ConvertRecord

RE: Content Claims Filling Disk - Best practice for small files?

Ryan, Is this this maybe a case of exhausting inodes on the filesystem rather than exhausting the space available? If you do a ‘df -I’ on the system what do you see for inode usage? Warm regards, [cid:image001.jpg@01D68CDD.FC463950] Jim Williams | Manager, Site