Couchbase Server

memcached exited when disk image malformed

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Won't Fix
  • Affects Version/s: 1.8.1
  • Fix Version/s: .next
  • Component/s: couchbase-bucket
  • Security Level: Public
  • Labels:
    None

Description

[error_logger:error] [2012-08-04 18:55:47] [ns_1@10.8.0.97:error_logger:ale_error_logger_handler:log_msg:76] ** Generic server <0.395.0> terminating
** Last message in was {#Port<0.4901>,{exit_status,255}}
** When Server state == {state,#Port<0.4901>,memcached,
                               {[[],
                                 "Fatal error in persisting SET ``42dbfe23-24ad-4e22-9f15-2ccbdc8cd97f'' on vb 670!!! Requeue it...",
                                 "Fatal sqlite error in updating key '42dbfe23-24ad-4e22-9f15-2ccbdc8cd97f' !!! Reopen the database...",
                                 "sqlite error: database disk image is malformed",
...


I would think we shouldn't need to exit the whole process when unable to write to the disk, correct?

Activity

Hide
Permalink
Perry Krug added a comment -
Even though sqlite is just for 1.x, the problem of being unable to write to disk could still be present in 2.0 and should not cause the process to exit.
Show
Perry Krug added a comment - Even though sqlite is just for 1.x, the problem of being unable to write to disk could still be present in 2.0 and should not cause the process to exit.

People

  • Assignee:
    Chiyoung Seo
    Reporter:
    Perry Krug
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: