Hi,

Glad it helped! Also note the fix has already been merged to 1.2.0

Cheers

On 6 Apr 2017 11:53, "尹文才" <batman...@gmail.com> wrote:

> Hi Arnaud and Andre, thanks very much for your help, now the NiFi cluster
> is able to start up very fast after updating the bootstrap.conf to use
> /dev/./urandom as an extra Java parameter. Let's just hope the fix for the
> problem will be included in later NiFi version(1.2.0?).
>
> 2017-04-05 20:22 GMT+08:00 Arnaud G <greatpat...@gmail.com>:
>
>> Hi!
>>
>> We had the same problem on Openstack (on clustered and non clustered
>> instances) and the problem can easily be solved by changing the entropy
>> source to /dev/urandom in the Java security parameters.
>>
>> Regards,
>>
>> On Wed, Apr 5, 2017 at 1:07 PM, 尹文才 <batman...@gmail.com> wrote:
>>
>>> Thanks Andre, you mean the slow startup of NiFi secure cluster on
>>> openstack currently could be remedied by updating bootstrap.conf to
>>> instruct NiFi to use */dev/urandom, I will give it a try tomorrow. By
>>> the way, NiFi starts up very slow in standalone mode as well when deployed
>>> on openstack environment, according to my test, I had deployed a single
>>> fresh NiFi node(non-secure) on openstack and it took around 7 minutes to
>>> get up. Do you have any ideas of this problem?*
>>>
>>> 2017-04-05 17:48 GMT+08:00 Andre <andre-li...@fucs.org>:
>>>
>>>> Hi,
>>>>
>>>> Sorry for the abrupt message it was sent before I finished typing... :-)
>>>>
>>>> Some users have issues due to lack of entropy within the VMs. This was
>>>> covered on 1.2.0-SNAPSHOT but users of old versions may need to configure
>>>> entropy options manually.
>>>>
>>>> Let me know if it helps.
>>>>
>>>> Kind regards
>>>>
>>>> On Wed, Apr 5, 2017 at 7:45 PM, Andre <andre-li...@fucs.org> wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> Can you please try the fix discussed here:
>>>>>
>>>>> https://issues.apache.org/jira/browse/NIFI-3313
>>>>>
>>>>> Kind regards
>>>>>
>>>>> On Wed, Apr 5, 2017 at 7:36 PM, 尹文才 <batman...@gmail.com> wrote:
>>>>>
>>>>>>   Hi guys, I have been using apache nifi since version 0.7 and as I
>>>>>> know from my previous experiences that nifi should be up and running in
>>>>>> less than 1 minute(standalone mode). Recently my company has switched 
>>>>>> from
>>>>>> running in Vmware ESXI to openstack and thus I reinstalled nifi 1.1.2 in
>>>>>> openstack virtual machines(2 nodes cluster). To my surprise, nifi started
>>>>>> up very slow and it almost took 6-7 minutes which is much slower than
>>>>>> before.
>>>>>>
>>>>>>   I actually was not very familiar with openstack and it was setup
>>>>>> and configured by someone else, but I know that there're 2 network
>>>>>> interfaces for the virtual machine, one is an internal IP(10.0.0.*, for
>>>>>> communication with machines inside openstack) and the other one is an
>>>>>> external IP(192.168.227.*, for communication with office network, I use
>>>>>> this IP to access the nifi web UI)
>>>>>>
>>>>>>   I then decided to check the logs(nifi-app.log) and I found that it
>>>>>> took the most time between the following 2 log lines:
>>>>>>
>>>>>> 2017-04-05 16:59:09,162 INFO [main] 
>>>>>> o.a.nifi.properties.NiFiPropertiesLoader
>>>>>> Loaded 121 properties from /usr/local/nifi/./conf/nifi.properties
>>>>>> 2017-04-05 17:03:48,810 INFO [main] 
>>>>>> o.a.n.admin.AuditDataSourceFactoryBean
>>>>>> Database not built for repository:
>>>>>>
>>>>>>   but the logs didn't give me any useful clues why it would be so
>>>>>> slow. So i dived into nifi's source code and tried to debug to find out
>>>>>> the reason, it appeared to me that the application spent the most
>>>>>> time at start method of class JettyServer when it tries to start the
>>>>>> jetty server:
>>>>>>
>>>>>> // start the server
>>>>>> server.start();
>>>>>>
>>>>>>   I checked the time it took to start the NiFi server in the log:
>>>>>>
>>>>>> 2017-04-05 17:08:55,149 INFO [main] org.apache.nifi.NiFi Controller 
>>>>>> initialization took 590449683493 nanoseconds.
>>>>>>
>>>>>>
>>>>>> the time '*590449683493 nanoseconds*' equals approximately to 10 minutes.
>>>>>>
>>>>>> I'm also not very familiar with Jetty, not sure what's going on here. 
>>>>>> Did anyone come across this slow
>>>>>>
>>>>>> startup issue or does anyone have any idea of this problem? Thanks.
>>>>>>
>>>>>> btw, I've attached the logs.
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>>
>>
>

Reply via email to