You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 23, 2020. It is now read-only.
Hi, we are expecting issues when trying to create index backup to s3 bucket.
Exhibitor is made by maven and run by: java -jar exhibitor-1.6.0.jar -c s3 --s3credentials /srv/exhibitor/aws_cred --s3config bucket:key --s3configprefix prefix --s3backup true
Exhibitor running, and communicating with zookeper. We are using 3 node shared config with s3.
When i am trying to create "New Index" on GUI Backup and Restore page, there are some new files on s3, but Backup/restore page list is empty.
In exhibitor log i see: INFO com.netflix.exhibitor.core.activity.ActivityLog Starting index build [ActivityQueue-1] ERROR com.netflix.exhibitor.core.activity.ActivityLog Index Build: Getting available backups [ActivityQueue-1] ERROR com.netflix.exhibitor.core.activity.ActivityLog Index Build: there are 6 available backups [ActivityQueue-1] INFO com.netflix.exhibitor.core.activity.ActivityLog Index Build: indexing backup log 1 of 6 [ActivityQueue-1] WARN com.amazonaws.services.s3.internal.S3AbortableInputStream Not all bytes were read from the S3ObjectInputStream, aborting HTTP connection. This is likely an error and may result in sub-optimal behavior. Request only the bytes you need via a ranged GET or drain the input stream after use. [ActivityQueue-1] INFO com.netflix.exhibitor.core.activity.ActivityLog Index Build: indexing backup log 2 of 6 [ActivityQueue-1] WARN com.amazonaws.services.s3.internal.S3AbortableInputStream Not all bytes were read from the S3ObjectInputStream, aborting HTTP connection. This is likely an error and may result in sub-optimal behavior. Request only the bytes you need via a ranged GET or drain the input stream after use. [ActivityQueue-1] INFO com.netflix.exhibitor.core.activity.ActivityLog Index Build: indexing backup log 3 of 6 [ActivityQueue-1] WARN com.amazonaws.services.s3.internal.S3AbortableInputStream Not all bytes were read from the S3ObjectInputStream, aborting HTTP connection. This is likely an error and may result in sub-optimal behavior. Request only the bytes you need via a ranged GET or drain the input stream after use. [ActivityQueue-1] INFO com.netflix.exhibitor.core.activity.ActivityLog Index Build: indexing backup log 4 of 6 [ActivityQueue-1] WARN com.amazonaws.services.s3.internal.S3AbortableInputStream Not all bytes were read from the S3ObjectInputStream, aborting HTTP connection. This is likely an error and may result in sub-optimal behavior. Request only the bytes you need via a ranged GET or drain the input stream after use. [ActivityQueue-1] INFO com.netflix.exhibitor.core.activity.ActivityLog Index Build: indexing backup log 5 of 6 [ActivityQueue-1] WARN com.amazonaws.services.s3.internal.S3AbortableInputStream Not all bytes were read from the S3ObjectInputStream, aborting HTTP connection. This is likely an error and may result in sub-optimal behavior. Request only the bytes you need via a ranged GET or drain the input stream after use. [ActivityQueue-1] INFO com.netflix.exhibitor.core.activity.ActivityLog Index Build: indexing backup log 6 of 6 [ActivityQueue-1] WARN com.amazonaws.services.s3.internal.S3AbortableInputStream Not all bytes were read from the S3ObjectInputStream, aborting HTTP connection. This is likely an error and may result in sub-optimal behavior. Request only the bytes you need via a ranged GET or drain the input stream after use. [ActivityQueue-1] INFO com.netflix.exhibitor.core.activity.ActivityLog Indexing active log 1 of 4 [ActivityQueue-1] INFO com.netflix.exhibitor.core.activity.ActivityLog Indexing active log 2 of 4 [ActivityQueue-1] INFO com.netflix.exhibitor.core.activity.ActivityLog Indexing active log 3 of 4 [ActivityQueue-1] INFO com.netflix.exhibitor.core.activity.ActivityLog Indexing active log 4 of 4 [ActivityQueue-1] INFO com.netflix.exhibitor.core.activity.ActivityLog Index completed: /exhibitor-1522852941289 [ActivityQueue-1]
Thanks for any help.
The text was updated successfully, but these errors were encountered:
Hi, we are expecting issues when trying to create index backup to s3 bucket.
Exhibitor is made by maven and run by:
java -jar exhibitor-1.6.0.jar -c s3 --s3credentials /srv/exhibitor/aws_cred --s3config bucket:key --s3configprefix prefix --s3backup true
Exhibitor running, and communicating with zookeper. We are using 3 node shared config with s3.
When i am trying to create "New Index" on GUI Backup and Restore page, there are some new files on s3, but Backup/restore page list is empty.
In exhibitor log i see:
INFO com.netflix.exhibitor.core.activity.ActivityLog Starting index build [ActivityQueue-1] ERROR com.netflix.exhibitor.core.activity.ActivityLog Index Build: Getting available backups [ActivityQueue-1] ERROR com.netflix.exhibitor.core.activity.ActivityLog Index Build: there are 6 available backups [ActivityQueue-1] INFO com.netflix.exhibitor.core.activity.ActivityLog Index Build: indexing backup log 1 of 6 [ActivityQueue-1] WARN com.amazonaws.services.s3.internal.S3AbortableInputStream Not all bytes were read from the S3ObjectInputStream, aborting HTTP connection. This is likely an error and may result in sub-optimal behavior. Request only the bytes you need via a ranged GET or drain the input stream after use. [ActivityQueue-1] INFO com.netflix.exhibitor.core.activity.ActivityLog Index Build: indexing backup log 2 of 6 [ActivityQueue-1] WARN com.amazonaws.services.s3.internal.S3AbortableInputStream Not all bytes were read from the S3ObjectInputStream, aborting HTTP connection. This is likely an error and may result in sub-optimal behavior. Request only the bytes you need via a ranged GET or drain the input stream after use. [ActivityQueue-1] INFO com.netflix.exhibitor.core.activity.ActivityLog Index Build: indexing backup log 3 of 6 [ActivityQueue-1] WARN com.amazonaws.services.s3.internal.S3AbortableInputStream Not all bytes were read from the S3ObjectInputStream, aborting HTTP connection. This is likely an error and may result in sub-optimal behavior. Request only the bytes you need via a ranged GET or drain the input stream after use. [ActivityQueue-1] INFO com.netflix.exhibitor.core.activity.ActivityLog Index Build: indexing backup log 4 of 6 [ActivityQueue-1] WARN com.amazonaws.services.s3.internal.S3AbortableInputStream Not all bytes were read from the S3ObjectInputStream, aborting HTTP connection. This is likely an error and may result in sub-optimal behavior. Request only the bytes you need via a ranged GET or drain the input stream after use. [ActivityQueue-1] INFO com.netflix.exhibitor.core.activity.ActivityLog Index Build: indexing backup log 5 of 6 [ActivityQueue-1] WARN com.amazonaws.services.s3.internal.S3AbortableInputStream Not all bytes were read from the S3ObjectInputStream, aborting HTTP connection. This is likely an error and may result in sub-optimal behavior. Request only the bytes you need via a ranged GET or drain the input stream after use. [ActivityQueue-1] INFO com.netflix.exhibitor.core.activity.ActivityLog Index Build: indexing backup log 6 of 6 [ActivityQueue-1] WARN com.amazonaws.services.s3.internal.S3AbortableInputStream Not all bytes were read from the S3ObjectInputStream, aborting HTTP connection. This is likely an error and may result in sub-optimal behavior. Request only the bytes you need via a ranged GET or drain the input stream after use. [ActivityQueue-1] INFO com.netflix.exhibitor.core.activity.ActivityLog Indexing active log 1 of 4 [ActivityQueue-1] INFO com.netflix.exhibitor.core.activity.ActivityLog Indexing active log 2 of 4 [ActivityQueue-1] INFO com.netflix.exhibitor.core.activity.ActivityLog Indexing active log 3 of 4 [ActivityQueue-1] INFO com.netflix.exhibitor.core.activity.ActivityLog Indexing active log 4 of 4 [ActivityQueue-1] INFO com.netflix.exhibitor.core.activity.ActivityLog Index completed: /exhibitor-1522852941289 [ActivityQueue-1]
Thanks for any help.
The text was updated successfully, but these errors were encountered: