| View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] |
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0000031 | Rosetta | [All Projects] Crash | public | 2012-06-27 22:02 | 2012-08-03 11:49 |
|
| Reporter | delucasl | |
| Assigned To | delucasl | |
| Priority | low | Severity | crash | Reproducibility | random |
| Status | assigned | Resolution | open | |
| Platform | All platforms | OS | Any | OS Version | Any |
| Product Version | Trunk | |
| Fixed in Version | | |
|
| Summary | 0000031: Using DatabaseFilters and mysql/postgre and non-blocking mpi at the same time causes a race condition |
| Description | DatabaseFilters write a structure and then if necessary delete the structure being filtered out. In normal operation this is fine, as the MPIWorkPoolJobDistributor blocks so only one node can output at a time. Blocking is not strictly necessary when outputting to a database server, and can cause bottlenecking in short protocols. However, if blocking is disabled using the -jd2:mpi_fast_nonblocking_output, two processes can try to simultaniously delete the same pose, which causes a crash when the delete option fails. |
| Steps To Reproduce | run any jd2 supported application outputting to a database server with a large number of MPI managed nodes, a large nstruct and jd2:mpi_fast_nonblocking_output turned on. It will crash at some point when the race condition occurs. |
| Tags | No tags attached. |
|
| Application(s) Affected | anything supporting jd2 |
| Command Line Used | whatever.mysqlmpi.linuxgccrelease @flags.txt -jd2:mpi_fast_nonblocking_output |
| Developer Options | |
| Fixed in SVN Version | |
|
| Attached Files | |
|
Relationships 
Relationships