[RTFACT-14407] External User Plugin Dependencies do not propagate correctly to secondary nodes in HA configurations Created: 18/Jun/17  Updated: 25/Feb/19  Resolved: 25/Feb/19

Status: Resolved
Project: Artifactory Binary Repository
Component/s: Plugins
Affects Version/s: 5.3.0, 5.3.2
Fix Version/s: 6.6.0

Type: Bug Priority: High
Reporter: Loren Yeung Assignee: Dudi Morad (Inactive)
Resolution: Fixed Votes: 5
Labels: None

Issue Links:
Dependency
is a precondition for RTFACT-15640 User plugin dependencies do not get p... Open
is a precondition for RTFACT-12618 Reload existing jars when reloading p... Resolved
Relationship
is related to RTFACT-14958 Configuration file sync fails for emp... Open
Assigned QA: Konstantin Shenderov (Inactive)
Sprint: Leap 32, Leap 33

 Description   

External dependencies placed in $art_home/etc/plugins/lib, like Jar files, are not replicated correctly, the file is usually a partial, much smaller size (about half) on secondary nodes.

Steps to reproduce:
1. On Primary Node, place Jar file into dir, (I did it using curl), file size should be normal.
2. HA will begin to sync the file over immediately to other nodes, in the corresponding directories ($second_node_art_home/etc/plugins/lib)
3. Check secondary node's $art_home/etc/plugins/lib, the file will be there, but a smaller size. Restarting the secondary, or deleting the file will only result in the partial file being downloaded to it again. No fix other than manually moving the file over to secondary nodes.

Note: this occurs more frequently than not, especially with files over the size of 10MB, and over slower connections. Was able to do reproduce with files as small as 57 KB.

This can also happen on the primary, if the customer is starting with a (mostly) clean Artifactory home when doing an upgrade (download new Art version -> copy old config files, but not plugins dep. into new home, start Art), so the node will pull the files from the DB, and end up in the bad state.

Workaround:
Leave the corrupt files intact and also place the same files with a different name on the node.



 Comments   
Comment by Gal Ben Ami [ 10/Jun/18 ]

Seems like this was resolved on earlier versions.
Reproduced on 5.3.4 but could not on current 6.x version.

Comment by Dudi Morad (Inactive) [ 25/Feb/19 ]

Fix Notes:

Please upgrade to 6.6.0 to fix this issue, fixed as part of https://www.jfrog.com/jira/browse/RTFACT-15849.
Fixed case where file content written as String instead of bytes

Generated at Tue Jan 21 16:04:49 UTC 2020 using JIRA 7.6.16#76018-sha1:9ed376192612a49536ac834c64177a0fed6290f5.