I've only done it against Solr cloud, but I don't know a reason why it
wouldn't work against standalone Solr.
Nothing is jumping out at me as being wrong with your config. My JAAS
config was the following:
SolrJClient {
com.sun.security.auth.module.Krb5LoginModule required
useKeyTab=true
When attempting to use the putsolrcontentstream (Version 1.6.0) to load json
file into a Solr 6.3 cluster that requires Kerberos authentication.
I have set the -D java.security.auth.login.config=/disk-1/nifi/jaas/jaas.conf
And the jass file looks like this -
MicroServicesSolrClient {
We are running into issues with NiFi not allowing secure connections in a
container due to the proxy...the only documentation we've found on this
involves whitelisting specific proxy addresses. Is this the only solution?
Specifically, we're concerned about the fact that we don't know the proxy
Vijay
What mechanism are you using to login to NiFi?
Thanks
On Fri, Oct 12, 2018 at 10:37 AM Vijay Chhipa wrote:
>
> Hello
>
> I can't find the 'logout' link on the canvas or under my profile name or in
> the hamburger menu.
> Whats the recommended way to logout of Apache NiFi
>
> Can you
Hello
I can't find the 'logout' link on the canvas or under my profile name or in the
hamburger menu.
Whats the recommended way to logout of Apache NiFi
Can you please point me to this link on a screenshot or if its somewhere in the
docs a pointer to that is highly appreciated.
Thanks
Hi Lee,
Thanks for the link to that thread, it was one of the ones I had gone through
before posting here. I don't think it works for me in my use case, though,
since I have a JSON string coming in to both the Process Group and the Merge
Content, I modify the flow file in the process group to
It very well could become a problem down the road. The reason ZooKeeper is
usually on a dedicated machine is that you want it to be able to have
enough resources to always communicate within a quorum to reconcile
configuration changes and feed configuration details to clients.
That particular
Another thing is that you can also have the process add a period to the
start of the filename to hide them until they're done being written and can
be renamed, if you want to be extra safe.
On Fri, Oct 12, 2018 at 10:01 AM Aldrin Piri wrote:
> Hi Tom,
>
> You can make use of the minimum file
Hi Tom,
You can make use of the minimum file age property on ListFile to ignore a
file until it has reached the desired 10 minute buffer.
On Fri, Oct 12, 2018 at 9:59 AM Tomislav Novosel
wrote:
> Hi Nifi team,
>
> my usecase is to list files and fetch files using ListFile and FetchFile
>
Hi Nifi team,
my usecase is to list files and fetch files using ListFile and FetchFile
processors from intermediate folder which is also destination of my
external .exe script.
Fetching from that folder has completion strategy to delete files.
How can I wait for let's say 10 minutes before
Thanks Mike. We will get an external ZooKeeper instance deployed. I guess
co-locating it with one of the NiFi nodes shouldn’t be an issue, or will it? We
are chronically short of hardware. BTW, does the following message in the logs
point to some sort of problem with the embedded ZooKeeper?
Also, in a production environment NiFi should have its own dedicated
ZooKeeper cluster to be on the safe side. You should not reuse ZooKeeper
quora (ex. have HBase and NiFi point to the same quorum).
On Fri, Oct 12, 2018 at 8:29 AM Mike Thomsen wrote:
> Alexander,
>
> I am pretty sure your
Alexander,
I am pretty sure your problem is here:
*nifi.state.management.embedded.zookeeper.start=true*
That spins up an embedded ZooKeeper, which is generally intended to be used
for local development. For example, HBase provides the same feature, but it
is intended to allow you to test a real
nifi.cluster.node.protocol.port=11443 by default on all nodes, I haven’t
touched that property. Yesterday, we discovered some issues preventing two of
the boxes from communicating. Now, they can talk okay. Ports 11443, 2181 and
3888 are explicitly open in iptables, but clustering still doesn’t
14 matches
Mail list logo