0e1c32e1d2
fix: consistency check was broken when the key server key space is sharded
2018-07-09 15:46:17 -07:00
ef6ccc7b9e
fix: consistency check was not checking for data inconsistencies
2018-07-09 15:46:12 -07:00
6b40f2764d
fix: off by one error on popping missing tags
2018-07-09 15:43:22 -07:00
c6133ba711
Merge pull request #579 from satherton/release-5.2-leaks
...
Destroy peers that are inactive
2018-07-09 15:21:24 -07:00
e503dc975c
fix: destroy peers that are inactive
...
do not open new connections to send replies
2018-07-09 13:37:06 -07:00
4a9feece79
Merge pull request #566 from alecgrieser/bump-api-version
...
Bump API version from 520 to 600
2018-07-09 13:35:31 -07:00
46b8612566
bump API version from 520 to 600
2018-07-09 11:00:57 -07:00
f49569075c
Merge pull request #577 from etschannen/release-6.0
...
Added a trace event related to max_notifications being reached
2018-07-08 20:19:17 -07:00
ef62c98ef5
Added a trace event related to max_notifications being reached
2018-07-08 20:18:24 -07:00
1a1d0c36da
Merge pull request #576 from etschannen/release-6.0
...
Merge 5.2 into 6.0
2018-07-08 20:15:18 -07:00
5a2cb3037b
merge 5.2 into 6.0
2018-07-08 20:14:06 -07:00
d894f4cd52
Merge branch 'release-5.2' of github.com:apple/foundationdb into release-5.2
2018-07-08 20:12:36 -07:00
3b62fa5b89
Merge pull request #574 from satherton/release-5.2-leaks
...
Old memory leak fixes
2018-07-08 20:11:43 -07:00
2ac65fc708
Merge pull request #575 from etschannen/feature-remote-logs
...
Allow peers to be deleted when no longer used
2018-07-08 20:10:14 -07:00
c5b5d02858
Merge branch 'release-5.2' of github.com:apple/foundationdb into release-5.2
2018-07-08 20:04:31 -07:00
d42c9914d2
fix: future quiet databases need to be able to continue the reconfigure if the first one completes the repopulate but is cancelled before changing usable_regions
2018-07-08 19:56:55 -07:00
ce6b0d4952
fix: consistency check must also configuration usable regions to 1, because the remote log set might not be able to copy data
2018-07-08 18:25:01 -07:00
380b2895f7
fix: we need to wait for the yield in the team tracker not just after the initial failure reaction delay, but also after zeroHealthyTeams changes
2018-07-08 17:44:19 -07:00
0e97ce79b4
fix: destroy peers that are inactive
...
do not open new connections to send replies
2018-07-08 10:26:41 -07:00
1c90e948f8
Merge pull request #573 from etschannen/feature-remote-logs
...
Data distribution bug fixes
2018-07-07 17:43:11 -07:00
4dd18afb84
fix: we cannot make MAX_RECOVERY_VERSIONS lower than MAX_VERSIONS_IN_FLIGHT because we can mark a recovery as stalled before finishing the recovery, leading to an infinite loop of recoveries
2018-07-07 17:41:20 -07:00
d6c6e7d306
fix: do not attempt data movement to an unhealthy destination team
...
allow building more teams than desired if all teams are unhealthy
bestTeamStuck is an error in simulation again
2018-07-07 16:51:16 -07:00
a2f16e217e
Memory waste fix, when a Peer disconnects an extra packet buffer block is allocated to copy unsent reliable bytes to even if there aren't any.
2018-07-06 19:44:30 -07:00
fee4234e6b
Bug fixes in memory activity logging.
2018-07-06 19:02:42 -07:00
acee7eef1b
Merge branch 'release-5.2' of github.com:etschannen/foundationdb into release-5.2-leaks
2018-07-06 18:32:21 -07:00
3892aa7263
Merge pull request #572 from etschannen/feature-remote-logs
...
the cluster controller needs to update its priority immediately
2018-07-06 18:31:27 -07:00
13fb59cf11
fix: the cluster controller needs to update its priority immediately
2018-07-06 18:29:54 -07:00
cdafd542ee
fix: fixed a memory leak where leaderInfo notifications are not cleared out
2018-07-06 17:40:29 -07:00
72ffdf7204
Merge pull request #571 from etschannen/feature-remote-logs
...
added a trace event for forced recovery
2018-07-06 17:11:05 -07:00
f0494f18b1
added a trace event for forced recovery
2018-07-06 17:09:29 -07:00
d58ccab22a
Merge pull request #570 from etschannen/feature-remote-logs
...
properly handle zero logRouterTags
2018-07-06 16:58:51 -07:00
43b5cb28ba
fix: properly handle zero logRouterTags, this is important for forced recovery
2018-07-06 16:52:25 -07:00
6dbddab530
Merge pull request #568 from etschannen/feature-remote-logs
...
Many bug fixes
2018-07-06 16:12:56 -07:00
2718176927
fix: remote logs did not pop all of the data for removed logs on recovery because data for the missing tag was not recorded yet at the time of recovery
2018-07-06 16:10:41 -07:00
28c0d96c90
fix: treat the local region as best when version difference is too large
...
re-check requests when the version difference becomes small
2018-07-06 14:44:11 -07:00
9015b8038f
io_error should cause the process to die and restart, to prevent repeated recruitment of a bad disk
2018-07-06 14:42:36 -07:00
7d54ca4dc2
fix: errors from disk should trump errors from workers
2018-07-06 14:41:36 -07:00
6d7172ef7e
fix: canKillProcesses did not take into account the remoteTLogPolicy when checking notEnoughLeft
2018-07-05 21:36:09 -07:00
6f4ca2eba2
fix: get all processes did not include rebooting processes
2018-07-05 21:13:56 -07:00
bb2eb2fe53
Merge pull request #565 from etschannen/feature-remote-logs
...
Simulation did not permanently kill machines in most tests
2018-07-05 15:07:28 -07:00
5b12414b74
Merge pull request #564 from alexmiller-apple/tlsplugin
...
Fix dependencies for TLS library stuff
2018-07-05 14:32:45 -07:00
cd4fb9285a
waitForExlusion requires both regions to be healthy, which is only possible if we do not kill all logs in a region
2018-07-05 14:04:42 -07:00
6c98aa8aac
Fix not depending on FDBLibTLS.a and default TLS_LIBDIR to a sensible place.
2018-07-05 13:23:20 -07:00
6cf5354425
checkSatelliteTagLocations is not an error if the same zoneId is used multiple times
2018-07-05 13:00:13 -07:00
21347df254
fix: getting metrics did not handle broken_promise errors
2018-07-05 12:30:11 -07:00
da5a232d7e
fix: If we have not recruited the remote logs yet and detect a configuration change, we must fail the master to update the remote recruitment request
2018-07-05 12:17:41 -07:00
7315e5da55
fix: isExcluded and isCleared were exactly wrong
...
fix: isCleared should mean the process is dead
2018-07-05 02:22:22 -07:00
507b3bacb0
fix: kill all tlogs in one region prevents the remote logs from recovering in that region, do not allow that to prevent us from configuring usable_regions=1.
...
added more recovery states.
2018-07-05 00:08:51 -07:00
99e2b06c2d
Merge pull request #562 from etschannen/feature-remote-logs
...
Added repopulate region anti-quorum to the configuration
2018-07-04 16:44:35 -04:00
e17dfea3b6
fix: desiredTLogCount was used instead of getDesiredLogs(), which caused problems with recruitment when desiredTLogCount was -1.
...
canKillProcess logic was wrong.
We still need to configure usable_regions because if datacenterVersionDifference is too large we cannot complete data movement.
2018-07-04 16:22:32 -04:00
Evan Tschannen