---
** [tickets:#1266] IMM: Client timeout for class-changes is hardwired and short
in imm-server**
**Status:** assigned
**Milestone:** 4.4.2
**Created:** Mon Mar 16, 2015 10:11 AM UTC by Anders Bjornerstedt
**Last Updated:** Mon Mar 16, 2015 10:11 AM UTC
**Owner:** Anders Bjornerstedt
A schema change that includes instance migration can be large.
The number of instances may be as large as the recommended upper limit of
imm database size (currently 300000 objects of average size 300 bytes).
This means that the operation may take time.
Currently there is a timeout mechanism in the server that generates a timeout
to the *client*. This timeout is hardwired to 6 seconds, for PRT-ops and
class-operations. The timeout does not abort the server side operation and
it is unclear why this server side generated client timeout is there. It should
not be needed since the client has its own timeout in the imma library.
This server side timeout to clients should either be removed or significantly
increased. The only possible reason for it to exist that I can think of is to
clean up client-continuation-records in the server.
---
Sent from sourceforge.net because [email protected] is
subscribed to https://sourceforge.net/p/opensaf/tickets/
To unsubscribe from further messages, a project admin can change settings at
https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a
mailing list, you can unsubscribe from the mailing list.
------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
