This is an automated email from the ASF dual-hosted git repository.

joewitt pushed a change to tag HDF-3.3.1.35-7-tag
in repository https://gitbox.apache.org/repos/asf/nifi.git


*** WARNING: tag HDF-3.3.1.35-7-tag was deleted! ***

     was c22ea1c626 HOTFIX-3868 NIFI-5905 Secure S2S fails with 
NullPointerException

This change permanently discards the following revisions:

 discard c22ea1c626 HOTFIX-3868 NIFI-5905 Secure S2S fails with 
NullPointerException
 discard 2b73dd092d HOTFIX-3472: Contains the following changes:
 discard 7f3aafb7af HOTFIX-3472 NIFI-7023 This closes #3991. Removed SLF4J and 
Log4J transitive dependencies from Zookeeper so tests log correctly. Changed 
template handling. Added unit tests.
 discard ed83f27d0a HOTFIX-3472 NIFI-7117: When SocketLoadBalancedFlowFileQueue 
creates its array of Queue Partitions in the constructor, it added the local 
partition as the first element in that list. This list should be ordered the 
same across all nodes in the cluster. By making the local partition the first 
in the array, each node had a different ordering of these partitions. As a 
result, Partition by Attribute strategy would constantly rebalance flowfiles 
that it received to other nod [...]
 discard 40ef1c50c6 HOTFIX-3472: NIFI-7076: This closes #4024. Revert 
"NIFI-6787 - Before: When checking if a load balanced connection queue is full, 
we compare the totalSize.get() and getMaxQueueSize()."
 discard b925490303 HOTFIX-3472: NIFI-6787: Added a comment to the UI tooltip, 
user guide, and javadocs to indicate that round robin may skip a node if that 
node is not receiving the data as fast as other nodes in the cluster, in order 
to maximum throughput.
 discard 91455eddf7 HOTFIX-3472: NIFI-6787 - Before: When checking if a load 
balanced connection queue is full, we compare the totalSize.get() and 
getMaxQueueSize(). After: Go over all partitions and see if all of them are 
full. Wrapping RoundRobinPartitioner in a (new) AvailableSeekingPartitioner 
which selects a new partition if the currently selected one is full.
 discard a76f641679 HOTFIX-3472: NIFI-6760: When writing/reading the length of 
a DataFrame, do so usin… (#3801)
 discard a8bb65c369 HOTFIX-3472: NIFI-6759: When encountering Exception during 
load-balanced connection communications, after closing socket, return from 
method rather than continuing loop
 discard da03008314 HOTFIX-3472: NIFI-6736: Create thread on demand to handle 
incoming request from client for load balancing. This allows us to avoid 
situations where we don't have enough threads and we block on the server side, 
waiting for data, when clients are trying to send data in another connection
 discard b7fa049636 HOTFIX-3472: NIFI-6696: Ensured that callback to 
RemoteQueuePartition do not attempt to obtain the Partition Read Lock. The Read 
Lock is not necessary as long as the 'partitioner' is volatile, because it 
doesn't matter whether or not the actual partitions themselves change, since 
the only partition that would be touched is the Rebalancing Partition,on, which 
is fixed. Obtaining the partition read lock can lead to a deadlock as outlined 
in the Jira description.
 discard e5e8c81f9c HOTFIX-3472: NIFI-6517: Ensure that if IOException is 
thrown from LoadBalanceSession that we properly catch the Exception, mark 
session as complete, and then re-throw. There was one condition in which this 
was not occurring. This commit addresses that situation.
 discard b0b5a7d358 HOTFIX-3472: NIFI-6353: If LoadBalanceSession determines 
remote node's queue is full, mark session complete and penalize the Partition, 
rather than just penalizing the session. This allows the client to move on to 
another session, which avoids an issue where backpressure on one queue can 
prevent data from being transferred between nodes in another queue
 discard 0106270392 HOTFIX-3475: NIFI-6285: Addressed issue that resulted in 
swapped data not being swapped back in if load balancing strategy changed while 
data was swapped out; added integration tests for swapping. In testing, also 
encountered an issue with data being swapped out while swap files were being 
recovered causing the queue size to be wrong and causing errors about not being 
able to swap data in, because it attempted to swap the data in twice.
 discard efb2bc9766 HOTFIX-3472: NIFI-6017 - ArrayIndexOutOfBounds Load 
Balancer CorrelationAttributePartitioner
 discard ac1b9d9aad HOTFIX-3472: NIFI-5997: Recover FlowFile Repository before 
swap files; then, when recovering swap files, ignore any that are unknown to 
the flowfile repo. This prevents us from incrementing the size of the flowfile 
queue for unknown swap files
 discard f4dd26f059 HOTFIX-3472: NIFI-5997: If we swap out data, ensure that we 
do not increment the size of the queue by the size of the data that we failed 
to swap out. Also, if the FlowFile Repo does not know about a given swap file, 
do not restore it on restart
 discard 7ccd0a6c55 HOTFIX-3472: NIFI-5919: Addressed a race condition that can 
exist if adding FlowFiles to a FlowFileQueue before adjusting the size of the 
queue to account for the FlowFiles
 discard 78a4aedf14 HOTFIX-3472: NIFI-5752: Load balancing fails with wildcard 
certs
 discard 5b5b780f8f HOTFIX-3472: NIFI-5769: Refactored FlowController to use 
Composition over Inheritance - Ensure that when root group is set, that we 
register its ID in FlowManager
 discard f251020ccf HOTFIX-3472: NIFI-5673 Set up property/assembly for new 
auto-load directory - Set up NarAutoLoader to watch directory for new files - 
Move NarAutoLoader to JettyServer since it will need access to ExtensionManager 
- Created NarLoader to shared between NarAutoLoader and the framework - Created 
nifi-framework-nar-loading-utils so we can use nifi-documentation to call 
DocGenerator - Add additional bundles to overall map in NarClassLoaders as they 
are loaded - Added handli [...]
 discard 43ff0593fb NIFI-6846: Updated variable name after cherry-picking commit
 discard 1dd2b0a465 NIFI-6846: If an Exception is thrown while a Processor is 
writing to a FlowFile, but that Content Claim is not yet eligible for 
destruction, mark it as a transient claim on the RepositoryRecord so that if 
it's available when the FlowFile Repository is checkpointed, then it will be 
cleaned up then

Reply via email to