Ive got a wks/offline server scenario where reverse DNS doesn't work and things like the online Usage help and processor state don't update in a similar way. If I was to guess it'd be something like a recent jetty upgrade behaving differently; but just a guess. When the 30s timeout occurs, things render as expected.
It's also a pain trying to drag connectors into a funnel, that processor type in particular has difficulty turning green. On Mon, 21 Aug 2023, 23:41 Russell Bateman, <r...@windofkeltia.com> wrote: > Thanks, Matt. This is happening locally during development where I'm not > using DNS (just localhost). I find this problem less acute on older > versions of NiFi (1.1.3.2) than more recent ones (1.23.0, 1.19.1). > > Thanks, > Russ > > On 8/20/23 19:03, Matthew Hawkins wrote: > > Hi Russell, > > > > Something I've noticed myself, and it's easily reproducible on the Usage > > pages for processors, is that Nifi is doing a reverse DNS lookup when > > loading the page. If your DNS is broken, it can take 10-30 seconds for > the > > page content to appear. > > > > Kr, > > > > On Fri, 18 Aug 2023, 07:29 Russell Bateman,<r...@windofkeltia.com> > wrote: > > > >> Matt, > >> > >> I experimented with the Open in New Window button, but the new window, > >> which probably isn't an iframe, nevertheless doesn't respond to attempts > >> to get around the cache. > >> > >> You're probably right about the version not changing being at the root > >> of the browser's inability to respond to a change. Sadly, the > >> edit-display-debug-edit cycle doesn't excite me into changing versions > >> just so I can see the result. > >> > >> I'm certainly not going to clamor for work to be done to get around > >> this. It's annoying, but not crippling. > >> > >> Thanks, > >> > >> Russ > >> > >> > >> On 8/17/23 13:54, Matt Gilman wrote: > >>> Russell, > >>> > >>> Thanks for the response. The suggestion to open a new tab was for the > >>> generated documentation, not the NiFi canvas itself. The generated > >>> documentation is shown in an iframe which will offer you the menu item > in > >>> the context menu for opening in a new tab. IIRC correctly, the path to > >> the > >>> generated documentation contains the version of the component. For > folks > >>> simply using a released version of NiFi this works great since versions > >>> will differ and any browser caching will only optimize page loading for > >> the > >>> user. If you're a developer, however, you're likely making changes to > >> your > >>> component and the version is not changing (x.y.z-SNAPSHOT). This is > where > >>> the browser cache could result in the behavior your seeing. > >>> > >>> Matt > >>> > >>> On Thu, Aug 17, 2023 at 3:21 PM Russell Bateman<r...@windofkeltia.com> > >>> wrote: > >>> > >>>> Thanks, Matt, > >>>> > >>>> (Since I use Chrome 99% of the time, I'm using Chrome here.) > >>>> > >>>> Clicking on the reload control next to the address bar, while holding > >>>> down Shift, reloads the canvas, but the NiFi Documentation page > >>>> disappears and I have to reload it using the View usage context menu > of > >>>> my processor. Once reloaded, nothing has changed. > >>>> > >>>> This is also the behavior of the Configure Processor dialog. As I > reload > >>>> View usage, ... > >>>> > >>>> In Chrome, there's no effective content-menu option to right-click in > >>>> the page contents and open in a new tab. I can... > >>>> > >>>> Back > >>>> Forward > >>>> Reload > >>>> ----------- > >>>> Save As... > >>>> Print > >>>> Cast > >>>> Search images with Google > >>>> ------------------------- > >>>> Send to your devices > >>>> Create QR code for this page > >>>> ---------------------------- > >>>> Translate > >>>> --------- > >>>> View page source > >>>> View frame source > >>>> Reload frame > >>>> Inspect > >>>> > >>>> > >>>> If I right-click the current tab itself, I'm able to choose to > >>>> Duplicate., but that doesn't seem to lead to anything more helpful. > >>>> > >>>> By the way, I'm doing this using NiFi 1.23.0. I have also verified the > >>>> date of my NAR to ensure that I'm not repeatedly working using a NAR > >>>> with old content. Also, the version displayed for the custom processor > >>>> is that of the various /pom.xml/ files I'm building with. > >>>> > >>>> I usually develop on the latest NiFi version. However, my company has > >>>> NARs that won't load beginning 1.14.0. I just brought up 1.13.2, what > >>>> most of our customers run, and tried my latest NAR which *does* > display > >>>> my changes.Same with 1.1.2, which represents the oldest platform > >>>> executing at any custom site. Exceptionally, I set up 1.19.1 where it > >>>> *also works*. > >>>> > >>>> This is unexpected; maybe it does point, as unlikely as it seems, to > >>>> something changed in 1.23.0 (instead of being caused by anything > between > >>>> the dossier of my chair and the space bar of my keyboard as I have > been > >>>> expecting to learn. ;-) ) > >>>> > >>>> It could still be me and I'm just not seeing the obvious yet. > >>>> > >>>> > >>>> On 8/17/23 12:44, Matt Gilman wrote: > >>>>> Russell, > >>>>> > >>>>> Assuming this is a browser cache issue, can you try right-clicking > >>>> anywhere > >>>>> in the page contents of the generated documentation and open it in a > >> new > >>>>> tab. Once that is open, can you try doing a hard refresh by holding > >> Shift > >>>>> while clicking Reload next to the address bar? This should clear the > >>>> cache > >>>>> and fetch the updated generated documentation. At this point, you > >> should > >>>> be > >>>>> able to close that tab and retry from the NiFi UI. > >>>>> > >>>>> Let us know if this doesn't help and we can see if something isn't > >>>> getting > >>>>> generated and updated correctly. > >>>>> > >>>>> Matt > >>>>> > >>>>> On Thu, Aug 17, 2023 at 2:38 PM Russell Bateman< > r...@windofkeltia.com> > >>>>> wrote: > >>>>> > >>>>>> Seems like a really stupid user/browser question, but I cannot seem > to > >>>>>> get changes I've made to properties, relationships, attributes read > or > >>>>>> written, etc. *for custom processors*. Also, from the Properties tab > >> in > >>>>>> Configuring Processor, the cartoon blurbs obtained by hovering over > >> (?) > >>>>>> aren't updated either. > >>>>>> > >>>>>> This is despite that changes I make to my /additionalDetails.html/ > >> files > >>>>>> come through with no problem. > >>>>>> > >>>>>> I have tried Chrome, Opera, Brave and Firefox. All [mis]behave > >>>> identically. > >>>>>> I have tried killing the browser running the NiFi UI, stopping also > >> the > >>>>>> NiFi instance, relaunching NiFi, quickly asking the browser to > display > >>>>>> the canvas, then holding down the Ctrl key as I click Reload. > >>>>>> > >>>>>> In past times, I have observed that eventually the changes are > >>>>>> recognized and displayed, so this is not permanent, however, it's > very > >>>>>> annoying especially when I'm polishing my processor documentation > >>>>>> wording in the class that extends AbstractProcessor. All the while, > >> as I > >>>>>> say, the processor's corresponding /additionalDetails.html/ displays > >>>>>> changes I make to it in a timely and accurate fashion. > >>>>>> > >>>>>> Suggestions? >
