- 13 1月, 2018 40 次提交
-
-
由 Heikki Linnakangas 提交于
Plenty remains, but this is a start.
-
由 Heikki Linnakangas 提交于
-
由 Heikki Linnakangas 提交于
-
由 Ashwin Agrawal 提交于
These tests are very tightly coupled with filerep and persistent tables implemenation. We do need to have tests in replacement but these would be coded not in TINC and mostly much less scenarios as in general walreplication mirrors active for full ICW validates most of crashrecovery logic. What's missing mostly is real crash scenarios in middle of active workload like creating/dropping objects and all.
-
由 Heikki Linnakangas 提交于
After removing -s option from gpsegstart, this unit test started failing with curious error: Stderr: Usage: gpunit [--help] [options] gpunit: error: no such option: -s ====================================================================== ERROR: Test Suite Name|programs.test.unit.test_cluster_clsrecoversegment|Test Case Name|test_output_segments_in_change_tracking_disabled_should_print_failed_segments|Test Details| ---------------------------------------------------------------------- Traceback (most recent call last): File "/home/heikki/git-sandbox-gpdb/master/gpMgmt/bin/gppylib/programs/test/unit/test_cluster_clsrecoversegment.py", line 16, in setUp (options, _) = raw_options.parse_args() File "/usr/lib/python2.7/optparse.py", line 1402, in parse_args self.error(str(err)) File "/usr/lib/python2.7/optparse.py", line 1584, in error self.exit(2, "%s: error: %s\n" % (self.get_prog_name(), msg)) File "/usr/lib/python2.7/optparse.py", line 1574, in exit sys.exit(status) SystemExit: 2 It turns out that the unit test was passing the command-line options from the gpunit invocation, to the options parser of the gpsegstart command. It was accidental that it ever worked, because gpsegstart also happened to have a -s option, like gpunit did. Now that the option was removed, the gpsegstart options parser started to fail. To fix, explicitly pass "no command-line arguments" to the gpsegstart options parser, so that it doesn't pick up the args from the gpunit invocation.
-
由 Heikki Linnakangas 提交于
Remove test code for check_persistent_tables function, which was removed earlier. Fix a few more initFromString() lines.
-
由 Ashwin Agrawal 提交于
Many times the `commit_blocking` test fails, its not clear if the problem happened during the test, or cluster was not in right state before we started. Hence adding expected state for the test at start which would help to easily know if this test failed or is just side-effect for previous test failure.
-
由 Heikki Linnakangas 提交于
-
由 Heikki Linnakangas 提交于
I removed the filespaces arg earlier, but failed to update the format string accordingly.
-
由 Ashwin Agrawal 提交于
-
由 Ashwin Agrawal 提交于
- Special lock functions for RelationExtension - Special function ReadBuffer_Resync() - States related to CT and RESYNC - Xlog during PageInit() for vacuum lazy (upstream doesn't have it so removed it)
-
由 Ashwin Agrawal 提交于
This reverts commit 1a27788edfd2163cbfcb1dc30c5eb870eac77181. As should be passing now since FTS using uninitialized variable `fts_status` causing the failure has been fixed now.
-
由 Ashwin Agrawal 提交于
On QD start, FTS process can take sometime to start and initialize the `ftsProbeInfo->fts_status`. So, check against the same only if its initialized and avoid incorrectly reporting segment as down and failing queries.
-
由 Ashwin Agrawal 提交于
-
由 Heikki Linnakangas 提交于
Leftovers from removal of filespaces and replication ports. Caught by unit tests.
-
由 Heikki Linnakangas 提交于
-
由 Heikki Linnakangas 提交于
-
由 Heikki Linnakangas 提交于
On second thoughts, let's keep the QD mirror running. I'm not sure why we disabled it originally, but now that I went through the trouble of fixing subsequent tests to pass with a QD mirror, let's keep it enabled.
-
由 Heikki Linnakangas 提交于
-
由 Heikki Linnakangas 提交于
The setup script for the walrep tests disables the standby for the QD node. That used to not work, and therefore the mirror was still running, but now that I fixed "gpinitstandby -ra", it is disabled again. I'm not convinced that we should disable the mirror, and leave it disabled, in the walrep tests. But that's the way it was.
-
由 Heikki Linnakangas 提交于
-
由 Heikki Linnakangas 提交于
I had removed the fileSpaceDictionary argument to SegmentRow constructor earlier, but this was left behind.
-
由 Heikki Linnakangas 提交于
-
由 Heikki Linnakangas 提交于
print_summary() no longer has a filespaces argument.
-
由 Heikki Linnakangas 提交于
-
由 Heikki Linnakangas 提交于
-
由 Heikki Linnakangas 提交于
Persistent table are no more.
-
由 Heikki Linnakangas 提交于
We might want to have something similar with tablespaces, but not as a TINC test like this.
-
由 Heikki Linnakangas 提交于
-
由 Heikki Linnakangas 提交于
-
由 Heikki Linnakangas 提交于
These functions don't exist anymore.
-
由 Heikki Linnakangas 提交于
There are some "known" differences that are currently not masked out. I think the 'last_value' field is WAL-logged to a higher value than what's written to disk in the master. This was not visible before, when the demo cluster didn't have a standby for the QD node. In QE nodes, sequences are not used.
-
由 Heikki Linnakangas 提交于
-
由 Xiaoran Wang 提交于
Signed-off-by: NMax Yang <myang@pivotal.io>
-
由 Ashwin Agrawal 提交于
Also, remove caling GpRecover() in test_mpp23395. Ideally this test needs to be re-written in isolation2 but this should atleast get it green.
-
由 Heikki Linnakangas 提交于
Now that max_wal_senders is not pegged at 1, it's normal for there to be unused slots.
-
由 Jacob Champion 提交于
Follow-up to the previous commit.
-
由 Heikki Linnakangas 提交于
-
由 Heikki Linnakangas 提交于
It's now in gp_segment_configuration.
-
由 Heikki Linnakangas 提交于
-