Opened 12 years ago
Closed 8 years ago
#234 closed defect (wontfix)
Test rasimport with large file and small server countdown
| Reported by: | Dimitar Misev | Owned by: | Dimitar Misev |
|---|---|---|---|
| Priority: | major | Milestone: | Future |
| Component: | rasmgr | Version: | 8.3 |
| Keywords: | Cc: | abeccati, Peter Baumann, barboni@…, pozzati@…, Marcus Sen, Alexander Herzig | |
| Complexity: | Hard |
Description
rasimport should be tested with importing a large files, while starting rasserver with a small countdown (~25) and small timeout (~100).
It seems that ingestion breaks randomly in this scenario.
Change History (4)
comment:1 by , 10 years ago
| Cc: | added |
|---|---|
| Complexity: | → Very Hard |
| Milestone: | → 9.1 |
comment:2 by , 10 years ago
| Cc: | added |
|---|---|
| Complexity: | Very Hard → Hard |
| Component: | rasgeo → rasmgr |
This is not a rasgeo component, but more likely rasmgr c/s protocol issue.
comment:3 by , 10 years ago
| Milestone: | 9.1 → Future |
|---|
Note:
See TracTickets
for help on using tickets.
Perhaps the problem is that rasimport does several updates with the same connection in between the rasserver to which it is connected may be restarted by rasmgr. Whereas rasql just submits one query string. So this server restart is not done properly.