Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Not Getting installed #3333

Closed
vasanthakumarr opened this issue Jul 15, 2013 · 1 comment
Closed

Not Getting installed #3333

vasanthakumarr opened this issue Jul 15, 2013 · 1 comment

Comments

@vasanthakumarr
Copy link

Hi All,

This is the error i am getting while installing the plugin in for river-jdbc in windows,
Plugin installation assumed to be site plugin, but contains source code, abortin
g installation...
Kindly give the solutions asap
@Paikan
Copy link
Contributor

Paikan commented Jul 15, 2013

Please consider closing this ticket and asking this kind of questions in the ES mailing list http://www.elasticsearch.org/community/ there will be a wider audience there to answer and won't pollute issues.

dnhatn added a commit that referenced this issue Feb 1, 2019
@dnhatn
Enable trace log in FollowerFailOverIT (#38148)
3ecdfe1 
This suite still fails one per week sometimes with a worrying assertion.
Sadly we are still unable to find the actual source.

Expected: <SeqNoStats{maxSeqNo=229, localCheckpoint=86, globalCheckpoint=86}>
but: was   <SeqNoStats{maxSeqNo=229, localCheckpoint=-1, globalCheckpoint=86}>

This change enables trace log in the suite so we will have a better
picture if this fails again.

Relates #3333
dnhatn added a commit to dnhatn/elasticsearch that referenced this issue Feb 3, 2019
@dnhatn
Enable trace log in FollowerFailOverIT (elastic#38148)
ba1ec32 
This suite still fails one per week sometimes with a worrying assertion.
Sadly we are still unable to find the actual source.

Expected: <SeqNoStats{maxSeqNo=229, localCheckpoint=86, globalCheckpoint=86}>
but: was   <SeqNoStats{maxSeqNo=229, localCheckpoint=-1, globalCheckpoint=86}>

This change enables trace log in the suite so we will have a better
picture if this fails again.

Relates elastic#3333
@dnhatn dnhatn mentioned this issue Feb 3, 2019
Merged
dnhatn added a commit that referenced this issue Feb 3, 2019
@dnhatn
Enable trace log in FollowerFailOverIT (#38148)
920eba2 
This suite still fails one per week sometimes with a worrying assertion.
Sadly we are still unable to find the actual source.

Expected: <SeqNoStats{maxSeqNo=229, localCheckpoint=86, globalCheckpoint=86}>
but: was   <SeqNoStats{maxSeqNo=229, localCheckpoint=-1, globalCheckpoint=86}>

This change enables trace log in the suite so we will have a better
picture if this fails again.

Relates #3333
dnhatn added a commit that referenced this issue Feb 3, 2019
@dnhatn
Enable trace log in FollowerFailOverIT (#38148)
3bca1aa 
This suite still fails one per week sometimes with a worrying assertion.
Sadly we are still unable to find the actual source.

Expected: <SeqNoStats{maxSeqNo=229, localCheckpoint=86, globalCheckpoint=86}>
but: was   <SeqNoStats{maxSeqNo=229, localCheckpoint=-1, globalCheckpoint=86}>

This change enables trace log in the suite so we will have a better
picture if this fails again.

Relates #3333
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@spinscale @Paikan @vasanthakumarr