-
Notifications
You must be signed in to change notification settings - Fork 3
/
release-notes-2.16
4397 lines (2803 loc) · 187 KB
/
release-notes-2.16
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
HTML header: <title>dCache 2.16 Release Notes</title>
<!--#include virtual="/template/default-head.shtml" -->
<meta name="viewport" content="width=device-width, initial-scale=1.0"/>
<!-- Bootstrap -->
<link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.6/css/bootstrap.min.css"
integrity="sha384-1q8mTJOASx8j1Au+a5WDVnPi2lkFfwwEAa8hDDdjZlpLegxhjVME1fgjWPGmkzs7" crossorigin="anonymous"/>
<link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.6/css/bootstrap-theme.min.css"
integrity="sha384-fLW2N01lMqjakBkx3l/M9EahuwpSfeNvV63J5ezn3uZzapT0u7EYsXMjQV+0En5r" crossorigin="anonymous"/>
<!--link type="text/css" rel="stylesheet" href="jquery.tocify.css" /-->
<style type="text/css">
h5 {
font-size: 15px;
font-style: italic;
margin-top: 20px;
}
body {
padding-top: 20px;
}
@media (max-width: 767px) {
#toc {
position: relative;
width: 100%;
margin: 0px 0px 20px 0px;
}
}
@media print {
#toc {
display: none;
}
}
</style>
<div class="container">
<div id="banner">
<div id="bird_large">
<img src="/images/dcache-banner.png" class="bird"></img>
</div>
<div id="sidebar-b">
<span class="dcache-nav-bar">
<a href="/index.shtml">home</a>
|
<a href="/news.shtml">news</a>
|
<a href="/manuals/index.shtml">documentation</a>
|
<a href="/downloads/IAgree.shtml">downloads</a>
|
<a href="/feedback.shtml">feedback</a>
|
<a href="/manuals/googlesearch.shtml">search</a>
|
<a href="/imprint.shtml">imprint </a>
</span>
</div>
</div>
<div id="content">
<div class="row">
<div class="page-header">
<h1>What's new in dCache 2.16<br/>
<small>The release notes</small></h1>
</div>
## Highlights
* New experimental RESTful API.
* New experimental end user web interface called dCacheView.
* New experimental support for redundant cell communication using
multiple message brokers.
* New resilience service for managing file replicas. Will eventually
replace the replica manager.
* New experimental support for replicable services.
* Scalable SRM frontend service.
* Limited OpenID Connect support.
## Incompatibilities
* Apache ZooKeeper is now a required dependency.
* Several database schemas will be updated upon upgrade. This includes
billing and pinmanager. Upon downgrade, these schemas must be rolled
back using the `dcache database rollbackToDate` command *prior* to
downgrading dCache. Third party code that uses these database will
possibly have to be modified.
* The dCache location manager can no longer be configured to establish
arbitrary topologies.
* The `srm` service was split into two services - a frontend service
called `srm` and a backend service called `srmmanager`. Both are
required to operate an SRM service in dCache.
* Support for the SRM 1 protocol has been dropped.
* The FTP door's default root path behavior now matches that of
other doors. That is, it no longer uses the per user root setting
as the root directory. The original behavior can be restored
by appropriate configuration.
* The `RemoteTransferManager` and `CopyManager` cells of the
`transfermanagers` service have been merged.
* Sites with a custom `httpd.conf` configuration will have to adjust
this upon upgrade to inject the cell address of the `info` service.
## Differences from dCache v2.15
The notes for [release 2.16.0](#release2.16.0) detail the differences
from dCache 2.15. Please read this section *very carefully* when
upgrading from this version.
## Release 2.16.66
### scripts
The instructions that are printed out once `dcache pool convert`
completes successfully now correctly point to the
property that needs to be updated, namely `pool.plugins.meta`.
### Changelog 2.16.65..2.16.66
<!-- git log 2.16.65..2.16.66 -no-merges -format='[%h](https://github.com/dcache/dcache/commit/%H)%n: %s%n' -->
[f1b41a2393](https://github.com/dcache/dcache/commit/f1b41a2393b21f142605c4a6ce22f6015d9c3e5c)
: [maven-release-plugin] prepare release 2.16.66
[ee58228c14](https://github.com/dcache/dcache/commit/ee58228c14015d836f1a7d076f89acbde77a10f5)
: scripts: update reference to configuration property
[d0b33fce9b](https://github.com/dcache/dcache/commit/d0b33fce9b09d233d1209861709d026206add1ee)
: [maven-release-plugin] prepare for next development iteration
## Release 2.16.65
### dcache-resilience
There was a small regression in the way resilience computes
the number of operations necessary to adjust copies when
a storage unit definition changes.
The current rellease fixed computation of operation count when storage requirements change.
### ftp
In order to aid diagnosing problems when FTP response being lost, now dcache logs failures to wrap/encrypt responses.
### Changelog 2.16.64..2.16.65
<!-- git log 2.16.64..2.16.65 -no-merges -format='[%h](https://github.com/dcache/dcache/commit/%H)%n: %s%n' -->
[22b932c](https://github.com/dcache/dcache/commit/22b932cafe36dc1b277613789b1720038dc2b331)
: [maven-release-plugin] prepare release 2.16.65
[a1e22fe](https://github.com/dcache/dcache/commit/a1e22feae7b9251a2b7fb15709af4664802066f5)
: scripts: add support for parsing ZooKeeper transaction logs
[8b7354a](https://github.com/dcache/dcache/commit/8b7354adf6d952fb38696221bf8b539cd401d144)
: ftp: log failures to wrap/encrypt responses
[bab0c9c](https://github.com/dcache/dcache/commit/bab0c9cdca8a858ec0b3b3e4225ef66eecc0ff76)
: dcache-resilience: fix computation of operation count when storage requirements change
[f415195](https://github.com/dcache/dcache/commit/f41519546f1ab4422d71ae3bada00ee7617cb794)
: [maven-release-plugin] prepare for next development iteration
## Release 2.16.64
### ftp
Error reporting in the FTP service has been improved: in some mixed IPv4 / IPv6 scenarios,
only unclear error messages were reported.
### Changelog 2.16.63..2.16.64
<!-- git log 2.16.63..2.16.64 -no-merges -format='[%h](https://github.com/dcache/dcache/commit/%H)%n: %s%n' -->
[5c05ba0cf5](https://github.com/dcache/dcache/commit/5c05ba0cf59ea1f8881fb51d35faeb11df765139)
: [maven-release-plugin] prepare release 2.16.64
[dde92b3fae](https://github.com/dcache/dcache/commit/dde92b3faebe13a92fa781df1deccd043b05d324)
: ftp: returned error is too vague for meaningful investigation
[aa68760e98](https://github.com/dcache/dcache/commit/aa68760e986955cac4f45a87ff6412e71a64f307)
: [maven-release-plugin] prepare for next development iteration
## Release 2.16.63
### gplazma
gplazma now supports a Fermilab-specific authorization data source in JSON format.
### pool
During active ftp transfers, connection problems would lead to the rather unhelpful error
message "451 General problem". This error reporting was refactored, so that diagnosis
of the cause is now greatly facilitated.
### poolmanager
A potential NullPointerException (that was not observed in real-world usage until now)
was fixed in Pool Manager.
### resilience
A correction to resilience's error handling results in no more reports on
non-resilient (but corrupted) files.
### spacemanager
In order to facilitate debugging, Space Manager now logs link-group related content
in greater detail.
### Changelog 2.16.62..2.16.63
<!-- git log 2.16.62..2.16.63 -no-merges -format='[%h](https://github.com/dcache/dcache/commit/%H)%n: %s%n' -->
[99ff6e5b70](https://github.com/dcache/dcache/commit/99ff6e5b703949a1cd3339f0c7a221024ee257f8)
: [maven-release-plugin] prepare release 2.16.63
[bf97198b25](https://github.com/dcache/dcache/commit/bf97198b258818797ed24a6a3f65cea67100b368)
: poolmanager: fix migration command if named pool is removed
[1656cb63d5](https://github.com/dcache/dcache/commit/1656cb63d5a1f8f7072d31634e169f54726a1349)
: dcache-resilience: repair over-aggressive handling of broken file messages
[ac2bc68cf7](https://github.com/dcache/dcache/commit/ac2bc68cf792125207546b215ed3731b20305da9)
: pool: fix error message for failed active FTP transfers
[5cc6fd8750](https://github.com/dcache/dcache/commit/5cc6fd875061ca481fe6c66202a1759dedd1a2ec)
: correct the project version in pom.xml
[525ba8f80b](https://github.com/dcache/dcache/commit/525ba8f80b43ea7def8864166095af0bd6cb9191)
: set project version
[6ea80f7843](https://github.com/dcache/dcache/commit/6ea80f7843883ece757b3b85f5ab5ff3c3819b74)
: gplazma-fermi: fix last modified check in junit test
[9ddefe4776](https://github.com/dcache/dcache/commit/9ddefe477678f70a55cf4c9a1b092db6721ecad6)
: spacemanager: add remote pool monitor debug logging
[6c2e08afaa](https://github.com/dcache/dcache/commit/6c2e08afaa4dbd77f4df748315be967909f50d5e)
: gplazma-fermi: add mapping plugin to support VO group and username from file
[3f2dbbfdb6](https://github.com/dcache/dcache/commit/3f2dbbfdb6201bdd38a0c816be05eff3eb34222f)
: [maven-release-plugin] prepare for next development iteration
## Release 2.16.62
### resilience
Logging for cases where file replication was fatally aborted was improved. Previously, alarms
messages pertained to the PNFSID of the affected files. In rare cases, like when facing
network congestion, many hundreds of alarms could be created. With this change, alarms messages
refer to the storage unit, and a suffix based on an hourly timestamp is added to the
alarm message. The alarm will thus be incremented during the hour but a new
alarm will be created (only) hourly; in this way, those receiving
email alerts will receive them once an hour.
### Changelog 2.16.61..2.16.62
<!-- git log 2.16.61..2.16.62 -no-merges -format='[%h](https://github.com/dcache/dcache/commit/%H)%n: %s%n' -->
[ca403db91f](https://github.com/dcache/dcache/commit/ca403db91fdfce473bedbb72102ac1f7e50cd812)
: [maven-release-plugin] prepare release 2.16.62
[da3ba6f48f](https://github.com/dcache/dcache/commit/da3ba6f48fb7f18453891b0340c2568047ecf7e3)
: [maven-release-plugin] prepare for next development iteration
[5dab91daa9](https://github.com/dcache/dcache/commit/5dab91daa9161a9e0ed766a9368d387eb2094d25)
: substituted Calendar for Instance which was failing.
[58004eb269](https://github.com/dcache/dcache/commit/58004eb269456653350e204aafb753e0468f24e1)
: dcache-resilience: avoid spamming alarms with abort messages
## Release 2.16.61
### ftp
A bug (that was not observed in real-world settings yet) that might have caused
NullPointerExceptions was fixed in the ftp service.
### resilience
Error handling within the Resilience service was improved.
### Changelog 2.16.60..2.16.61
<!-- git log 2.16.60..2.16.61 -no-merges -format='[%h](https://github.com/dcache/dcache/commit/%H)%n: %s%n' -->
[787fd2b84a](https://github.com/dcache/dcache/commit/787fd2b84afcad9b8f4bb62cbd93b3e18717c80c)
: [maven-release-plugin] prepare release 2.16.61
[155ac94dd8](https://github.com/dcache/dcache/commit/155ac94dd8166d2df7512534e157bc0e644be777)
: removed stray import
[d3ce544154](https://github.com/dcache/dcache/commit/d3ce54415405beeff00dd0735656ddd5c3538407)
: dcache-resilience: handle properly RuntimeExceptions from tasks
[83435d3188](https://github.com/dcache/dcache/commit/83435d318839b705ffe3ae8cd09ad406b1506d4f)
: ftp: ensure adapter is closed
[f51e086f80](https://github.com/dcache/dcache/commit/f51e086f8079eb90b3dc5cbe66d51cc77b09300e)
: ftp: remove rare NullPointerException when proxying data
[ac26d22940](https://github.com/dcache/dcache/commit/ac26d2294083b9848a46255c9d6bcafdbd642bef)
: [maven-release-plugin] prepare for next development iteration
## Release 2.16.60
### dcache-resilience
When a checksum or broken file message/error is generated,
Resilience makes a best effort to (a) remove the broken
copy and (b) make another replica. This, of course, is not always possible, particularly if
the broken file is the only accessible copy. This resulted in faulty behavior
particularly the thrashing noted in the case of a restaging operation which results in a checksum error.
This is now fixed.
The current release improved error handling for resilience.
It fixed unnecessary Migration Task exceptions resulting from
source pools with no replica in the repository.
Now it should be possible for Resilience to use pools blocked only for
writes from doors.
### Changelog 2.16.59..2.16.60
<!-- git log 2.16.59..2.16.60 -no-merges -format='[%h](https://github.com/dcache/dcache/commit/%H)%n: %s%n' -->
[c94e97d](https://github.com/dcache/dcache/commit/c94e97df75dc46d2495de43e809d49d5ee06e0c6)
: [maven-release-plugin] prepare release 2.16.60
[a2208da](https://github.com/dcache/dcache/commit/a2208dac9bb375321760568b660a71abf10b1ebb)
: bad commit put DOWN twice
[3019c7e](https://github.com/dcache/dcache/commit/3019c7e4bb61a0a0a7dd3e6ddfd362c88159a7be)
: dcache-resilience: define non-writable pool to mean p2p-client is disabled
[5296408](https://github.com/dcache/dcache/commit/52964084f11dbe2cfc62f18a7da088b229599f31)
: dcache: fix remote pool monitor wait bug
[c1a3389](https://github.com/dcache/dcache/commit/c1a3389d833d290ac70142fd9bf5fde6e4e24166)
: dcache-resilience: repair handling of broken files*
[0005651](https://github.com/dcache/dcache/commit/0005651b42fee9d1a98210f3a933bc192fd1e95b)
: [maven-release-plugin] prepare for next development iteration
[1fce35f](https://github.com/dcache/dcache/commit/1fce35f893a2beb17d37f20e047b3602ff4c2846)
: dcache-resilience: fix bug in source handling with Clear Cache Location messages
## Release 2.16.59
### cells
The current release added explicit ZooKeeper/Curator monitoring. Events generated by ZooKeeper and Curator are now logged in a new, which may help diagnose
problems that are suspected to come from bad ZooKeeper interaction.
### Changelog 2.16.58..2.16.59
<!-- git log 2.16.58..2.16.59 -no-merges -format='[%h](https://github.com/dcache/dcache/commit/%H)%n: %s%n' -->
[e6fe17c](https://github.com/dcache/dcache/commit/e6fe17ca9f3849af5d7ed01de3488643777a6ba8)
: [maven-release-plugin] prepare release 2.16.59
[c5916dd](https://github.com/dcache/dcache/commit/c5916ddf5e2599b9507050cf0dd16ba0ee84deab)
: dcache-resilience: fix wrong assumption about error type in Message
[71c377f](https://github.com/dcache/dcache/commit/71c377fc448bad69cd54b117a937cabe0e08e1ff)
: cells: add explicit ZooKeeper/Curator monitoring
[6d78493](https://github.com/dcache/dcache/commit/6d7849372f747707df068dd65f597513be5b0d62)
: [maven-release-plugin] prepare for next development iteration
## Release 2.16.58
### star
The current release improved documentation to help dCache admins to have a better understanding of how to generate StAR record.
The current release fixed fix printing exception error message for dcache-star script if there's a problem when run with newer versions of Python.
### Changelog 2.16.57..2.16.58
<!-- git log 2.16.57..2.16.58 -no-merges -format='[%h](https://github.com/dcache/dcache/commit/%H)%n: %s%n' -->
[e4c262a](https://github.com/dcache/dcache/commit/e4c262adbfd1f2515027b18f9878eaa564a33c92)
: [maven-release-plugin] prepare release 2.16.58
[afcabff](https://github.com/dcache/dcache/commit/afcabffd42482987b754dc5640ba242f44c8088a)
: star: fix printing exception error message
[7982d56](https://github.com/dcache/dcache/commit/7982d564af711f446b5e32c7902ddba40a2ccf40)
: star: update documentation to provide better description of script
[8582150](https://github.com/dcache/dcache/commit/858215053a4969c89dcdacf1c99978405db1cbdf)
: [maven-release-plugin] prepare for next development iteration
## Release 2.16.57
### info
The info service collects information about who is allowed to reserve space.
Since some of this information, like VOs, usernames and gids, may be considered
sensitive information, this update allows admins to control whether or not
to publish them. The default behaviour is unchanged from the previous behaviour,
i.e. info publishes everything. If a site admin wants to change this,
the `info.limits.show-only-vo-authz` property can be set to `true`.
### scripts
The dcache script and manpage still refered explicitely to Java 6. This patch
changes the phrasing of the respective text.
### Changelog 2.16.56..2.16.57
<!-- git log 2.16.56..2.16.57 -no-merges -format='[%h](https://github.com/dcache/dcache/commit/%H)%n: %s%n' -->
[b1e67a165e](https://github.com/dcache/dcache/commit/b1e67a165ea7c5e19b012b0ba91855e0677ba770)
: [maven-release-plugin] prepare release 2.16.57
[ad748c8b9c](https://github.com/dcache/dcache/commit/ad748c8b9c579b1b064a403c57d9063f9843c09c)
: scripts: update reference to JDK to avoid mentioning specific java version
[264901a803](https://github.com/dcache/dcache/commit/264901a80345be3ea37b199df697428d642f1912)
: info: allow admin to control whether non-VO / non-FQAN identities are shown
[a4c2d5e22c](https://github.com/dcache/dcache/commit/a4c2d5e22c5d2f11cf102902726c69cd424621fa)
: [maven-release-plugin] prepare for next development iteration
## Release 2.16.56
### chimera
The current release fixed previously introduced issues for `lost+found` directory permissions.
Now, the `lost+found` directory permissions is updated without causing
problems if that directory has been removed or permissions have been
modified.
### Changelog 2.16.55..2.16.56
<!-- git log 2.16.55..2.16.56 -no-merges -format='[%h](https://github.com/dcache/dcache/commit/%H)%n: %s%n' -->
[cd08165](https://github.com/dcache/dcache/commit/cd081659f8e1ab8552356ed96406fe8bbfb32761)
: [maven-release-plugin] prepare release 2.16.56
[03a7300](https://github.com/dcache/dcache/commit/03a730064df9f139a69dcdb20241129b8a4effd8)
: chimera: correct previous attempt to fix 'lost+found' directory permission
[742ec49](https://github.com/dcache/dcache/commit/742ec4916d11af5cb0e39a32671488a56c823b0a)
: [maven-release-plugin] prepare for next development iteration
## Release 2.16.55
### pnfsmanager
The current release improves documentation for `set log slow threshold` admin command help.
### spacemanager
When trying to upload into dCache using a space-token where there
is no selectable link for this operation then the user was presented with
a generic error message; for example,
`No write links configured for [net=131.169.71.98,protocol=GFtp/2,store=dot:user@osm,cache=,linkgroup=]`.
This behavior is changed now and an improved error message is returned to the user if they attempt an upload data into dCache using a space-reservation in a way where
`poolmanager` configuration prevents the upload.
### webdav
The current release improved error handling when dCache is full.
### Changelog 2.16.54..2.16.55
<!-- git log 2.16.54..2.16.55 -no-merges -format='[%h](https://github.com/dcache/dcache/commit/%H)%n: %s%n' -->
[6f50a50](https://github.com/dcache/dcache/commit/6f50a50cf4515a18fd9662dfdff5057aa71810ea)
: [maven-release-plugin] prepare release 2.16.55
[dd97a05](https://github.com/dcache/dcache/commit/dd97a05b7d0c3cbf4047fe41b16b2fba6206aaae)
: systemtest: work with new OpenSSL DN format
[b61aab6](https://github.com/dcache/dcache/commit/b61aab61caae9e07a079c7d66ab390c76ce209e7)
: spacemanager: provide space-specific error message on bad upload
[fb2285e](https://github.com/dcache/dcache/commit/fb2285ee27ef6951647ba0312722a4058a65fe26)
: webdav: return 507 Insufficient Storage when dCache is full
[3123a7e](https://github.com/dcache/dcache/commit/3123a7e3c694f70f302a76298c6ab43e30d53e4c)
: pnfsmanager: update slow logging admin command help
[b95d321](https://github.com/dcache/dcache/commit/b95d3213cfa2c44e33f156fe517d40e2383715a5)
: [maven-release-plugin] prepare for next development iteration
## Release 2.16.54
### cells
dCache no longer logs stack-traces when running multiple cells with the same name.
### pool
For certain failures,the pool was logging transfer failures twice. This is now fixed.
### rpm
dCache ensures now that user 'dcache' is a member of group 'dcache'.
### star
The current release Introduced new property `star.db.*`, which makes possible now to run PostgreSQL on non-standard ports can use STAR.
### statistics
Timeout in contacting PoolManager no longer results in a stack-trace being logged.
### Changelog 2.16.53..2.16.54
<!-- git log 2.16.53..2.16.54 -no-merges -format='[%h](https://github.com/dcache/dcache/commit/%H)%n: %s%n' -->
[928eedf](https://github.com/dcache/dcache/commit/928eedf282a9aa58cba63f71de3e40984dcb9364)
: [maven-release-plugin] prepare release 2.16.54
[c0ddc8b](https://github.com/dcache/dcache/commit/c0ddc8be3aa08274b5e2c8b20364bf2f0966d94a)
: [maven-release-plugin] prepare for next development iteration
[737c0c2](https://github.com/dcache/dcache/commit/737c0c2f5567e17d5541564f0a32cba11c196101)
: pool: fix double logging on remote FTP transfer error
[2d66570](https://github.com/dcache/dcache/commit/2d66570d12ce5ad83ef2a757764c99776f38f1e9)
: cells: don't log stack-trace on starting cell with same name as running cell
[76a0285](https://github.com/dcache/dcache/commit/76a0285fb6435a67cf0685935f44d9584b787268)
: pool: Fix how certain bugs are logged
[f9c3b4e](https://github.com/dcache/dcache/commit/f9c3b4e6ad163799ee607f78131fa195e160bc5e)
: star: support PostgreSQL running on non-standard TCP ports
[eb1e8c1](https://github.com/dcache/dcache/commit/eb1e8c15189b2db01bc8433bbd191dbda5fa110a)
: rpm: don't assume existing dcache user is member of dcache group
[7d26897](https://github.com/dcache/dcache/commit/7d26897d0e488ad49cf81471039faea852cec87b)
: statistics: avoid stack-trace on internal timeout
## Release 2.16.53
### admin
The admin interface reported an attempt to connect to an absent cell as a bug. The current release fixed the issue.
### httpd
Requests to httpd targeting an unknown resource was returning `200 OK` response code. Nevertheless the `404 NOT FOUND`
response would be closer fit. This is now fixed.
### Changelog 2.16.52..2.16.53
<!-- git log 2.16.52..2.16.53 -no-merges -format='[%h](https://github.com/dcache/dcache/commit/%H)%n: %s%n' -->
[d3251cd](https://github.com/dcache/dcache/commit/d3251cd0dbef0f0d4310d58ef47c666f65b2c485)
: [maven-release-plugin] prepare release 2.16.53
[f9fa835](https://github.com/dcache/dcache/commit/f9fa835279113492e92d14d58f9253398079d4e0)
: admin: do not report attempts to connect to missing cell as a bug
[cb1dbde](https://github.com/dcache/dcache/commit/cb1dbde4813579b079c4d7eccb3e9db22cfcf82f)
: httpd: return 404 status code on an unknown page
[6ce3535](https://github.com/dcache/dcache/commit/6ce35350b5f218542ee3158daf63fa3bfaed7bc3)
: [maven-release-plugin] prepare for next development iteration
## Release 2.16.52
### Changes affecting multiple services
dCache no longer logs stack-traces if a Java VirtualMachineError occurs. This is unnecessary as dCache was (presumably) working fine until Java
discovered a problem.
### chimera
Sites updating to dCache 2.15 or later might observe that a lost+found directory with incorrect permissions was created during the update. This
patch ensures correct permissions. Since we cannot know if the current permissions in lost+found are
intended, this patch does not modify any existing lost+found directory
permissions.
### pool
The `sweeper free`command no longer logs a stack trace if it is started with incorrect input information.
An irrelevant stack trace was logged by the pool. This release corrects that.
### Changelog 2.16.51..2.16.52
<!-- git log 2.16.51..2.16.52 -no-merges -format='[%h](https://github.com/dcache/dcache/commit/%H)%n: %s%n' -->
[35ee85d55b](https://github.com/dcache/dcache/commit/35ee85d55b4854c48ac313900923aadaa2e4e1fc)
: [maven-release-plugin] prepare release 2.16.52
[33b71595ad](https://github.com/dcache/dcache/commit/33b71595adb8ce403a51e3a2f35e11d1177b8316)
: chimera: update schema migration when creating 'lost+found' directory.
[f099997ebf](https://github.com/dcache/dcache/commit/f099997ebf96de48eac2e825d4f4f53c2116bab6)
: pool: fix stack-trace on bad command input
[0f767a691b](https://github.com/dcache/dcache/commit/0f767a691b6a94e51282ca7399821ff67f6323eb)
: pool: fix stacktrace on FaultEvent logging
[9831422ad2](https://github.com/dcache/dcache/commit/9831422ad236ee185ac5008d0577273c7978f5f1)
: system: Don't log stack-trace on fatal JVM error
[f510231470](https://github.com/dcache/dcache/commit/f5102314705699ce112a75c913e562607d89089e)
: [maven-release-plugin] prepare for next development iteration
## Release 2.16.51
### alarms
Until now, the sorting order of alarms did not provide a correct ordering
for all types of alarms. With this release, alarms are now implicitly ordered
by at least their latest modification timestamp.
### resilience
One of the features of resilience is the enforcement of file
partioning on pools according to pool tags. The pool tag
restrictions are observed whenever a file is copied. In
addition, it is rechecked when a storage unit is updated,
in order to make sure the files are distributed correctly
according to the new requirements. This is done by
removing the offending copies and recopying them in
a new location.
Should files get redistributed, however, by rebalancing or
a migration job, it is possible that the partitioning will
be violated, since only resilience observes it.
The resilience service now verifies that files are distributed according to the requirements
specified by pool tags while doing periodic scans (or scans initiated through the admin
command).
### statistics
A possible race condition was removed from the implementation of the `create stat` admin command.
### Changelog 2.16.50..2.16.51
<!-- git log 2.16.50..2.16.51 -no-merges -format='[%h](https://github.com/dcache/dcache/commit/%H)%n: %s%n' -->
[474cea883c](https://github.com/dcache/dcache/commit/474cea883c2016af9e192bb5a8597507bc09c336)
: [maven-release-plugin] prepare release 2.16.51
[848ccaa4f8](https://github.com/dcache/dcache/commit/848ccaa4f87f0a2d5da98a2973b6b7b7ead395b4)
: statistics: fix race in "create stat" admin command
[6b91bf85e0](https://github.com/dcache/dcache/commit/6b91bf85e0f316b5aa81b8a02e16f9efd49d9c2e)
: srm: fix stacktrace on database failure
[20e98664bc](https://github.com/dcache/dcache/commit/20e98664bc17748ce8a72d1d100655b7d9deda87)
: alarms: revert LogEntry.compareTo() to throw NPE on null object
[06ed380733](https://github.com/dcache/dcache/commit/06ed38073303f4bc9929a0e853cc2c1ad8e60503)
: resilience: force tag partition checking on scans from admin command and periodic checks
[9565b03a7a](https://github.com/dcache/dcache/commit/9565b03a7a4f0cb531acd52fafc95c07c50b194a)
: alarms: fix natural order comparator to use timestamp first
[805892ebf6](https://github.com/dcache/dcache/commit/805892ebf69c0b9ed3548fe91148ea35abc85fe9)
: [maven-release-plugin] prepare for next development iteration
## Release 2.16.50
### dcap
A pool that has gone offline and comes back up again may become
very slow to respond due to a large amount of superfluous error
messages to dcap clients that disconnected in the meantime. This
patch ensures a more responsive reaction to these cases by
introducing a time-to-live value for such messages.
### pool
Error reporting was improved for cases of IO errors in pools.
### Changelog 2.16.49..2.16.50
<!-- git log 2.16.49..2.16.50 -no-merges -format='[%h](https://github.com/dcache/dcache/commit/%H)%n: %s%n' -->
[f8ef2c239f](https://github.com/dcache/dcache/commit/f8ef2c239f52409c8f161a572cb2b497e0781f9e)
: [maven-release-plugin] prepare release 2.16.50
[abfdee972d](https://github.com/dcache/dcache/commit/abfdee972d5c681dddf1215e4ca908f7f28bf2a9)
: pool: avoid 'null' and other nondescript error messages
[5a75c9b609](https://github.com/dcache/dcache/commit/5a75c9b609c28619f245eb89b344ad229191748a)
: [maven-release-plugin] prepare for next development iteration
[9d55193337](https://github.com/dcache/dcache/commit/9d551933372bf1bc912095df1b18f417dae34c03)
: dcap: add TTL information to dcap messages
## Release 2.16.49
### Changes affecting multiple services
Many dCache components use RemotePoolMonitor to provide fast access to
the information that PoolManager has about pools. In order to facilitate
system diagnosis, the 'info' admin command was augmented by information
about the current status of the RemotePoolMonitor.
### admin
The Apache sshd library used by the admin interface was updated.
Although we believe that dCache is not affected, some security vulnerability
scanners alert users to a potentially vulnerable library version.
The update serves mostly to avoid those false alarms.
### dcap
In order to better handle large READV requests, the buffer size
for dcap commands was changed to automatically grow to the
required size, up to a maximum buffer size of 8 MB.
### pool
A bug in gfal2 results in FTP transfers being aborted some 50 ms after
being initiated. This results in the door killing the mover shortly
after the pool received the PoolDeliverFile message. If the mover is
not queued, but not yet fully started, this may lead to the pool
disabling itself. This patch corrects that problem, ensuring that
the pool continues to run despite any aborted transfers.
### xrootd
In the 4.7 releases, the xrootd client started enforcing
protocol requirements for kXR_login which, unfortunately,
broke access to dCache. The xrootd client expects an answer
with a 16-character session ID from the door and then the
pool after the redirection. Without this ID, the client
would retry (without success) repeatedly and appear to hang.
dCache's xrootd implementation has been augmented with the session
ID, enabling it to work with xrootd clients of version 4.7 and up.
### Changelog 2.16.48..2.16.49
<!-- git log 2.16.48..2.16.49 -no-merges -format='[%h](https://github.com/dcache/dcache/commit/%H)%n: %s%n' -->
[4c08188f48](https://github.com/dcache/dcache/commit/4c08188f48f3fcdf5c384605d37aaeae22ecbc1f)
: [maven-release-plugin] prepare release 2.16.49
[c89c0d0ffd](https://github.com/dcache/dcache/commit/c89c0d0ffd4016dbc7893f8921ad6bef8e1f0792)
: many: add diagnostic information about remote pool monitor
[5fd8a663e9](https://github.com/dcache/dcache/commit/5fd8a663e93288a3b419634498652501774343eb)
: pool: dont disable pool if mover cancelled before open
[efdcd16213](https://github.com/dcache/dcache/commit/efdcd162133622798daea346909625d65a3bee9f)
: Manual correction of missing mvn-release-plugin commit: Preparation for next development iteration
[6185ebf498](https://github.com/dcache/dcache/commit/6185ebf498b3a95deeb655467b77c191b50aac68)
: apache sshd: upgrade to 1.3.0 due to security vulnerability
[92cadf866b](https://github.com/dcache/dcache/commit/92cadf866bc7418ee3fd6bbc6f98d030aba3449f)
: dcache: fix bug in PoolSelectionUnitV2 match()
[1e2adb151e](https://github.com/dcache/dcache/commit/1e2adb151e4bb97ea6ba2f1150052b756ea10aba)
: dcache-xrootd: Fix login handshake to support xrootd clients (> 4.7.0)
[089a4474a6](https://github.com/dcache/dcache/commit/089a4474a6550d4fc9fdbb3cdb811f2c2f9e8669)
: dcap: bump max command size sent by client to 8MB
## Release 2.16.48
### cells
The current release improved some problematic error messages has better error reporting to ensure bugs are understood.
### httpd
The curren release fixed the issue of change of format in transfers.txt after upgrading from 2.13 to 2.16.
### pool
The current release fixed log and alarms duplication when rebuilding broken entry.
### Changelog 2.16.47..2.16.48
<!-- git log 2.16.47..2.16.48 -no-merges -format='[%h](https://github.com/dcache/dcache/commit/%H)%n: %s%n' -->
[ec1553b](https://github.com/dcache/dcache/commit/ec1553b0db6ce5c94828b9ad440637368d6e08ec)
: [maven-release-plugin] prepare release 2.16.48
[1b5d4b2](https://github.com/dcache/dcache/commit/1b5d4b2170ecd27c25b5b6e63cc0852f24f8dce2)
: httpd: restore millis to transfer time for transfers.txt
[eb6eacb](https://github.com/dcache/dcache/commit/eb6eacb1de823cf6ea1763f1173812c87be6897f)
: pool: fix log and alarms duplication when rebuilding broken entry
[f8377dd](https://github.com/dcache/dcache/commit/f8377dd9820373e8468710ab8c4aae8f2d8bf09e)
: cells: better error reporting to ensure bugs are understood
[ed9054b](https://github.com/dcache/dcache/commit/ed9054ba6163273e19c24e5994001972b1fce4ba)
: [maven-release-plugin] prepare for next development iteration
## Release 2.16.47
### pool
The current release fixed regression in GridFTP OPTS CKSM command and GridFTP `OPTS CKSM` command is supported again.
The current release fixe regression with third-party pull transfers using GridFTP, with
dCache acting as the GridFTP client that prevented data integrity
checks.
### resilience
When resilience tries to copy or remove a file, and it is no longer
in the namespace, this should be a fatal error, differently from
the discovery that a replica is no longer in cache. These two
errors, however, were treated the same way. This is now fixed and the correct behavior is
immediate abort of operation when file is not in namespace.
The current release improved error handling for file deletion during scan correctly it fixed bug in formatting and handling of cache exception types.
When doing a pool scan, the storage unit information must be
recovered for each file. This is done from the chimera attributes.
The code checks an internal map for an index number corresponding
to the unit it knows about from the PoolMonitor.
However, if the pool selection unit configuration changes such that
a storage unit is eliminated, that mapping will also be deleted
from resilience. In the case that the attributes stored in
Chimera still have the older storage class information, there
will be a NoSuchElementException thrown.
This is fixed now and Pool scans that encounter this situation do not get stuck
forever in the queue.
### webdav
In RFC 7230, section 3.2, it states that HTTP header names should be
case insensitive. Despite this, the standard milton mechanism for
acquiring header information is case sensitive, which (in turn) means
that several HTTP header values in dCache are similarly case sensitive.
There were reports that this case sensitivity has caused problems with certain clients (e.g., go).
The current release fixed this issue and headers that control third-party transfers are now case insensitive, so should work with more clients.
### Changelog 2.16.46..2.16.47
<!-- git log 2.16.46..2.16.47 -no-merges -format='[%h](https://github.com/dcache/dcache/commit/%H)%n: %s%n' -->
[d13e0ce](https://github.com/dcache/dcache/commit/d13e0ced7cfb909a168c6342e2cbb574ea845f67)
: [maven-release-plugin] prepare release 2.16.47
[b018bd8](https://github.com/dcache/dcache/commit/b018bd8ade2c919b2e105f78eaea62631ec3237e)
: Update FileOperationHandler.java
[0bd79ab](https://github.com/dcache/dcache/commit/0bd79ab0f9337ac093c73be1efd3b651c5da28ea)
: pool: fix data integrity regression for 3rd-party GridFTP pull transfers
[fda0922](https://github.com/dcache/dcache/commit/fda09222b092b3a1ea50090ccaa502b572352816)
: pool: fix regression in GridFTP OPTS CKSM command
[937e483](https://github.com/dcache/dcache/commit/937e48329123aa0f37f51b8cdb50828002e318b5)
: resilience: handle file deletion during scan correctly
[3ce133b](https://github.com/dcache/dcache/commit/3ce133b0f91b969bae6fd821231bf94c230b1914)
: resilience: add pool operation logging
[5a7bdfe](https://github.com/dcache/dcache/commit/5a7bdfea18c9ba1dc7d2a0e51696f81a1aee5b88)
: resilience: handle storage unit NoSuchElement failure
[0a9d62e](https://github.com/dcache/dcache/commit/0a9d62e7ca7c056441dd43aab217f1dfb38c750a)
: webdav: adjust header parsing to be case insensitive
[d423c5e](https://github.com/dcache/dcache/commit/d423c5e2a1935950e11e3ab4bb8f0996ea46f58b)
: resilience: handle all cases where no locations for file may be discovered
[3b390ba](https://github.com/dcache/dcache/commit/3b390ba68c9ca0a3c731e08a562f6e1a4bfbc6ac)
: resilience: distinguish correctly between file not in repository and file not found
[24f999b](https://github.com/dcache/dcache/commit/24f999bf0b1be3eb029d764589b12a2aaced6e69)
: resilience: fix bug in formatting and handling of cache exception types
[41985bd](https://github.com/dcache/dcache/commit/41985bdc7b65d3c5a0b44293b12bf261e0abbfcb)
: PoolManager : set return code to CacheException.PERMISSION_DENIED if staging is not allowed due to stage protection.
[91ebad3](https://github.com/dcache/dcache/commit/91ebad3a9e184d4a1359c00ec8a3fd93cd163eab)
: [maven-release-plugin] prepare for next development iteration
## Release 2.16.46
### configuration
There are configuration options in zookeeper that may affect how well
the zookeeper cluster will work with dCache. The lack of documentation
of how dCache uses zookeeper prevents admins from tuning their zookeeper
instance. This is now fixed and zookeeper configuration is updated with
hints on how dCache uses zookeeper, along with the corresponding zookeeper configuration properties.
### webdav
The current release fixed the stack-traces on bad client input.
### Changelog 2.16.45..2.16.46
<!-- git log 2.16.45..2.16.46 -no-merges -format='[%h](https://github.com/dcache/dcache/commit/%H)%n: %s%n' -->
[c3a8fe8](https://github.com/dcache/dcache/commit/c3a8fe8aa968861aba2b3b91684759f131aac4bd)
: [maven-release-plugin] prepare release 2.16.46
[704501a](https://github.com/dcache/dcache/commit/704501a044f15bcc3f967e9af3aa1ffe77717ee4)
: configuration: update zookeeper configuration with hints
[bf7f2c8](https://github.com/dcache/dcache/commit/bf7f2c892febe61f8857dc2a4ba9ee2378c8af05)
: webdav: avoid stack-trace on bad user requests
[7663c8c](https://github.com/dcache/dcache/commit/7663c8c7b013c5f573d825b67466b41f473a4005)
: alarms: guard against NPEs on LogEntry getters
[fa3f0a8](https://github.com/dcache/dcache/commit/fa3f0a832ab3bacf7a6b291bbe1be8670abc97dd)
: [maven-release-plugin] prepare for next development iteration
## Release 2.16.45
### admin
While `migration move` tasks on pools were working correctly, for `migration info` command an error occurred,
that the current user (root) wasn't allowed to execute anything (due to missing ACLs). This is now fixed.
### Changelog 2.16.44..2.16.45
<!-- git log 2.16.44..2.16.45 -no-merges -format='[%h](https://github.com/dcache/dcache/commit/%H)%n: %s%n' -->
[dc7ea00](https://github.com/dcache/dcache/commit/dc7ea00dfac555c9c6534e202fbb1477ccac0264)
: [maven-release-plugin] prepare release 2.16.45
[4a46bde](https://github.com/dcache/dcache/commit/4a46bde8c8915d336372db669119149ed71d61d0)
: resilience: restore extractor class value for extractor property
[4f510f3](https://github.com/dcache/dcache/commit/4f510f3070509aa2e5b901935066e3e7963daf30)
: admin: Fix Inconsistent ACL enforcement, RT 9207
[d4abc07](https://github.com/dcache/dcache/commit/d4abc07fea6a1177b8abca4c977a39ba37491520)
: [maven-release-plugin] prepare for next development iteration
## Release 2.16.44
### configuration
For some services it was unclear what were the admin's responsibilities in
terms of consistent configuration. The current release updated the documentation describing what is needed to deploy redundant services.
### srm
The current release improved configuration for `srmPing` responses.
### Changelog 2.16.43..2.16.44
<!-- git log 2.16.43..2.16.44 -no-merges -format='[%h](https://github.com/dcache/dcache/commit/%H)%n: %s%n' -->
[305fd82](https://github.com/dcache/dcache/commit/305fd8270cc2773a0fa8456298223d60d6d0115c)
: [maven-release-plugin] prepare release 2.16.44