Skip to content

Update log#1840

Merged
martinsumner merged 1 commit into
develop-3.0from
mas-i1824-crashfold
Dec 16, 2022
Merged

Update log#1840
martinsumner merged 1 commit into
develop-3.0from
mas-i1824-crashfold

Conversation

@martinsumner

Copy link
Copy Markdown
Contributor

Make situation clearer in log

Rather than change behaviour, just make it clear that the warning can be ignored when shutting down. This should avoid unnecessary concern.

Make situation clearer in log

Rather than change behaviour, just make it clear that the warning can be ignored when shutting down.  This should avoid unnecessary concern.
@azharnisar

Copy link
Copy Markdown

+1

@martinsumner
martinsumner merged commit f3aef17 into develop-3.0 Dec 16, 2022
martinsumner added a commit that referenced this pull request Dec 19, 2022
Make situation clearer in log

Rather than change behaviour, just make it clear that the warning can be ignored when shutting down.  This should avoid unnecessary concern.
martinsumner added a commit that referenced this pull request Dec 19, 2022
* Do not crash when object's contents is an empty list (#1837)

* Add test to illustrate issue

* Do not crash when object's contents is an empty list

* add missing function clause repair_keys_range in convert_fold (#1839)

* add missing function clause repair_keys_range in convert_fold, to unbreak aae_fold for that case

* thread converted aae_fold query in riak_client, to complete prev commit

* Change the default PR value from 0 to default (#1836)

This means that get requests will use bucket-type level Primary Read settings

Co-authored-by: Peter Tihanyi <[email protected]>

* Mas i1121 reip3 (#1838)

* Add reip/3

To allow for reip without loading the riak_core application

* Use alternate name

* Update riak_kv_console.erl

* Update riak_kv_console.erl

* reip_manual inputs are atoms

* Add warning to update riak.conf file after reip

* Make clear where attention is required

And return 'ok' to make clear the op was successful

* Update rebar.config

* Update log (#1840)

Make situation clearer in log

Rather than change behaviour, just make it clear that the warning can be ignored when shutting down.  This should avoid unnecessary concern.

* Update Readme, remove mercurial refs

Co-authored-by: Enrique Fernández <[email protected]>
Co-authored-by: Andrei Zavada <[email protected]>
Co-authored-by: Peter Tihanyi <[email protected]>
Co-authored-by: Peter Tihanyi <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants