Re: [jgroups-users] JDBC_PING - "clear_table_on_view_change" attribute missing

Thanks a lot! I'll try

Regards
Michał

On 28/11/2018, 11:02, "Questions/problems related to using JGroups" <[email protected]> wrote:

    Use remove_all_data_on_view_change instead
    
    On 28.11.18 10:32, Questions/problems related to using JGroups wrote:
    > Hi,
    > 
    > I’m trying to migrate from jgroups 3.6.11 to 4.0.15.
    > 
    > However, I have a problem regarding JDBC_PING configuration:
    > 
    > <*JDBC_PING **connection_driver**="${hybris.database.driver}"
    > **connection_password**="${hybris.database.password}"
    > **connection_username**="${hybris.database.user}"
    > **connection_url**="${hybris.database.url}"
    > **initialize_sql**="${hybris.jgroups.schema}"
    > **datasource_jndi_name**="${hybris.datasource.jndi.name}"
    > **clear_table_on_view_change**="${hybris.jgroups.clear_table_on_view_change}"*/>
    > />
    > 
    > With new, 4.0 xsd schema attribute *clear_table_on_view_change* is not 
    > available anymore. Documentation 
    > <http://www.jgroups.org/manual4/index.html> ,however still refers to it:
    > 
    > /Another attribute /|/clear_table_on_view_change/|/ governs how zombies 
    > are handled. Zombies are table entries for members which crashed, but 
    > weren’t removed for some reason. E.g. if we have a single member 
    > /|/A/|/ and kill it (via kill -9), then it won’t get removed from the 
    > table./
    > 
    > /If /|/clear_table_on_view_change/|/ is set to true, then the 
    > coordinator //clears// the table after a view change (instead of only 
    > removing the crashed members), and everybody re-inserts its own 
    > information. This attribute can be set to true if automatic removal of 
    > zombies is desired. However, it is costly, therefore if no zombies ever 
    > occur (e.g. because processes are never killed with kill -9), or zombies 
    > are removed by a system admin, then it should be set to false./
    > 
    > So it seems to be the same content as for 3.6. Furthermore,
    > 
    > /Table 19. JDBC_PING/
    > 
    > table in above mentioned documentation does not contain such an 
    > attribute and this is another difference comparing to 3.6.
    > 
    > So I’m confused a bit now. Was this enabled by default? Replaced by 
    > another attribute? Or something else happened?
    > 
    > Please help.
    > 
    > Regards
    > 
    > Michał
    > 
    > 
    > 
    > 
    > 
    > _______________________________________________
    > javagroups-users mailing list
    > [email protected]
    > https://lists.sourceforge.net/lists/listinfo/javagroups-users
    > 
    
    -- 
    Bela Ban | http://www.jgroups.org
    
    
    
    _______________________________________________
    javagroups-users mailing list
    [email protected]
    https://lists.sourceforge.net/lists/listinfo/javagroups-users
    


_______________________________________________
javagroups-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/javagroups-users