parts.partition_max* testcases are incompatible with --parallel

Bug #1180481 reported by Laurynas Biveinis
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MySQL Server
Unknown
Unknown
Percona Server moved to https://jira.percona.com/projects/PS
Fix Released
Medium
Laurynas Biveinis
5.1
Invalid
Undecided
Unassigned
5.5
Invalid
Undecided
Unassigned
5.6
Fix Released
Medium
Laurynas Biveinis

Bug Description

The following 5.6 tests used to be skipped due to ulimit configuration:

02:02:19.760 parts.partition_max_parts_hash_myisam w2 [ skipped ] Need open_files_limit >= 16450 (see ulimit -n)
02:02:19.991 parts.partition_max_parts_inv_myisam w2 [ skipped ] Need open_files_limit >= 16450 (see ulimit -n)
02:02:20.211 parts.partition_max_parts_key_myisam w2 [ skipped ] Need open_files_limit >= 16450 (see ulimit -n)
02:02:20.545 parts.partition_max_parts_list_myisam w2 [ skipped ] Need open_files_limit >= 16450 (see ulimit -n)
02:02:20.791 parts.partition_max_parts_range_myisam w2 [ skipped ] Need open_files_limit >= 16450 (see ulimit -n)
02:02:21.055 parts.partition_max_sub_parts_key_list_myisam w2 [ skipped ] Need open_files_limit >= 16450 (see ulimit -n)
02:02:21.281 parts.partition_max_sub_parts_key_range_myisam w2 [ skipped ] Need open_files_limit >= 16450 (see ulimit -n)
02:02:21.527 parts.partition_max_sub_parts_list_myisam w2 [ skipped ] Need open_files_limit >= 16450 (see ulimit -n)
02:02:21.851 parts.partition_max_sub_parts_range_myisam w2 [ skipped ] Need open_files_limit >= 16450 (see ulimit -n)
02:25:09.874 parts.partition_max_parts_hash_innodb w1 [ skipped ] Need open_files_limit >= 16450 (see ulimit -n)
02:25:11.212 parts.partition_max_parts_inv_innodb w1 [ skipped ] Need open_files_limit >= 16450 (see ulimit -n)
02:25:11.213 parts.partition_max_parts_key_innodb w1 [ skipped ] Need open_files_limit >= 16450 (see ulimit -n)
02:25:11.214 parts.partition_max_parts_list_innodb w1 [ skipped ] Need open_files_limit >= 16450 (see ulimit -n)
02:25:11.214 parts.partition_max_parts_range_innodb w1 [ skipped ] Need open_files_limit >= 16450 (see ulimit -n)
02:25:12.551 parts.partition_max_sub_parts_key_list_innodb w1 [ skipped ] Need open_files_limit >= 16450 (see ulimit -n)
02:25:12.552 parts.partition_max_sub_parts_key_range_innodb w1 [ skipped ] Need open_files_limit >= 16450 (see ulimit -n)
02:25:13.993 parts.partition_max_sub_parts_list_innodb w1 [ skipped ] Need open_files_limit >= 16450 (see ulimit -n)
02:25:13.993 parts.partition_max_sub_parts_range_innodb w1 [ skipped ] Need open_files_limit >= 16450 (see ulimit -n)

But several slaves were configured with high enough open file limit, enabling these tests, and all of them started failing, i.e.

01:05:54.580 CURRENT_TEST: parts.partition_max_parts_hash_myisam
01:05:54.580 mysqltest: In included file "./suite/parts/inc/partition_max_parts_hash.inc":
01:05:54.580 included from ./suite/parts/inc/partition_max_parts_hash.inc at line 47:
01:05:54.580 At line 47: query 'load data infile '$MYSQL_TMP_DIR/data01' into table t2 partition (p8191) fields terminated by ','' failed: 1290: The MySQL server is running with the --secure-file-priv option so it cannot execute this statement

We must either fix this, either revert to low open file limits for the time being.

Tags: ci upstream

Related branches

tags: added: ci
tags: added: upstream
summary: - Numerous parts.partition_max* test failures
+ parts.partition_max* testcases are incompatible with --parallel
Revision history for this message
Shahriyar Rzayev (rzayev-sehriyar) wrote :

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-1364

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.