[jira] Created: (RIVER-214) There should be a way to flush class info from a running Outrigger server

["Jim Hurley (JIRA)" <ji...@apache.org>]

There should be a way to flush class info from a running Outrigger server
-------------------------------------------------------------------------

                 Key: RIVER-214
                 URL: https://issues.apache.org/jira/browse/RIVER-214
             Project: River
          Issue Type: Improvement
          Components: com_sun_jini_outrigger
    Affects Versions: jtsk_1.0
            Reporter: Jim Hurley
            Priority: Minor


Bugtraq ID [4431546|http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4431546]

Changing the "entry schema" being used with a space causes Outrigger
to freak out in completely undefined ways.  This is being addressed by
bug 4278245, but that fix will only cause Outrigger to throw a checked
exception when it detects an operation that represents a schema
change, there will still be no way to actually change the entry schema
of a running space.

Comments:
---------------------
Need to consider interactions between this feature and any new logging
strategies we might pursue (currently class data is write once).

Fixing this may require a change to the LogStore interface and / or the logging format. We may or not be able to make this backward compatable.


Suggested Fix
--------------------------
Add an admin method that cause Outrigger to purge the class data
associated with a particular class of entries (would obviously have to
handle subclasses properly).  Would only need to work if there were no
entries of that type in the space (if there were it could throw a
checked exception).  As part of this may want to introduce an admin
method to lock out operations on the space.

The other possible model is for Outrigger to expunge the class info
for entry types when outrigger discovers that it has no more entries
of that particular class (this is consistent with the approach Reggie
takes). Means that Outrigger wouldn't leak memory to storing unused
class info, but could make it harder to diagnose problems with
distributed upgrades of clients.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.