You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Sunitha Kambhampati (JIRA)" <de...@db.apache.org> on 2005/05/11 21:10:06 UTC
[jira] Created: (DERBY-271) Document the new property derby.system.durability=test
Document the new property derby.system.durability=test
------------------------------------------------------
Key: DERBY-271
URL: http://issues.apache.org/jira/browse/DERBY-271
Project: Derby
Type: Sub-task
Components: Documentation
Versions: 10.1.0.0
Reporter: Sunitha Kambhampati
Fix For: 10.1.0.0
Need to document the new property - derby.system.durability
This should probably go along with other properties in Tuning guide.
--------------------------------------------------
derby.system.durability
Currently the only valid supported case insensitive value is 'test'
If this property is set to any other value other than 'test', this
property setting is ignored
In the future, this property can be used to set different modes of durability
- for example a form of relaxed durability where database can recover to a
consistent state, or to enable some kind of in-memory mode.
When set to 'test', the store system will not force sync calls in the
following cases
- for the log file at each commit
- for the log file before data page is forced to disk
- for page allocation when file is grown
- for data writes during checkpoint
That means
- a commit no longer guarantees that the transaction's modification
will survive a system crash or JVM termination
- the database may not recover successfully upon restart
- a near full disk at runtime may cause unexpected errors
- database can be in an inconsistent state
This setting is provided for performance reasons and should ideally
only be used when the system can withstand the above consequences.
One sample use would be to use this mode (derby.system.durability=test)
when using Derby as a test database, where high performance is required
and the data is not very important.
If database is booted with derby.system.durability=test, the following warning message is logged in derby.log
WARNING: The database is booted with derby.system.durability=test. In this mode, it is possible that database may not be able to recover, committed transactions may be lost, database may be in an inconsistent state. Please use this mode only when these consequences are acceptable
and a similar message will appear in derby.log if the database was booted with derby.system.durability=test at any time previously.
It is important to realize that once the database is booted with derby.system.durability=test, there are no guarantees on if the database is consistent or not.
-------------------
Valid supported values are test
Example
derby.system.durability=test
One can set this as a command line option to the JVM when starting the
application or in the derby.properties file. It is a system level
property.
This property is static; if you change it while Derby is running,
the change does not take effect until you reboot.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (DERBY-271) Document the new property derby.system.durability=test
Posted by "Sunitha Kambhampati (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-271?page=comments#action_65573 ]
Sunitha Kambhampati commented on DERBY-271:
-------------------------------------------
Thanks Jeff for quickly generating the doc.
Here are some of my comments. Thanks.
------------------------
This is a property that can take values other than test, but currently we only support 'test' but in future will be used for other durability modes.
Therefore I dont think we should say ' This property can be used under testing purposes to improve performance' but maybe instead to say something similar to
This property can be used to change the default durability of derby to improve performance at the expense of consistency and durability of the database.
Currently the only valid supported case insensitive value is 'test'. If this property is set to any other value other than 'test', this property setting is ignored
In the future, this property can be used to set different modes of durability - for example a form of relaxed durability where database can recover to a
consistent state, or to enable some kind of in-memory mode.
1) I think we need to specify that the supported value is test , maybe after 'Default' section .
Supported values are 'test'
2) This line needs to change 'Consequently, this property should only be set when using Derby as a test database, where high performance is required and the data is not very important.'
Since users can use it for whatever they want as long as they can withstand the consequences of using derby.system.durability=test. So how about we change this to say a sample usage would be to enable this property when using Derby as a test database where consistency or recoverability is not an issue. It could probably go along in the example section.
> Document the new property derby.system.durability=test
> ------------------------------------------------------
>
> Key: DERBY-271
> URL: http://issues.apache.org/jira/browse/DERBY-271
> Project: Derby
> Type: Sub-task
> Components: Documentation
> Versions: 10.1.0.0
> Reporter: Sunitha Kambhampati
> Assignee: Jeff Levitt
> Attachments: derby271new.zip
>
> Need to document the new property - derby.system.durability
> This should probably go along with other properties in Tuning guide.
> --------------------------------------------------
> derby.system.durability
> Currently the only valid supported case insensitive value is 'test'
> If this property is set to any other value other than 'test', this
> property setting is ignored
> In the future, this property can be used to set different modes of durability
> - for example a form of relaxed durability where database can recover to a
> consistent state, or to enable some kind of in-memory mode.
> When set to 'test', the store system will not force sync calls in the
> following cases
> - for the log file at each commit
> - for the log file before data page is forced to disk
> - for page allocation when file is grown
> - for data writes during checkpoint
> That means
> - a commit no longer guarantees that the transaction's modification
> will survive a system crash or JVM termination
> - the database may not recover successfully upon restart
> - a near full disk at runtime may cause unexpected errors
> - database can be in an inconsistent state
> This setting is provided for performance reasons and should ideally
> only be used when the system can withstand the above consequences.
> One sample use would be to use this mode (derby.system.durability=test)
> when using Derby as a test database, where high performance is required
> and the data is not very important.
> If database is booted with derby.system.durability=test, the following warning message is logged in derby.log
> WARNING: The database is booted with derby.system.durability=test. In this mode, it is possible that database may not be able to recover, committed transactions may be lost, database may be in an inconsistent state. Please use this mode only when these consequences are acceptable
> and a similar message will appear in derby.log if the database was booted with derby.system.durability=test at any time previously.
> It is important to realize that once the database is booted with derby.system.durability=test, there are no guarantees on if the database is consistent or not.
> -------------------
> Valid supported values are test
> Example
> derby.system.durability=test
> One can set this as a command line option to the JVM when starting the
> application or in the derby.properties file. It is a system level
> property.
> This property is static; if you change it while Derby is running,
> the change does not take effect until you reboot.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-271) Document the new property derby.system.durability=test
Posted by "Jeff Levitt (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-271?page=all ]
Jeff Levitt updated DERBY-271:
------------------------------
Comment: was deleted
> Document the new property derby.system.durability=test
> ------------------------------------------------------
>
> Key: DERBY-271
> URL: http://issues.apache.org/jira/browse/DERBY-271
> Project: Derby
> Type: Sub-task
> Components: Documentation
> Versions: 10.1.0.0
> Reporter: Sunitha Kambhampati
>
> Need to document the new property - derby.system.durability
> This should probably go along with other properties in Tuning guide.
> --------------------------------------------------
> derby.system.durability
> Currently the only valid supported case insensitive value is 'test'
> If this property is set to any other value other than 'test', this
> property setting is ignored
> In the future, this property can be used to set different modes of durability
> - for example a form of relaxed durability where database can recover to a
> consistent state, or to enable some kind of in-memory mode.
> When set to 'test', the store system will not force sync calls in the
> following cases
> - for the log file at each commit
> - for the log file before data page is forced to disk
> - for page allocation when file is grown
> - for data writes during checkpoint
> That means
> - a commit no longer guarantees that the transaction's modification
> will survive a system crash or JVM termination
> - the database may not recover successfully upon restart
> - a near full disk at runtime may cause unexpected errors
> - database can be in an inconsistent state
> This setting is provided for performance reasons and should ideally
> only be used when the system can withstand the above consequences.
> One sample use would be to use this mode (derby.system.durability=test)
> when using Derby as a test database, where high performance is required
> and the data is not very important.
> If database is booted with derby.system.durability=test, the following warning message is logged in derby.log
> WARNING: The database is booted with derby.system.durability=test. In this mode, it is possible that database may not be able to recover, committed transactions may be lost, database may be in an inconsistent state. Please use this mode only when these consequences are acceptable
> and a similar message will appear in derby.log if the database was booted with derby.system.durability=test at any time previously.
> It is important to realize that once the database is booted with derby.system.durability=test, there are no guarantees on if the database is consistent or not.
> -------------------
> Valid supported values are test
> Example
> derby.system.durability=test
> One can set this as a command line option to the JVM when starting the
> application or in the derby.properties file. It is a system level
> property.
> This property is static; if you change it while Derby is running,
> the change does not take effect until you reboot.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
Re: [jira] Commented: (DERBY-271) Document the new property
derby.system.durability=test
Posted by David Van Couvering <da...@vancouvering.com>.
Wow, email is coming in slow (at least for me). I got this email at
6pm, it was sent out at 10am.
I'll take a look at this and have feedback for you tomorrow.
David
Jeff Levitt (JIRA) wrote:
> [ http://issues.apache.org/jira/browse/DERBY-271?page=comments#action_65519 ]
>
> Jeff Levitt commented on DERBY-271:
> -----------------------------------
>
> Could someone possibly review this so we can commit if all is OK? Thanks!
>
>
>>Document the new property derby.system.durability=test
>>------------------------------------------------------
>>
>> Key: DERBY-271
>> URL: http://issues.apache.org/jira/browse/DERBY-271
>> Project: Derby
>> Type: Sub-task
>> Components: Documentation
>> Versions: 10.1.0.0
>> Reporter: Sunitha Kambhampati
>> Assignee: Jeff Levitt
>> Attachments: derby271new.zip
>>
>>Need to document the new property - derby.system.durability
>>This should probably go along with other properties in Tuning guide.
>>--------------------------------------------------
>>derby.system.durability
>>Currently the only valid supported case insensitive value is 'test'
>>If this property is set to any other value other than 'test', this
>>property setting is ignored
>>In the future, this property can be used to set different modes of durability
>>- for example a form of relaxed durability where database can recover to a
>>consistent state, or to enable some kind of in-memory mode.
>>When set to 'test', the store system will not force sync calls in the
>>following cases
>>- for the log file at each commit
>>- for the log file before data page is forced to disk
>>- for page allocation when file is grown
>>- for data writes during checkpoint
>>That means
>>- a commit no longer guarantees that the transaction's modification
>>will survive a system crash or JVM termination
>>- the database may not recover successfully upon restart
>>- a near full disk at runtime may cause unexpected errors
>>- database can be in an inconsistent state
>>This setting is provided for performance reasons and should ideally
>>only be used when the system can withstand the above consequences.
>>One sample use would be to use this mode (derby.system.durability=test)
>>when using Derby as a test database, where high performance is required
>>and the data is not very important.
>>If database is booted with derby.system.durability=test, the following warning message is logged in derby.log
>>WARNING: The database is booted with derby.system.durability=test. In this mode, it is possible that database may not be able to recover, committed transactions may be lost, database may be in an inconsistent state. Please use this mode only when these consequences are acceptable
>>and a similar message will appear in derby.log if the database was booted with derby.system.durability=test at any time previously.
>>It is important to realize that once the database is booted with derby.system.durability=test, there are no guarantees on if the database is consistent or not.
>>-------------------
>>Valid supported values are test
>>Example
>>derby.system.durability=test
>>One can set this as a command line option to the JVM when starting the
>>application or in the derby.properties file. It is a system level
>>property.
>>This property is static; if you change it while Derby is running,
>>the change does not take effect until you reboot.
>
>
[jira] Commented: (DERBY-271) Document the new property derby.system.durability=test
Posted by "Jeff Levitt (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-271?page=comments#action_65519 ]
Jeff Levitt commented on DERBY-271:
-----------------------------------
Could someone possibly review this so we can commit if all is OK? Thanks!
> Document the new property derby.system.durability=test
> ------------------------------------------------------
>
> Key: DERBY-271
> URL: http://issues.apache.org/jira/browse/DERBY-271
> Project: Derby
> Type: Sub-task
> Components: Documentation
> Versions: 10.1.0.0
> Reporter: Sunitha Kambhampati
> Assignee: Jeff Levitt
> Attachments: derby271new.zip
>
> Need to document the new property - derby.system.durability
> This should probably go along with other properties in Tuning guide.
> --------------------------------------------------
> derby.system.durability
> Currently the only valid supported case insensitive value is 'test'
> If this property is set to any other value other than 'test', this
> property setting is ignored
> In the future, this property can be used to set different modes of durability
> - for example a form of relaxed durability where database can recover to a
> consistent state, or to enable some kind of in-memory mode.
> When set to 'test', the store system will not force sync calls in the
> following cases
> - for the log file at each commit
> - for the log file before data page is forced to disk
> - for page allocation when file is grown
> - for data writes during checkpoint
> That means
> - a commit no longer guarantees that the transaction's modification
> will survive a system crash or JVM termination
> - the database may not recover successfully upon restart
> - a near full disk at runtime may cause unexpected errors
> - database can be in an inconsistent state
> This setting is provided for performance reasons and should ideally
> only be used when the system can withstand the above consequences.
> One sample use would be to use this mode (derby.system.durability=test)
> when using Derby as a test database, where high performance is required
> and the data is not very important.
> If database is booted with derby.system.durability=test, the following warning message is logged in derby.log
> WARNING: The database is booted with derby.system.durability=test. In this mode, it is possible that database may not be able to recover, committed transactions may be lost, database may be in an inconsistent state. Please use this mode only when these consequences are acceptable
> and a similar message will appear in derby.log if the database was booted with derby.system.durability=test at any time previously.
> It is important to realize that once the database is booted with derby.system.durability=test, there are no guarantees on if the database is consistent or not.
> -------------------
> Valid supported values are test
> Example
> derby.system.durability=test
> One can set this as a command line option to the JVM when starting the
> application or in the derby.properties file. It is a system level
> property.
> This property is static; if you change it while Derby is running,
> the change does not take effect until you reboot.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Assigned: (DERBY-271) Document the new property derby.system.durability=test
Posted by "Jeff Levitt (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-271?page=all ]
Jeff Levitt reassigned DERBY-271:
---------------------------------
Assign To: Jeff Levitt
> Document the new property derby.system.durability=test
> ------------------------------------------------------
>
> Key: DERBY-271
> URL: http://issues.apache.org/jira/browse/DERBY-271
> Project: Derby
> Type: Sub-task
> Components: Documentation
> Versions: 10.1.0.0
> Reporter: Sunitha Kambhampati
> Assignee: Jeff Levitt
>
> Need to document the new property - derby.system.durability
> This should probably go along with other properties in Tuning guide.
> --------------------------------------------------
> derby.system.durability
> Currently the only valid supported case insensitive value is 'test'
> If this property is set to any other value other than 'test', this
> property setting is ignored
> In the future, this property can be used to set different modes of durability
> - for example a form of relaxed durability where database can recover to a
> consistent state, or to enable some kind of in-memory mode.
> When set to 'test', the store system will not force sync calls in the
> following cases
> - for the log file at each commit
> - for the log file before data page is forced to disk
> - for page allocation when file is grown
> - for data writes during checkpoint
> That means
> - a commit no longer guarantees that the transaction's modification
> will survive a system crash or JVM termination
> - the database may not recover successfully upon restart
> - a near full disk at runtime may cause unexpected errors
> - database can be in an inconsistent state
> This setting is provided for performance reasons and should ideally
> only be used when the system can withstand the above consequences.
> One sample use would be to use this mode (derby.system.durability=test)
> when using Derby as a test database, where high performance is required
> and the data is not very important.
> If database is booted with derby.system.durability=test, the following warning message is logged in derby.log
> WARNING: The database is booted with derby.system.durability=test. In this mode, it is possible that database may not be able to recover, committed transactions may be lost, database may be in an inconsistent state. Please use this mode only when these consequences are acceptable
> and a similar message will appear in derby.log if the database was booted with derby.system.durability=test at any time previously.
> It is important to realize that once the database is booted with derby.system.durability=test, there are no guarantees on if the database is consistent or not.
> -------------------
> Valid supported values are test
> Example
> derby.system.durability=test
> One can set this as a command line option to the JVM when starting the
> application or in the derby.properties file. It is a system level
> property.
> This property is static; if you change it while Derby is running,
> the change does not take effect until you reboot.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-271) Document the new property derby.system.durability=test
Posted by "Jeff Levitt (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-271?page=all ]
Jeff Levitt updated DERBY-271:
------------------------------
Attachment: derby271new.zip
Decided to add another change, this time to the main Properties overview page (ctunproper22250.dita) to add this property to the table on that page. I have deleted the old patch zip from this JIRA entry and added the new one, along with the HTML output for review.
> Document the new property derby.system.durability=test
> ------------------------------------------------------
>
> Key: DERBY-271
> URL: http://issues.apache.org/jira/browse/DERBY-271
> Project: Derby
> Type: Sub-task
> Components: Documentation
> Versions: 10.1.0.0
> Reporter: Sunitha Kambhampati
> Assignee: Jeff Levitt
> Attachments: derby271new.zip
>
> Need to document the new property - derby.system.durability
> This should probably go along with other properties in Tuning guide.
> --------------------------------------------------
> derby.system.durability
> Currently the only valid supported case insensitive value is 'test'
> If this property is set to any other value other than 'test', this
> property setting is ignored
> In the future, this property can be used to set different modes of durability
> - for example a form of relaxed durability where database can recover to a
> consistent state, or to enable some kind of in-memory mode.
> When set to 'test', the store system will not force sync calls in the
> following cases
> - for the log file at each commit
> - for the log file before data page is forced to disk
> - for page allocation when file is grown
> - for data writes during checkpoint
> That means
> - a commit no longer guarantees that the transaction's modification
> will survive a system crash or JVM termination
> - the database may not recover successfully upon restart
> - a near full disk at runtime may cause unexpected errors
> - database can be in an inconsistent state
> This setting is provided for performance reasons and should ideally
> only be used when the system can withstand the above consequences.
> One sample use would be to use this mode (derby.system.durability=test)
> when using Derby as a test database, where high performance is required
> and the data is not very important.
> If database is booted with derby.system.durability=test, the following warning message is logged in derby.log
> WARNING: The database is booted with derby.system.durability=test. In this mode, it is possible that database may not be able to recover, committed transactions may be lost, database may be in an inconsistent state. Please use this mode only when these consequences are acceptable
> and a similar message will appear in derby.log if the database was booted with derby.system.durability=test at any time previously.
> It is important to realize that once the database is booted with derby.system.durability=test, there are no guarantees on if the database is consistent or not.
> -------------------
> Valid supported values are test
> Example
> derby.system.durability=test
> One can set this as a command line option to the JVM when starting the
> application or in the derby.properties file. It is a system level
> property.
> This property is static; if you change it while Derby is running,
> the change does not take effect until you reboot.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Closed: (DERBY-271) Document the new property derby.system.durability=test
Posted by "Jean T. Anderson (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-271?page=all ]
Jean T. Anderson closed DERBY-271:
----------------------------------
Resolution: Fixed
Fix Version: 10.1.0.0
Committed, revision 170786, patch in derby271modifiedfinal.zip that adds documentation for the new derby.system.durability property to the Tuning Guide.
> Document the new property derby.system.durability=test
> ------------------------------------------------------
>
> Key: DERBY-271
> URL: http://issues.apache.org/jira/browse/DERBY-271
> Project: Derby
> Type: Sub-task
> Components: Documentation
> Versions: 10.1.0.0
> Reporter: Sunitha Kambhampati
> Assignee: Jeff Levitt
> Fix For: 10.1.0.0
> Attachments: derby271modifiedfinal.zip
>
> Need to document the new property - derby.system.durability
> This should probably go along with other properties in Tuning guide.
> --------------------------------------------------
> derby.system.durability
> Currently the only valid supported case insensitive value is 'test'
> If this property is set to any other value other than 'test', this
> property setting is ignored
> In the future, this property can be used to set different modes of durability
> - for example a form of relaxed durability where database can recover to a
> consistent state, or to enable some kind of in-memory mode.
> When set to 'test', the store system will not force sync calls in the
> following cases
> - for the log file at each commit
> - for the log file before data page is forced to disk
> - for page allocation when file is grown
> - for data writes during checkpoint
> That means
> - a commit no longer guarantees that the transaction's modification
> will survive a system crash or JVM termination
> - the database may not recover successfully upon restart
> - a near full disk at runtime may cause unexpected errors
> - database can be in an inconsistent state
> This setting is provided for performance reasons and should ideally
> only be used when the system can withstand the above consequences.
> One sample use would be to use this mode (derby.system.durability=test)
> when using Derby as a test database, where high performance is required
> and the data is not very important.
> If database is booted with derby.system.durability=test, the following warning message is logged in derby.log
> WARNING: The database is booted with derby.system.durability=test. In this mode, it is possible that database may not be able to recover, committed transactions may be lost, database may be in an inconsistent state. Please use this mode only when these consequences are acceptable
> and a similar message will appear in derby.log if the database was booted with derby.system.durability=test at any time previously.
> It is important to realize that once the database is booted with derby.system.durability=test, there are no guarantees on if the database is consistent or not.
> -------------------
> Valid supported values are test
> Example
> derby.system.durability=test
> One can set this as a command line option to the JVM when starting the
> application or in the derby.properties file. It is a system level
> property.
> This property is static; if you change it while Derby is running,
> the change does not take effect until you reboot.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Closed: (DERBY-271) Document the new property derby.system.durability=test
Posted by "Jeff Levitt (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-271?page=all ]
Jeff Levitt closed DERBY-271:
-----------------------------
Resolution: Invalid
Fix Version: (was: 10.1.0.0)
The dita page already correctly indicates to use the trunk directory. My mistake!
> Document the new property derby.system.durability=test
> ------------------------------------------------------
>
> Key: DERBY-271
> URL: http://issues.apache.org/jira/browse/DERBY-271
> Project: Derby
> Type: Sub-task
> Components: Documentation
> Versions: 10.1.0.0
> Reporter: Sunitha Kambhampati
>
> Need to document the new property - derby.system.durability
> This should probably go along with other properties in Tuning guide.
> --------------------------------------------------
> derby.system.durability
> Currently the only valid supported case insensitive value is 'test'
> If this property is set to any other value other than 'test', this
> property setting is ignored
> In the future, this property can be used to set different modes of durability
> - for example a form of relaxed durability where database can recover to a
> consistent state, or to enable some kind of in-memory mode.
> When set to 'test', the store system will not force sync calls in the
> following cases
> - for the log file at each commit
> - for the log file before data page is forced to disk
> - for page allocation when file is grown
> - for data writes during checkpoint
> That means
> - a commit no longer guarantees that the transaction's modification
> will survive a system crash or JVM termination
> - the database may not recover successfully upon restart
> - a near full disk at runtime may cause unexpected errors
> - database can be in an inconsistent state
> This setting is provided for performance reasons and should ideally
> only be used when the system can withstand the above consequences.
> One sample use would be to use this mode (derby.system.durability=test)
> when using Derby as a test database, where high performance is required
> and the data is not very important.
> If database is booted with derby.system.durability=test, the following warning message is logged in derby.log
> WARNING: The database is booted with derby.system.durability=test. In this mode, it is possible that database may not be able to recover, committed transactions may be lost, database may be in an inconsistent state. Please use this mode only when these consequences are acceptable
> and a similar message will appear in derby.log if the database was booted with derby.system.durability=test at any time previously.
> It is important to realize that once the database is booted with derby.system.durability=test, there are no guarantees on if the database is consistent or not.
> -------------------
> Valid supported values are test
> Example
> derby.system.durability=test
> One can set this as a command line option to the JVM when starting the
> application or in the derby.properties file. It is a system level
> property.
> This property is static; if you change it while Derby is running,
> the change does not take effect until you reboot.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-271) Document the new property derby.system.durability=test
Posted by "Jeff Levitt (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-271?page=all ]
Jeff Levitt updated DERBY-271:
------------------------------
Attachment: derby271modified.zip
The attached zip contains your changes plus output for review. I stayed away from mentioning anything that had to do with the future. For example, I didn't mention that we "currently" support only 'test', I instead just said that we only support 'test.' When we add support for any other values, then we'll just modify the docs to include it. The idea is to avoid making promises to users that we may not be able to keep, because adding support for more values might get pushed to a later time, no one may have the resources to change the code, etc. So I tried to avoid saying anything about the future, or anything but what the code currently does.
> Document the new property derby.system.durability=test
> ------------------------------------------------------
>
> Key: DERBY-271
> URL: http://issues.apache.org/jira/browse/DERBY-271
> Project: Derby
> Type: Sub-task
> Components: Documentation
> Versions: 10.1.0.0
> Reporter: Sunitha Kambhampati
> Assignee: Jeff Levitt
> Attachments: derby271modified.zip
>
> Need to document the new property - derby.system.durability
> This should probably go along with other properties in Tuning guide.
> --------------------------------------------------
> derby.system.durability
> Currently the only valid supported case insensitive value is 'test'
> If this property is set to any other value other than 'test', this
> property setting is ignored
> In the future, this property can be used to set different modes of durability
> - for example a form of relaxed durability where database can recover to a
> consistent state, or to enable some kind of in-memory mode.
> When set to 'test', the store system will not force sync calls in the
> following cases
> - for the log file at each commit
> - for the log file before data page is forced to disk
> - for page allocation when file is grown
> - for data writes during checkpoint
> That means
> - a commit no longer guarantees that the transaction's modification
> will survive a system crash or JVM termination
> - the database may not recover successfully upon restart
> - a near full disk at runtime may cause unexpected errors
> - database can be in an inconsistent state
> This setting is provided for performance reasons and should ideally
> only be used when the system can withstand the above consequences.
> One sample use would be to use this mode (derby.system.durability=test)
> when using Derby as a test database, where high performance is required
> and the data is not very important.
> If database is booted with derby.system.durability=test, the following warning message is logged in derby.log
> WARNING: The database is booted with derby.system.durability=test. In this mode, it is possible that database may not be able to recover, committed transactions may be lost, database may be in an inconsistent state. Please use this mode only when these consequences are acceptable
> and a similar message will appear in derby.log if the database was booted with derby.system.durability=test at any time previously.
> It is important to realize that once the database is booted with derby.system.durability=test, there are no guarantees on if the database is consistent or not.
> -------------------
> Valid supported values are test
> Example
> derby.system.durability=test
> One can set this as a command line option to the JVM when starting the
> application or in the derby.properties file. It is a system level
> property.
> This property is static; if you change it while Derby is running,
> the change does not take effect until you reboot.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Reopened: (DERBY-271) Document the new property derby.system.durability=test
Posted by "Jeff Levitt (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-271?page=all ]
Jeff Levitt reopened DERBY-271:
-------------------------------
Sorry, I closed the wrong issue!
> Document the new property derby.system.durability=test
> ------------------------------------------------------
>
> Key: DERBY-271
> URL: http://issues.apache.org/jira/browse/DERBY-271
> Project: Derby
> Type: Sub-task
> Components: Documentation
> Versions: 10.1.0.0
> Reporter: Sunitha Kambhampati
>
> Need to document the new property - derby.system.durability
> This should probably go along with other properties in Tuning guide.
> --------------------------------------------------
> derby.system.durability
> Currently the only valid supported case insensitive value is 'test'
> If this property is set to any other value other than 'test', this
> property setting is ignored
> In the future, this property can be used to set different modes of durability
> - for example a form of relaxed durability where database can recover to a
> consistent state, or to enable some kind of in-memory mode.
> When set to 'test', the store system will not force sync calls in the
> following cases
> - for the log file at each commit
> - for the log file before data page is forced to disk
> - for page allocation when file is grown
> - for data writes during checkpoint
> That means
> - a commit no longer guarantees that the transaction's modification
> will survive a system crash or JVM termination
> - the database may not recover successfully upon restart
> - a near full disk at runtime may cause unexpected errors
> - database can be in an inconsistent state
> This setting is provided for performance reasons and should ideally
> only be used when the system can withstand the above consequences.
> One sample use would be to use this mode (derby.system.durability=test)
> when using Derby as a test database, where high performance is required
> and the data is not very important.
> If database is booted with derby.system.durability=test, the following warning message is logged in derby.log
> WARNING: The database is booted with derby.system.durability=test. In this mode, it is possible that database may not be able to recover, committed transactions may be lost, database may be in an inconsistent state. Please use this mode only when these consequences are acceptable
> and a similar message will appear in derby.log if the database was booted with derby.system.durability=test at any time previously.
> It is important to realize that once the database is booted with derby.system.durability=test, there are no guarantees on if the database is consistent or not.
> -------------------
> Valid supported values are test
> Example
> derby.system.durability=test
> One can set this as a command line option to the JVM when starting the
> application or in the derby.properties file. It is a system level
> property.
> This property is static; if you change it while Derby is running,
> the change does not take effect until you reboot.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (DERBY-271) Document the new property derby.system.durability=test
Posted by "Sunitha Kambhampati (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-271?page=comments#action_65628 ]
Sunitha Kambhampati commented on DERBY-271:
-------------------------------------------
All looks good. just a minor comment. how about saying I/O synchronization calls instead of just synchronization calls in the first para.
Thanks again for getting it out so quickly.
> Document the new property derby.system.durability=test
> ------------------------------------------------------
>
> Key: DERBY-271
> URL: http://issues.apache.org/jira/browse/DERBY-271
> Project: Derby
> Type: Sub-task
> Components: Documentation
> Versions: 10.1.0.0
> Reporter: Sunitha Kambhampati
> Assignee: Jeff Levitt
> Attachments: derby271modified.zip
>
> Need to document the new property - derby.system.durability
> This should probably go along with other properties in Tuning guide.
> --------------------------------------------------
> derby.system.durability
> Currently the only valid supported case insensitive value is 'test'
> If this property is set to any other value other than 'test', this
> property setting is ignored
> In the future, this property can be used to set different modes of durability
> - for example a form of relaxed durability where database can recover to a
> consistent state, or to enable some kind of in-memory mode.
> When set to 'test', the store system will not force sync calls in the
> following cases
> - for the log file at each commit
> - for the log file before data page is forced to disk
> - for page allocation when file is grown
> - for data writes during checkpoint
> That means
> - a commit no longer guarantees that the transaction's modification
> will survive a system crash or JVM termination
> - the database may not recover successfully upon restart
> - a near full disk at runtime may cause unexpected errors
> - database can be in an inconsistent state
> This setting is provided for performance reasons and should ideally
> only be used when the system can withstand the above consequences.
> One sample use would be to use this mode (derby.system.durability=test)
> when using Derby as a test database, where high performance is required
> and the data is not very important.
> If database is booted with derby.system.durability=test, the following warning message is logged in derby.log
> WARNING: The database is booted with derby.system.durability=test. In this mode, it is possible that database may not be able to recover, committed transactions may be lost, database may be in an inconsistent state. Please use this mode only when these consequences are acceptable
> and a similar message will appear in derby.log if the database was booted with derby.system.durability=test at any time previously.
> It is important to realize that once the database is booted with derby.system.durability=test, there are no guarantees on if the database is consistent or not.
> -------------------
> Valid supported values are test
> Example
> derby.system.durability=test
> One can set this as a command line option to the JVM when starting the
> application or in the derby.properties file. It is a system level
> property.
> This property is static; if you change it while Derby is running,
> the change does not take effect until you reboot.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (DERBY-271) Document the new property derby.system.durability=test
Posted by "Sunitha Kambhampati (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-271?page=comments#action_65635 ]
Sunitha Kambhampati commented on DERBY-271:
-------------------------------------------
It looks good to me now.
> Document the new property derby.system.durability=test
> ------------------------------------------------------
>
> Key: DERBY-271
> URL: http://issues.apache.org/jira/browse/DERBY-271
> Project: Derby
> Type: Sub-task
> Components: Documentation
> Versions: 10.1.0.0
> Reporter: Sunitha Kambhampati
> Assignee: Jeff Levitt
> Attachments: derby271modifiedfinal.zip
>
> Need to document the new property - derby.system.durability
> This should probably go along with other properties in Tuning guide.
> --------------------------------------------------
> derby.system.durability
> Currently the only valid supported case insensitive value is 'test'
> If this property is set to any other value other than 'test', this
> property setting is ignored
> In the future, this property can be used to set different modes of durability
> - for example a form of relaxed durability where database can recover to a
> consistent state, or to enable some kind of in-memory mode.
> When set to 'test', the store system will not force sync calls in the
> following cases
> - for the log file at each commit
> - for the log file before data page is forced to disk
> - for page allocation when file is grown
> - for data writes during checkpoint
> That means
> - a commit no longer guarantees that the transaction's modification
> will survive a system crash or JVM termination
> - the database may not recover successfully upon restart
> - a near full disk at runtime may cause unexpected errors
> - database can be in an inconsistent state
> This setting is provided for performance reasons and should ideally
> only be used when the system can withstand the above consequences.
> One sample use would be to use this mode (derby.system.durability=test)
> when using Derby as a test database, where high performance is required
> and the data is not very important.
> If database is booted with derby.system.durability=test, the following warning message is logged in derby.log
> WARNING: The database is booted with derby.system.durability=test. In this mode, it is possible that database may not be able to recover, committed transactions may be lost, database may be in an inconsistent state. Please use this mode only when these consequences are acceptable
> and a similar message will appear in derby.log if the database was booted with derby.system.durability=test at any time previously.
> It is important to realize that once the database is booted with derby.system.durability=test, there are no guarantees on if the database is consistent or not.
> -------------------
> Valid supported values are test
> Example
> derby.system.durability=test
> One can set this as a command line option to the JVM when starting the
> application or in the derby.properties file. It is a system level
> property.
> This property is static; if you change it while Derby is running,
> the change does not take effect until you reboot.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-271) Document the new property derby.system.durability=test
Posted by "Jeff Levitt (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-271?page=all ]
Jeff Levitt updated DERBY-271:
------------------------------
Attachment: derby271.zip
This patch creates a new file, rtunproperdurability.dita, for the Tuning Guide. It places this new file, which is titled "derby.system.durability", right before the "derby.system.home" property, so that it appears in alphabetical order in the Properties section of the Tuning Guide. I have included the HTML output of this new page for review in the zip file with the patch.
This patch should only be committed when the parent task for adding this functionality has been committed.
> Document the new property derby.system.durability=test
> ------------------------------------------------------
>
> Key: DERBY-271
> URL: http://issues.apache.org/jira/browse/DERBY-271
> Project: Derby
> Type: Sub-task
> Components: Documentation
> Versions: 10.1.0.0
> Reporter: Sunitha Kambhampati
> Assignee: Jeff Levitt
> Attachments: derby271.zip
>
> Need to document the new property - derby.system.durability
> This should probably go along with other properties in Tuning guide.
> --------------------------------------------------
> derby.system.durability
> Currently the only valid supported case insensitive value is 'test'
> If this property is set to any other value other than 'test', this
> property setting is ignored
> In the future, this property can be used to set different modes of durability
> - for example a form of relaxed durability where database can recover to a
> consistent state, or to enable some kind of in-memory mode.
> When set to 'test', the store system will not force sync calls in the
> following cases
> - for the log file at each commit
> - for the log file before data page is forced to disk
> - for page allocation when file is grown
> - for data writes during checkpoint
> That means
> - a commit no longer guarantees that the transaction's modification
> will survive a system crash or JVM termination
> - the database may not recover successfully upon restart
> - a near full disk at runtime may cause unexpected errors
> - database can be in an inconsistent state
> This setting is provided for performance reasons and should ideally
> only be used when the system can withstand the above consequences.
> One sample use would be to use this mode (derby.system.durability=test)
> when using Derby as a test database, where high performance is required
> and the data is not very important.
> If database is booted with derby.system.durability=test, the following warning message is logged in derby.log
> WARNING: The database is booted with derby.system.durability=test. In this mode, it is possible that database may not be able to recover, committed transactions may be lost, database may be in an inconsistent state. Please use this mode only when these consequences are acceptable
> and a similar message will appear in derby.log if the database was booted with derby.system.durability=test at any time previously.
> It is important to realize that once the database is booted with derby.system.durability=test, there are no guarantees on if the database is consistent or not.
> -------------------
> Valid supported values are test
> Example
> derby.system.durability=test
> One can set this as a command line option to the JVM when starting the
> application or in the derby.properties file. It is a system level
> property.
> This property is static; if you change it while Derby is running,
> the change does not take effect until you reboot.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-271) Document the new property derby.system.durability=test
Posted by "Jeff Levitt (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-271?page=all ]
Jeff Levitt updated DERBY-271:
------------------------------
Attachment: derby271modifiedfinal.zip
Here's an updated patch...can you review it again and comment that it looks good and can be committed if that's the case? Thanks!
> Document the new property derby.system.durability=test
> ------------------------------------------------------
>
> Key: DERBY-271
> URL: http://issues.apache.org/jira/browse/DERBY-271
> Project: Derby
> Type: Sub-task
> Components: Documentation
> Versions: 10.1.0.0
> Reporter: Sunitha Kambhampati
> Assignee: Jeff Levitt
> Attachments: derby271modifiedfinal.zip
>
> Need to document the new property - derby.system.durability
> This should probably go along with other properties in Tuning guide.
> --------------------------------------------------
> derby.system.durability
> Currently the only valid supported case insensitive value is 'test'
> If this property is set to any other value other than 'test', this
> property setting is ignored
> In the future, this property can be used to set different modes of durability
> - for example a form of relaxed durability where database can recover to a
> consistent state, or to enable some kind of in-memory mode.
> When set to 'test', the store system will not force sync calls in the
> following cases
> - for the log file at each commit
> - for the log file before data page is forced to disk
> - for page allocation when file is grown
> - for data writes during checkpoint
> That means
> - a commit no longer guarantees that the transaction's modification
> will survive a system crash or JVM termination
> - the database may not recover successfully upon restart
> - a near full disk at runtime may cause unexpected errors
> - database can be in an inconsistent state
> This setting is provided for performance reasons and should ideally
> only be used when the system can withstand the above consequences.
> One sample use would be to use this mode (derby.system.durability=test)
> when using Derby as a test database, where high performance is required
> and the data is not very important.
> If database is booted with derby.system.durability=test, the following warning message is logged in derby.log
> WARNING: The database is booted with derby.system.durability=test. In this mode, it is possible that database may not be able to recover, committed transactions may be lost, database may be in an inconsistent state. Please use this mode only when these consequences are acceptable
> and a similar message will appear in derby.log if the database was booted with derby.system.durability=test at any time previously.
> It is important to realize that once the database is booted with derby.system.durability=test, there are no guarantees on if the database is consistent or not.
> -------------------
> Valid supported values are test
> Example
> derby.system.durability=test
> One can set this as a command line option to the JVM when starting the
> application or in the derby.properties file. It is a system level
> property.
> This property is static; if you change it while Derby is running,
> the change does not take effect until you reboot.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira