Skip to content

Change the new ensemble log to info level#4566

Merged
hangc0276 merged 1 commit into
apache:masterfrom
zymap:yong/change-log-to-info
Mar 19, 2025
Merged

Change the new ensemble log to info level#4566
hangc0276 merged 1 commit into
apache:masterfrom
zymap:yong/change-log-to-info

Conversation

@zymap

@zymap zymap commented Mar 10, 2025

Copy link
Copy Markdown
Member

Motivation

Change the new ensemble log to the info level. Sometimes, the ensemble may not satisfied with the placement policy. The log should be info level but not a warn level. Because it will fix by the auto recovery later, so this just a information from the ensemble choose.

---

### Motivation

Change the new ensemble log to the info level. Sometimes, the ensemble
may not satisfied with the placement policy. The log should be info
level but not a warn level. Because it will fix by the auto recovery
later, so this just a information from the ensemble choose.
@hangc0276
hangc0276 merged commit a12943d into apache:master Mar 19, 2025
zymap added a commit that referenced this pull request Apr 7, 2025
---

### Motivation

Change the new ensemble log to the info level. Sometimes, the ensemble
may not satisfied with the placement policy. The log should be info
level but not a warn level. Because it will fix by the auto recovery
later, so this just a information from the ensemble choose.

(cherry picked from commit a12943d)
zymap added a commit that referenced this pull request Apr 7, 2025
---

### Motivation

Change the new ensemble log to the info level. Sometimes, the ensemble
may not satisfied with the placement policy. The log should be info
level but not a warn level. Because it will fix by the auto recovery
later, so this just a information from the ensemble choose.

(cherry picked from commit a12943d)
priyanshu-ctds pushed a commit to datastax/bookkeeper that referenced this pull request Jul 11, 2025
---

### Motivation

Change the new ensemble log to the info level. Sometimes, the ensemble
may not satisfied with the placement policy. The log should be info
level but not a warn level. Because it will fix by the auto recovery
later, so this just a information from the ensemble choose.

(cherry picked from commit a12943d)
(cherry picked from commit a753ace)
sandeep-ctds pushed a commit to datastax/bookkeeper that referenced this pull request Jul 22, 2025
---

### Motivation

Change the new ensemble log to the info level. Sometimes, the ensemble
may not satisfied with the placement policy. The log should be info
level but not a warn level. Because it will fix by the auto recovery
later, so this just a information from the ensemble choose.

(cherry picked from commit a12943d)
(cherry picked from commit a753ace)
manas-ctds pushed a commit to datastax/bookkeeper that referenced this pull request Feb 27, 2026
---

### Motivation

Change the new ensemble log to the info level. Sometimes, the ensemble
may not satisfied with the placement policy. The log should be info
level but not a warn level. Because it will fix by the auto recovery
later, so this just a information from the ensemble choose.

(cherry picked from commit a12943d)
(cherry picked from commit 0ce47aa)
dlg99 pushed a commit to datastax/bookkeeper that referenced this pull request Feb 27, 2026
---

### Motivation

Change the new ensemble log to the info level. Sometimes, the ensemble
may not satisfied with the placement policy. The log should be info
level but not a warn level. Because it will fix by the auto recovery
later, so this just a information from the ensemble choose.

(cherry picked from commit a12943d)
(cherry picked from commit 0ce47aa)
@hangc0276 hangc0276 added this to the 4.18.0 milestone May 29, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants