I've been developing locally on OSX and am now going through the process of
automating the installation on AWS Ubuntu. I have created a core, added my
fields and then untarred the data directory on my Ubuntu instance,
restarted solr (to hopefully reindex), but no documents are seen.
Nor are any er
write.lock
Thanks,
Jeff
On Thu, Feb 1, 2018 at 1:37 PM, Shawn Heisey wrote:
> On 2/1/2018 11:14 AM, Jeff Dyke wrote:
>
>> I've been developing locally on OSX and am now going through the process
>> of
>> automating the installation on AWS Ubuntu. I have created a core,
ckson
wrote:
> One note, be _very_ sure you copy in binary mode..
>
> On Thu, Feb 1, 2018 at 1:33 PM, Shawn Heisey wrote:
> > On 2/1/2018 12:56 PM, Jeff Dyke wrote:
> >> That's exactly what i thought as well. The only difference and i can
> try
> >> to
bly the issue.
>
> Best,
> Erick
>
> On Thu, Feb 1, 2018 at 4:34 PM, Shawn Heisey wrote:
> > On 2/1/2018 4:32 PM, Jeff Dyke wrote:
> >> I just created a tar file, actually a tar.gz file and scp'd to a
> server, at
> >> first i was worried that the gzip
Hi, I've been googling around for a while and can't seem to find an answer
to this. Is it possible to have the embedded jetty listen to H/2 as well
has HTTP/1.1, mainly i'd like to use this to access it on a private subnet
on AWS through HAProxy which is set up to prefer H/2.
With base jetty its
t; for more info.
>
> If it doesn't work out, please let us know, and post the commands you
> tried, output, etc.
>
> Best,
>
> Jason
>
> On Fri, Feb 23, 2018 at 11:56 AM, Jeff Dyke wrote:
> > Hi, I've been googling around for a while and can't seem
thread and my curiosity.
Best,
Jeff
On Fri, Feb 23, 2018 at 3:11 PM, Jeff Dyke wrote:
> Thanks for the tip Jason. I didn't see the -j option there or here
> https://lucene.apache.org/solr/guide/7_2/solr-
> control-script-reference.html
>
> I'll keep this short, i tried
> On 2/23/2018 1:28 PM, Jeff Dyke wrote:
> > Answering a bit of my own question, the underlying jetty would have to be
> > built with it, and get pushed into its jar directory.
> >
> > I think i'll put nginx in front of this, do a quick proxy forcing 1.1 and
> > m
I'm not sure where you're documents are coming from but i would find this
from a 403/404 in an S3 bucket if the permissions were not correct.
But ultimately Walters last sentence is the best next step.
On Mon, Mar 5, 2018 at 12:38 PM, Walter Underwood
wrote:
> I presume this error is from SolrJ
