- 13 1月, 2018 40 次提交
-
-
由 Ashwin Agrawal 提交于
Originally, we skip probing primary without mirrors, however, we still use the num_primary_segments to indicate number of requests. This caused inconsistency when processing the response, since, not all the primary segments got probe response. The fix is to only track the actual number of probe requests sent. Author: Xin Zhang <xzhang@pivotal.io> Author: Ashwin Agrawal <aagrawal@pivotal.io>
-
由 Xin Zhang 提交于
- detect primary goes down - flip the role to m/p/d/n and p/m/u/n (role/prefer/status/mode) in gp_segment_configuration - send promotion message to mirror to promote it Author: Xin Zhang <xzhang@pivotal.io> Author: Jacob Champion <pchampion@pivotal.io> Author: Asim R P <apraveen@pivotal.io>
-
由 Ashwin Agrawal 提交于
Author: Xin Zhang <xzhang@pivotal.io> Author: Ashwin Agrawal <aagrawal@pivotal.io>
-
由 Xin Zhang 提交于
In the past, the utility mode will not be retried, and caused wrong behavior when trying to connect to given segment under utility mode. In this refactoring, both utility mode and normal mode will go through connectdb() that has the retry logic. Author: Xin Zhang <xzhang@pivotal.io> Author: Ashwin Agrawal <aagrawal@pivotal.io>
-
由 Jacob Champion 提交于
We don't want to diff the output from `segwalrep.py recoverfull`, but we do want to know if the command has succeeded or not. Add a new execution mode, invoked via !\retcode EXECUTABLE [OPTIONS ...] which will bracket the program's stdout/stderr with begin/end_ignore, and also print out an exit code (which is not ignored).
-
由 Jacob Champion 提交于
Author: Jacob Champion <pchampion@pivotal.io> Author: Xin Zhang <xzhang@pivotal.io> Author: Ashwin Agrawal <aagrawal@pivotal.io>
-
由 Asim R P 提交于
If number of segments is not set to a value > 0, the assertion in getgpsegmentCount() trips. Executor calls this function from many places. Without this change, executing "select * from gp_stat_replication;" trips the assertion on a promoted mirror because number of contents is set to 0. Author: Asim R P <apraveen@pivotal.io> Author: Ashwin Agrawal <aagrawal@pivotal.io>
-
由 Heikki Linnakangas 提交于
There is no reason to believe that these bugs could reappear, in the same form.
-
由 Heikki Linnakangas 提交于
-
由 Heikki Linnakangas 提交于
It set the master_mirroring_administrator_disable variable, but it's not used for anything. Remove the variable, and all the code to pass that flag through.
-
由 Heikki Linnakangas 提交于
It was now unused.
-
由 Jacob Champion 提交于
There is a race condition in this test, where our disabling of the FTS probe process doesn't actually have to happen immediately (it takes a little while for the GUC to propagate). This may be the cause of some test failures we see where the primary is falling out of sync with the mirror before we want it to. Try a basic hack to see if it helps anything; the real fix will be to move to faultinjection, but that's another story. Author: Ashwin Agrawal <aagrawal@pivotal.io> Author: Jacob Champion <pchampion@pivotal.io>
-
由 Jacob Champion 提交于
SetSyncStandbysDefined and friends are now much simpler; there isn't really anything interesting to test anymore. We already have an integration test that covers the operation for the whole cluster.
-
由 Jacob Champion 提交于
Revert SyncRepUpdateSyncStandbysDefined to its upstream contract: only checkpointer may call it, and it acquires the SyncRepLock on its own. If we don't need to ensure that the FTS responder sends back syncrep=false immediately, the logic is vastly simplified, and we can remove the assertion on the receiver end. Also note that we don't need to set the GUC in memory directly; the SIGHUP will load the new GUC from disk, further simplifying things here. Author: Jacob Champion <pchampion@pivotal.io> Author: Ashwin Agrawal <aagrawal@pivotal.io>
-
由 Jacob Champion 提交于
synchronous_standby_names is set on the first FTS probe after starting the cluster, and it's written to disk, but it doesn't actually get persisted in memory on all cluster processes. The backend that "sets" the value exits without SIGHUP'ing the cluster, and it therefore "resets" to the empty string. If you're lucky enough to restart the cluster after this point, everything works as expected, but until then the cluster is in a strange state. This test (which currently fails) verifies that the synchronous_standby_names GUC is actually set appropriately on the segment.
-
由 Shoaib Lari 提交于
The syncing should be done automatically by the mirror, when the mirror connects to the primary. Author: Marbin Tan <mtan@pivotal.io> Author: Shoaib Lari <slari@pivotal.io>
-
由 Marbin Tan 提交于
gp_segment_configuration should be updated through gp_add_segment_primary and gp_add_segment_mirror - Add a fix for our status validation check. We were checking an incorrect of elements in a tuple, it was always return false if you only had primaries. Make it such that the mirrors will always be assumed down when validating when you only have primaries for the cluster. Author: Marbin Tan <mtan@pivotal.io>
-
由 Heikki Linnakangas 提交于
The column is called 'datadir', not 'directory'.
-
由 Heikki Linnakangas 提交于
The vacuum was causing trouble, see github issue #4298. And it seems pretty pointless or unrelated to gpexpand, anyway.
-
由 Heikki Linnakangas 提交于
This reverts commit 4efea6f73ef1b828e7ca435a9a62790f787ed861. I found the culprit, and don't need that debugging information anymore.
-
由 Heikki Linnakangas 提交于
-
由 Heikki Linnakangas 提交于
The "filespaces" argument was removed earlier, but I failed to remove the corresponding %s from the string.
-
由 Heikki Linnakangas 提交于
-
由 Heikki Linnakangas 提交于
gp_remove_segment_persistent_entries() function doesn't exist any more.
-
由 Heikki Linnakangas 提交于
-
由 Heikki Linnakangas 提交于
To hunt down "not enough arguments for format string" failure we're seeing MM_gpexpand_1 test in the pipeline
-
由 Marbin Tan 提交于
As a result of removing filespace, we need to pass the datadir instead. That way, gp_add_segment_primary now matches gp_add_segment_mirror. Author: Marbin Tan <mtan@pivotal.io> Author: Jacob Champion <pchampion@pivotal.io>
-
由 Marbin Tan 提交于
Author: Marbin Tan <mtan@pivotal.io>
-
由 Heikki Linnakangas 提交于
-
由 Heikki Linnakangas 提交于
On further inspection, the code seems perfectly fine.
-
由 Heikki Linnakangas 提交于
-
由 Jacob Champion 提交于
This reverts commit 0277b584 (which was already partially reverted in 0039844) and commit 4b4643f8. Commit 2b939748 already applied the logical intent of these commits, as well as some improvements which were accidentally reverted.
-
由 Xin Zhang 提交于
Author: Xin Zhang <xzhang@pivotal.io> Author: Ashwin Agrawal <aagrawal@pivotal.io>
-
由 C.J. Jameson 提交于
Author: C.J. Jameson <cjameson@pivotal.io>
-
由 Jamie McAtamney 提交于
-
由 Jamie McAtamney 提交于
We will not be supporting these utilities in GPDB 6. References to gpcrondump and gpdbrestore in the gpdb-doc directory have been left intact, as the documentation will be updated to refer to gpbackup and gprestore in a separate commit. Author: Jamie McAtamney <jmcatamney@pivotal.io>
-
由 Ashwin Agrawal 提交于
-
由 Ashwin Agrawal 提交于
Once this gos through in CI, will help to reduce one more job and there by elimintae one more VM expense.
-
由 Max Yang 提交于
* Fix tests associated filespace. * Update expected result of gpinitstandby with no standby_master directory. Author: Max Yang <myang@pivotal.io> Author: Xiaoran Wang <xiwang@pivotal.io>
-
由 Max Yang 提交于
Server side should exclude sub directory even parent directory wanted.
-